Tidal playback stuttering and skipping on Roon (ref#WOET3Q)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Hi, I have been using Roon and Tidal for years. I Roon hosted on a dedicated Intel NUC with ROC installed (latest Version) with various endpoint (main Devialet 220 pro, multiple Blusound devices and multiple Beocreate boards). Since a few weeks I experience issues with Tidal via Roon: after some time into a song, the music stutters and then jumps to the next song, where the issue repeats itself). That would be quite a pity as me and my family used to love Roon but with this bug we are about to abandon it...

Tell us about your home network

· My main setup is connected via cable ethernet; smaller speakers via WLAN; we rarely play more device than one at the same time. Internet connection is via a very fast cable network (1 Gbit).

2

Hey @Fabian_Dux,

Thanks for taking the time to write in and share your report!

From a fresh diagnostic report, we’re seeing the following traces which lead to playback stopping:

Warn: FTMSI-B-OE ti/D2FEEDFD: poor connection kbps:671.0 (min:1186.0)
Trace: [Devialet Expert 220 Pro] [raatclient] GOT [41] {"status":"Dropout","samples":22050}
Warn: [Devialet RAAT] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
Trace: [Devialet RAAT] [zoneplayer/raat] too many dropouts. stopping stream 
Warn: [zone Devialet RAAT] Track Stopped Due to Slow Media

It does appear to be struggling to maintain a sufficient network connection.

Can you navigate to your Roon Settings > Services > Tidal > Edit and share a screenshot of what you see?

To confirm, your setup is already hardwired via ethernet? Perhaps checking if your router is due for a firmware update may help - let us know any additional information around your network if possible. Thank you, Fabian!

3

Hi @Fabian_Dux,

Pinging this thread since we haven’t seen a response yet. Please let us know the answers to @benjamin’s questions in the post above since this information is crucial to troubleshooting.

If you’ve encountered any dropouts since your last post, please share the name of the track or an approximate timestamp here so our team can pinpoint the event in diagnostic logging.

Thank you and we’ll watch for your response.

4

This thread is now closing due to lack of response. You can reactivate the conversation by submitting a new support request anytime.