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?
· No
What are the make and model of the affected audio device(s) and the connection type?
· Ifi Zen Can 3, connected via 3.5 mm audio and TRS cable
Describe the issue
Getting a "Too many failures. Stopping playback" error. Tried to address it in a previous thread and the issue was solved for a single instance of running Roon but keeps on occurring now.
Here is the previous thread for reference: https://community.roonlabs.com/t/roon-is-not-recognizing-audio-output-ref-6b75hw/311411/6
Thanks for linking the previous thread — that context helps.
At this point, to continue meaningfully, we’ll need fresh diagnostics tied to a specific failure.
Please do the following:
Reproduce the issue once more (start playback until you see “Too many failures. Stopping playback”).
Note the exact local timestamp when it happens (date + time).
Post that timestamp here.
Just to set expectations clearly:
Based on everything you’ve described so far, it’s unlikely we’ll see a new or different error pattern in the logs. The behavior is still most consistent with the audio output being taken into Exclusive Mode intermittently by another application or background service on the system.
What we’re trying to determine from fresh logs is which process is taking control of the output, and when.
Once we have a precise timestamp, we can correlate it with system activity and confirm whether that’s what’s happening.
Thank you for reaching back. Reviewing the last thread where we left off, you’re likely just encountering some finnicky edge cases with Exclusive Control in Realtek.
Here’s the audio path you’re using:
RoonServer → WASAPI → Realtek analog output (green jack) → ZEN CAN 3
Whgile using this PC’s green analog output, Roon is talking directly to the Realtek sound chip. Any discrepancy between what Realtek expects and what WASAPI is configured to do will cause the Windows audio strack to reject Roon’s stop/start commands. Roon will keep trying until a certain number of failures, and then issue the error message you see.
One solution is to add a dedicaterd DAC, bypassing Wasapi/Realtek entirely and relying on a different control driver. This means adding more hardware.
In the current setup, you’d need to identify and remove the variable that is tripping up Wasapi → Realtek. It’s commonly something in the Windows sound preferences.
One option is to lock Windows to 48/24 in Sound → Device → Advanced → 24-bit / 48 kHz.
Also disable all Realtek sound enhancements in Windows Sound settings:
Enhancements: OFF
Spatial sound: OFF
Loudness EQ, Dolby, DTS: OFF
You can also try switching away from Realtek to the Microsoft High Definition Device Driver in the same Sound settings page.
After taking these steps, uncheck Exclusive Mode, restart Roon, and then recheck Exclusive Mode to re-initiate a handshake with the driver. Make sure no other audio devices are plugged into the computer and no other software might be open that could compete for exclusive control of the audio stack (iTunes, etc.).
We haven’t seen a response to this thread in over a week and we’re going to allow it to auto-close at this time under the assumption the issue has been resolved.
If you still need help, you can reopen the conversation by simply submitting a new tech support request here. Thank you!