Is your device connected directly to the Roon Server via cable or over the network, or is it chained through another device (such as a streamer, Roon Bridge, or Roon Remote)?
· It is connected through a different device (e.g Rasberry Pi)
Does the device play audio from another source when using the same connection?
· The device has no problems with another audio source
Have you checked that Roon is whitelisted in any firewalls?
· I've checked the firewall and the issue remains
If the device has multiple output options, do the other options work as expected?
· Only one output type is affected while the other output type works as expected
Is the device using the latest firmware as per the manufacturer?
· Firmware is up-to-date but the issue remains
What are the make and model of the affected audio device(s) and the connection type?
· Bluesound Node 2i feeding Chord Mojo 2
Describe the issue
No sound playing Tidal 192/24 Flac Bluesound Node 2i Chord Mojo 2
Thank you for the report. We’ve activated diagnostic logging to take a closer look.
We see some forcible network closures of RAATServer and some bandwidth allocation dropouts with the connection to Tidal during playback of 24/192 FLAC files. The prebuffer is sleeping in read. This occurs with lower-quality formats, as well, to nearly all endpoints, but Roon recovers playback in almost all cases.
Do you have any stateful firewalls or antivirus software that might be restricting RoonServer and RAATServer’s network access? What about traffic management settings in a router or managed switch (upstream of RoonServer) that might be throttling bandwidth?
In the meantime, we’ll take a closer look with the team to determine next steps and keep an eye out for your response.
The conclusion is that RoonServer’s ability to buffer content from Tidal’s servers is compromised.
Curiously, we see the buffer slowing intermittently during playback of lower-quality files, including 44.1kHz. These errors accumulate sufficiently to dispose the Zone because it’s not receiving an audio stream.
You’ll need to check the router’s settings to see why RoonServer’s connection to Tidal might be restricted or throttled. If there are Quality-of-Service or traffic management settings, verify that RoonServer’s IP address is prioritized.
Simplifying your network overall would be a useful thing to troubleshoot. Can you get a basic hardwire ethernet connection from your Roon Server directly to your router, as well as to your Node 2i?
The prebuffer short reads with all Tidal content, including much smaller 16/44.1 FLAC files. The downloads of these tracks time eventually time out, but Roon has often sufficiently buffered lower-quality content to maintain the audio stream.
With much larger files like 24/192 FLAC, the accumulated failures are often sufficient to end the audio stream.
Unfortuantelt, this is a repeat of our findings in the last log set - this Windows machine isn’t maintaining a connection to Tidal’s servers with sufficient bandwidth to download these files in time to play them back with Roon.
Have you tried changing the DNS server in the router settings page? If it’s something default from your provider, try switching to Cloudflare (1.1.1.1).
Certainly, let us know how it goes! My apologies if I’ve glazed over this - do you run into the same issue when streaming content from Tidal directly, completely outside of Roon?
