When playing Tidal 192/24, playing is sometimes stopped in the middle of a track. It seems to work properly when playing Tidal on 44/16.
Hardware :
Server on PC i7 Windows 11 32GRAM
Streamer is Marantz SACD 30n
The problem is the same when playing 192/24 from my library.
Hello @Johan_Vanheerswynghe
Thank you for reaching Roon support,
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Just now, Tidal is skipping tracks continuously on 192/24. It runs fine on 44/16.
At 12:55 it skipped tracks again.
At 12:58 it skipped tracks again.
It is now skipping tracks, not just stopping.
Switching back to 44/16.
Re-testing on 5Ghz Wifi channel now. Greater speed.
I changed a setting in my wifi extender to improve speed. Seems to be better. I’ll keep monitoring it.
I can easily repeat the issue. When my son is streaming much data to his PC, my music on ROON just stops playing (another PC on the network). So it is a network issue. I’ll have to stick to 44/16 to avoid the music stopping.
Any recommendations to improve?
Is there any possibility to give streaming priority over other downloads of data?
I would suggest directly connecting your server and endpoints via ethernet and eliminate wifi from your playback chain entirely.
Roon decompresses that 24/192 into PCM which is a many times larger “file” and it needs to stream in near real-time to avoid drop outs. Any stress on Wifi caused by others using a lot of data, environmental signal degradation, etc, can cause a drop in playback.
You might try changing the wifi channels being used, this can help with network congestion (and signal interference) from household usages (or neighbors), resulting in a more stable connection. That is set your son to using one channel and Roonserver/Endpoints to a different channel.
We’ve requested diagnostic logs to inspect these dropouts more closely; please leave Roon open on your Windows machine for at least an hour to allow the report to reach our cloud servers.
Based on the existing logs associated with your account, these dropouts are indeed due to accumulated packet loss. When WiFi interference prevents a packet of data from passing between Roon Server → Zone during playback, the endpoint will have to re-request that data before it can buffer it for playback. If too much data is re-requested in too short a window, the buffer can lag to the point where playback catches up. At this point, Roon Server tears down the audio stream, stopping playback to the Zone; it can’t play a broken stream.
Generally, relying on a hard-wired Ethernet connection for your networked Roon Zones will help mitigate this issue. Sometimes, network congestion and traffic management can impose restrictions on how much data Roon Server can transport to any Zone even over Ethernet. In those cases, we have several topological and settings adjustments that we recommend.
Please see here for more details:
Update : I have received a new state-of-the-art modem from my internet provider.
The WIFI speed has now tripled! And, I think the Roon issues are resolved.
Thanks.