Playback fails with "Too many failures" error (ref#86MILK)

[Asgeir_joel_Jacobson]

What best describes your playback issue?

· The queue is skipping tracks

What type of Zone is affected by this problem?

· *Network Zones* are affected.

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

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?

· It happened on the 24th and 25th of December and again on the 1st of January 26.

What are the make and model of the affected audio device(s) and the connection type?

· I use mu pc as a nucleus, and I am trying to play from the roon app on that computer and it doesn matter if I try to play through my stereo or through headphones on my laptop.

Describe the issue

When I select music, it goes through a few songs without playing them and then comes "To many failures" and everything stops

Describe your network setup

I have a fiber up to my apartment and from there a router. I am in close range of the router. I dont think its a connection problem cos I can play music from the Tidal app.

[vadim]

Hello @Asgeir_joel_Jacobson,

Thanks for the report — I checked the diagnostics and the failure is explained in the logs.

This is not a TIDAL login/auth issue. Roon is successfully fetching the track from TIDAL, but the RAAT stream to your network zone is experiencing repeated dropouts, and Roon stops playback once the dropout threshold is exceeded.

From the logs:

12/31 17:42:07 [Local 12/31 17:42:07] Debug: [easyhttp] [6716] GET to https://lgf.audio.tidal.com/mediatracks/CAEaKwgDEidjNGIwMDY2MTM5ODg4OWNkYzgxYTZkMzY2MDQwMDJiNV82Mi5tcDQ/0.flac?token=1767206526~MTU1YjY5ODFiZjU3NTc2MWFhZDg2YzMwYTIxYjA3MjVmMzRhNjk4Ng== returned after 207 ms, status code: 200, request body size: 0 B
12/31 17:42:07 [Local 12/31 17:42:07] Debug: FTMSI-B got length for ti/5D6DD79F; 134.5 MBytes

Playback starts, but buffer/streaming becomes unstable:

12/31 17:42:13 [Local 12/31 17:42:13] Debug: [prebuffer] sleeping in read -- this isn't good
12/31 17:42:17 [Local 12/31 17:42:17] Warn: FTMSI-B-OE ti/5D6DD79F: poor connection kbps:6841.0 (min:7689.0)

Then the endpoint reports repeated dropouts, and Roon kills the stream:

12/31 17:42:26 [Local 12/31 17:42:26] Trace: [Pro-Ject Audio Systems Stream Box S2 ultra @ 192.168.11.60:46111] [raatclient] GOT [797] {"status":"Dropout","samples":28634}
12/31 17:42:27 [Local 12/31 17:42:27] Trace: [Pro-Ject Audio Systems Stream Box S2 ultra @ 192.168.11.60:46111] [raatclient] GOT [797] {"status":"Dropout","samples":80640}
12/31 17:42:33 [Local 12/31 17:42:33] Trace: [Pro-Ject Audio Systems Stream Box S2 ultra @ 192.168.11.60:46111] [raatclient] GOT [797] {"status":"Dropout","samples":96000}
12/31 17:42:34 [Local 12/31 17:42:34] Warn: [Heima] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
12/31 17:42:34 [Local 12/31 17:42:34] Warn: [zone Heima] Track Stopped Due to Slow Media

So the “Too many failures” you see is the end result of too many dropouts on the network zone playback path. This would also explain why it can skip a few tracks and then stop — the stream fails repeatedly and Roon eventually aborts.

If you try playback to System Output (local audio on the laptop) and it plays fine while the network zone fails, that would confirm the issue is specific to the network endpoint path rather than TIDAL itself.

One more thing to test, since the logs show repeated RAAT dropouts leading to “Too many dropouts… Killing stream”:

Please try connecting the affected device by Ethernet cable (wired) and test playback again (same zone, same TIDAL content).

If playback is stable on wired but fails on Wi-Fi, that confirms the issue is caused by wireless instability / packet loss / mesh behavior, rather than TIDAL or your Roon installation.

[connor]

Hi @Asgeir_joel_Jacobson,

We wanted to reach out to see if you’d had a chance to try some of the suggestions in the post above.

Diagnostic logging indicates that Roon is experiencing sample loss during audio transport over the network. If you’re relying on WiFi for the S2 Ultra, then WiFi interference is the most plausible explanation. A hardwire connection should relieve symptoms.

If you’re already connected via ethernet, we’ll need to investigate the network settings more closely to ensure the network is handling clock sync traffic as Roon expects.

If dropouts continue to occur after hardwiring via ethernet, please let us know the approximate timestamp of the last dropout you encountered or the name of the track that was playing. We’ll pull fresh logs and continue to investigate. Thank you!