Does the issue happen with local library music, streaming service music, or both?
· *Both streaming and local* *library* music are affected.
Do you encounter any playback errors with the "System Output" Zone?
· The System Output has the same problem as my other Zone.
Do you have a complex network setup?
· Both the device and RoonServer are connecting to a *single router*
Please try rebooting your router.
· No, I'm still having trouble
Do you have an approximate timestamp of when the issue last occurred?
· December 16th 10:45 pm pacific (17th 6:45am UTC)
What are the make and model of the affected audio device(s) and the connection type?
· RME ADI-2/4 Pro SE
Describe the issue
When trying to play music music using Roon, it just starts skipping tracks without playing them. Eventually showing the message "Too many failures. Stopping playback.".
I'm playing everything on localhost on windows. Files are on local, and audio out is from local. It happens to all zones, including System Output. I'm on the latest build (2.57 build 1598). I'm connected to a RME ADI-2/4 PRO SE. The DAC works fine from other sources (such as youtube, and games). I'm on the latest MADIface driver (1.08). I've also tried my monitor sound output, same issue happens in Roon. My monitor sound output also works fine from other sources.
I've tried uninstalling and reinstalling Roon, tried the early access version, running Roon in admin mode, using HQPlayer (does not skip track, but HQPlayer shows "empty transport" error). None helped.
Describe your network setup
Everything on local windows machine. Local music files hosted on E drive. Roon installation on C drive. Playing through usb out to my RME ADI-2/4. Tried with system out, ASIO, and WASAPI
Thank you for the detailed report — that helps a lot.
Since this behavior affects all zones, including System Output, and occurs with both local and streaming content, this strongly suggests a local audio pipeline or OS-level issue, rather than a network or DAC-specific problem.
To move forward, we’ll need to gather a bit more targeted information.
1. Reproduce the issue once more and confirm the timestamp
You mentioned Dec 16th at 10:45 PM Pacific (17th 06:45 UTC) — if possible, please reproduce the issue again and confirm the exact local timestamp so we can review fresh diagnostics around that moment.
2. Check Windows audio configuration
Please verify:
That no other applications are holding the audio device in exclusive mode
Windows Sound Settings → ensure the default format matches a common rate (e.g. 24-bit / 44.1 kHz or 48 kHz)
Disable any audio “enhancements” or DSP at the OS/driver level
3. Windows Event Viewer
If the issue persists, please check Windows Event Viewer → Application for any errors occurring at the time Roon reports “Too many failures” and share screenshots or error messages if present.
Once we have a fresh timestamp and confirm whether the RAAT reset changes behavior, we can dig deeper into what’s causing the playback engine to fail repeatedly.
The time stamp I gave was pretty exact, and you asking for a more exact timestamp made me think that my tracking protection is blocking the logs from being sent.
I whitelisted all of the roon executables my adguard and everything worked.
I guess tracking is a synchronous operation prior to playing music, even if everything is on local?
I feel like that’s a bug. Or maybe it’s protection from people sharing logins?
Also note adguard does not filter HTTPS traffic by default, which means whatever it’s sending might not be encrypted.
Anyway, thank you for all of your help. My problem is resolved.
