Stream interruption or muting

@support, frequent cessation of play with Roon streaming TIDAL. Play progress bar animates a blue sweep back and forth, then the bar shows normal progressive positioning but no sound accompanies. Hitting forward to next track sometimes initiates play. No problems playing same tracks directly from TIDAL or using BLUESOUND controller app. This is a new and recent feature occurring ove last 3 weeks or more.
BLUESOUND Node 2, MacBook Pro., Ethernet CAT7,

Thanks for reaching out, @Richard_Hernandez1,

So we can better assist you, please describe your network configuration/topology, including any networking hardware currently in use, so we can have a clear understanding of how your devices are communicating.

Does this behavior only occur when playing to the BLUESOUND endpoint? If you play directly to the default output of your Mac Core is there any different behavior?

Does this only occur with TIDAL content or does this affect local content as well?

Thanks!

SET UP
Core resides on
Model Name: MacBook Pro - sys version Mac OSX 10.13.4
Model Identifier: MacBookPro7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.66 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 3 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: MBP71.003F.B00
SMC Version (system): 1.62f6
Serial Number (system): W8018CEQATN
Hardware UUID: 563E371B-A87D-58DA-91CF-90DC863840B1
Sudden Motion Sensor:
State: Enabled
Bluesound Node 2 connected directly to Mac with ethernet CAT7 cable
Streaming TIDAL as my only music source engaged at this time
No problem with TIDAL or Bluesound controller app

Way below minimum spec for cpu.mid 2010 macbook as far as I can determine. Penryn cpu

Hey @Richard_Hernandez1,

As wizardofoz mentioned above, the specs for your Core definitely falls short of our recommended specs.

Because this device uses an Core 2 Duo you may experience performance issues, particularly with larger libraries or DSP, or if you don’t use an SSD for your Roon database.

This may or may not be the cause of the behavior you’re seeing, but we do like to give people a “heads up” when their system is under spec, since it can impact the product in a number of ways, and you may encounter some limitations going forward.

Can you try playing TIDAL content directly to the default output of the Mac Core? Does the same behavior occur?

Thanks!

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.