Does the issue happen with local library music, streaming service music, or both?
· *Only streaming* music is affected.
Please select the streaming service(s) with which you're encountering playback problems.
· TIDAL
Have you tried logging out and back in again to your streaming service in Roon Settings?
· Logging out and back in had no impact, the issue remains
Do you have an approximate timestamp of when the issue last occurred?
· 30 Nov 2025 between 5pm and 5.30pm CET
What are the make and model of the affected audio device(s) and the connection type?
· see above
Describe the issue
Streaming from Tidal leads sporadically to interruption and skipping in the queue. It does not happen all the time. Internet connection is stable at 100/50. Setup: ROCK connected to the router via LAN, endpoint is WIIM Pro, also connected via LAN to the same router.
Describe your network setup
Fritzbox 7530 -> R.O.C.K -> WIIM Pro (all conntected via LAN)
Would you kindly let us know the quality set in the Settings → Services → Tidal → Edit → Streaming quality?
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.
Thanks for the update! From a recent diagnostic report from your ROCK, we can see the following errors leading to Tidal playback stopping:
Warn: FTMSI-B-OE ti/0F20631F: poor connection kbps:455.0 (min:803.0)
Trace: [Wohnzimmer] [zoneplayer/raat] too many dropouts. stopping stream
Trace: [Wohnzimmer] [Lossless, 16/44 TIDAL FLAC => 16/44] [PLAYING @ 0:15/2:44] Put There By The Land - Great Lake Swimmers
Warn: [zone Wohnzimmer] Track Stopped Due to Slow Media
Based on the network information you’ve provided so far, it sounds like your network setup/chain is already pretty simple - both devices are hardwired directly to your primary router.
If that is the case, I’d next look to investigate any network priority-related options within your router settings - and set bandwidth priority to both your endpoint and server.
I do believe FRITZ!Box lets you prioritize devices or applications under “Internet → Filter → Prioritization.” Or, on the mobile MyFRITZ!App you can mark a device as “prioritized device” (useful for e.g. video-conferencing) under the “Home Network → Network → Network Connections” settings.
Let me know if you have either of these options and if that changes your behavior as well. If it doesn’t, it may be worth exploring different DNS servers like Cloudflare or Google.
We have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. Can you please give this a try and let me know if it helps?
Thanks for the update - sorry to hear the above didn’t help. From a fresh diagnostic report, we can see similar errors leading to playback failure:
Warn: FTMSI-B-OE ti/A1584B1A: poor connection kbps:608.0 (min:990.0)
Trace: [Linkplay Technology Inc. WiiM Pro Receiver @ 192.168.1.146:44589] [raatclient] GOT [7843] {"status":"Dropout","samples":21504}
Warn: [Wohnzimmer] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
Trace: [Wohnzimmer] [zoneplayer/raat] too many dropouts. stopping stream
Info: [Wohnzimmer] [zoneplayer] advance didn't change the track. returning short read
Trace: [Wohnzimmer] [zoneplayer/raat] Endpoint Linkplay Technology Inc. WiiM Pro Receiver State Changed: Playing => Prepared
Trace: [Linkplay Technology Inc. WiiM Pro Receiver @ 192.168.1.146:44589] [raatclient] SENT [7873]{"request":"end_stream"}
Debug: [raat/tcpaudiosource] disconnecting
Warn: [zone Wohnzimmer] Track Stopped Due to Slow Media
Info: [zone Wohnzimmer] OnPlayFeedback StoppedEndOfMediaUnnatural
Debug: [zone Wohnzimmer] _Advance (Track)
Info: [audio/env] [zoneplayer -> stream] All streams were disposed
Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposed
My apologies if this has been glazed over, but does this occur no matter the endpoint you attempt to play audio from?
For example, if you only use the system output from the remote device you’re using Roon on, do you experience the same issue?
It may also be worth testing different Ethernet cables, as well as different ports - if possible. Let us know if that makes any difference, thank you!
You’re correct that if this issue occurs across all endpoints and cabling, then an upstream routing or peering issue between TIDAL and your ISP (Vodafone) becomes a realistic possibility. However, since ROCK cannot run a VPN, we need a different approach to confirm this.
1. Temporarily move your Roon Server to another device
If you have a macOS or Windows machine available, please install Roon Server there and point it to a clean database (do not restore a backup for this test).
This will allow us to bypass the ROCK networking path.
Then try TIDAL playback from the same network environment.
2. If the issue still occurs, test with a VPN
On the Mac or PC running the temporary Roon Server:
enable a VPN (any reputable provider is fine)
test playback again
If TIDAL becomes stable when the VPN is active, this strongly indicates a TIDAL ↔ Vodafone routing issue.
If the issue persists even through VPN, then we know the problem is not related to ISP peering.
Please let us know once you’ve had a chance to try running Roon Server on another device. This will give us the clearest data point to determine next steps.
Hi Vadim,
thank you. The described test setup looks quite burdensome. Given that the issue occurs only temporarily (mostly it works for days without any problems), I am not sure whether it would lead to clear results. In the support section I have read similar complaints about the Tidal connectivity with identical symtoms. I would rather switch to Qubuz, unless you tell me it would most likely make no difference.
