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?
· 21:32 (UTC+1), playing Hongkong Remastered by Monolake
What are the make and model of the affected audio device(s) and the connection type?
· Logitech G Pro X and cheap Pebble V3 speakers
Describe the issue
Roon worked fine before what I'm going to describe.
I have a PC and a work laptop, and I use my headphones and speakers on both. My work laptop runs on Linux, so I installed Roon Bridge and used my phone's Roon app to play some tunes
Now back on my PC, both my headphones and speakers won't work with Roon. When I play an album through Tidal or local files, it rapidly skips tracks until displaying the "Too many failures. Stopping playback." error message.
I tried restoring a backup from 4am, before the whole Roon Bridge usage, but the problem persists. I tried restarting my PC, my router, unplugging my devices, updating their drivers (even though everything else but Roon works fine).
Maybe I shouldn't have used Roon Bridge on devices used on another computer? Anyway, I'm starting to seriously regret it.
Describe your network setup
ROCK is directly connected to the router. My PC and work laptop both use WiFi
Thanks for writing in and for sharing your report! It’s likely the Roon bridge on your work laptop doesn’t have to do with your issues - just a timely coincidence!
From a fresh diagnostic report, we can see the following errors pop up when playback is attempted:
RAAT__OUTPUT_PLUGIN_STATUS_FORMAT_NOT_SUPPORTED
And look at the format Roon is trying to open:
PCM
16-bit
44.1 kHz
2 channels
So the failure happens after Roon hands the stream to the output device, when the RAAT output plugin asks the OS audio device to open that format.
Can you double-check your PC audio settings to confirm it can play back 44.1 kHz?
Windows Settings → Sound → More sound settings
→ Playback tab → your output → Properties → Advanced
To rule out any interaction with the Roon Bridge setup, could you please try the following:
Fully disconnect the Linux work laptop from your audio devices
Unplug the headphones and speakers from the Linux machine
Make sure the work laptop is not using them at all (and ideally powered off or asleep)
Then reconnect the headphones/speakers only to your PC and retry playback in Roon
On your Windows PC, could you please confirm whether Exclusive Mode is enabled or disabled for the affected devices?
Roon Settings → Audio → device settings
Please let us know:
What Default Format is selected
Whether “Allow applications to take exclusive control” is checked
Even if these formats worked previously, the error we’re seeing indicates that Windows is currently refusing to open the device at 44.1 kHz when Roon requests it, which usually points to an OS-level audio configuration or device lock rather than a library or Bridge-related issue.
Let us know the results after fully disconnecting the Linux machine and checking the Exclusive Mode settings, and we’ll take it from there.
The 1st step was already done, but I rebooted my Linux laptop just to ensure I did everything correctly. Disconnected everything properly and the laptop is powered off.
As for the 2nd step, both devices had exclusive mode disabled. I tried enabling it but nothing changed so I left it disabled. As for the default format, I see nothing of the sort in the device setup interface. Are you talking about “WASAPI” by any chance?
After writing this, I tried setting back to default the device settings, and now both the speakers and the “System Output” work fine. What’s super strange though is that my headphones work fine on the System Output if they’re the default audio device, but their specific device in Roon still doesn’t work.
I have no reason to use the devices separately instead of the System Output (apart for troubleshooting), so I guess my problem is solved? Kinda. I’m still not sure what triggered and solved this problem.
It could be that resetting to the default settings did two critical things:
Cleared the per-device audio configuration
Forced Roon to re-query Windows for:
Supported sample rates
Bit depth
Exclusive-mode behavior
Buffer requirements
Once that happened:
System Output worked immediately (fresh, generic path)
Speakers worked (their profile was rebuilt successfully)
Headphones partially worked
[quote="Maryline_Lantonnet, post:6, topic:314045"]
but their specific device in Roon still doesn’t work.
[/quote]
This tells us:
The driver itself is fine
Windows can play to it
Roon can play to it via System Output
But the headphones’ dedicated Roon device profile is still:
Expecting a format the driver no longer accepts
Or failing exclusive-mode negotiation
Or stuck on an invalid sample-rate range
You can aboslutely continue to use the setup you have currently with System Output, but if you’d like to continue troubleshooting the headphones, try this:
We wanted to circle back before this thread auto-closed due to inactivity. Are these Zones still functioning as expected at this time? Do you have any further questions we can answer?
Just letting you know that I couldn’t make my headphone zone work again, even after the procedure.
In my specific case it is not a problem though.
The roon bridge on my Linux laptop works fine for both speakers and headphones.
On my Windows PC the System Output zone still works too.
We wanted to circle back before this thread auto-closed due to inactivity. If you’d like to troubleshoot the problem you mentioned with the headphone Zone in your last response, we’ll just need the following to get started:
the name of a track that failed to play, or an approximate timestamp of when the problem occurred f it didn’t involve active playback. We’ll use this to pinpoint the event in logs.
a screenshot of the Signal Path for the headphone Zone.
We’ll proceed from there and pin down what’s wrong.
Otherwise, we can allow this thread to close automatically in a few days. We’ll watch for your response. Thank you!
We’re going to close this thread at this time due to inactivity. You can always submit a new tech support request here and we will reactivate the conversation. Thank you!
