Qobuz playback skipping and stopping in Roon (ref#AXX3T1)

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

· I'm experiencing a recurring issue with Qobuz playback in Roon.

Symptoms:

Some tracks are skipped completely.
Other tracks start playing but stop after a few seconds and Roon automatically jumps to the next track.
The issue occurs across multiple albums and artists.
Playback of local files appears to be normal.

Additional information:

Qobuz works normally through the native Qobuz app.
Internet connection is stable.
I have already logged out and back into Qobuz within Roon and restarted the Roon Server.

Could you help me identify the cause?

Tell us about your home network

· MOdem

I too have exactly this quite frequently, then days where it does not occur.

Hi @maciasteressa, welcome to the community, and thanks for the clear description.

Because local playback is fine and this only affects Qobuz, the next thing we want to check is whether Roon is hitting a network or service-specific issue when it tries to fetch the stream. A few things would help us narrow that down:

  • Are any switches, mesh nodes, or powerline adapters between the Roon Server and the modem/router?
  • When a track skips or stops, does it happen only on certain albums, or across all Qobuz content, including tracks you have already played before?
In the meantime, please try one targeted check: fully sign out of Qobuz in Roon, then restart the modem/router as well as the Roon Server, and sign back in once everything is back up. If you can also note one or two exact examples of the skipped tracks, that will help us look for a pattern.

Send back the network details and a couple of track examples, and we can take the next step from there. Thank you! :folded_hands:

Hi @maciasteressa,

Just checking in on this. Were you able to sign out of Qobuz in Roon, restart both your modem/router and Roon Server, and then sign back in after everything came back up? We also asked about any switches, mesh nodes, or powerline adapters between the Roon Server and the router, plus whether the skips are happening on specific albums or across all Qobuz tracks, so any updates on those details and a couple of exact track examples would help us narrow it down. Let us know what you found, thanks.

Hi,

Yes, I followed all the steps you suggested. I signed out of Qobuz in Roon, restarted both my modem/router and the Roon Server, and then signed back into Qobuz after everything was back online.

Unfortunately, the issue persists and tracks are still skipping.

There are no switches, mesh nodes, or powerline adapters between the Roon Server and the router. The problem does not seem to be limited to specific albums; it happens across different Qobuz content. Interestingly, playback is completely stable when using the Qobuz app directly or the KEF app, so the issue appears to be isolated to Roon’s integration with Qobuz.

Please let me know if there are any additional logs or diagnostics I can provide to help narrow this down.

Thank you.

Hi @maciasteressa,

Thanks for the additional information!

From a fresh server diagnostic report, it appears you’re hitting a known issue related to restrictions surrounding the Qobuz CDN within Roon.

While Qobuz did fix the CDN-related issues previously, we’re still seeing lingering CDN issues here and there, and are still in communication with Qobuz on getting these final strings tied up properly.

Specifically, Roon Server repeatedly requests block 850 of a Qobuz stream, literally hundreds of times across several minutes, and each request comes back with blocks read: 0 and download speed: -256kbps (a sentinel value indicating nothing was actually transferred).

The Qobuz CDN responds with HTTP 206 (success), meaning the connection isn’t being refused, but the data simply never arrives.

Could you see if any of the below troubleshooting steps help minimize the issue at all:

  1. In Roon > Settings > Services > Qobuz, temporarily set the streaming quality to CD Quality (16-bit/44.1kHz) rather than Hi-Res. See if the dropouts stop or significantly reduce.
  2. If you can, test out setting up a VPN tied to your server machine, and set it to somewhere outside of your current location, and see if you’re able to reproduce the issue.
Thanks for your ongoing patience in the meantime!🙏

Hi @maciasteressa,

Just to reiterate, Qobuz is still working to stabilize certain content delivery pathway upon which it sometimes relies to serve tracks to Roon users.

We’re working closely with their team to resolve this, and you can track progress in this thread:

Roon won't play certain tracks from Qobuz, gets stuck on progress bar (ref#K9XYO0) [Partially Resolved, Qobuz Backend Issue] - #763]Roon won't play certain tracks from Qobuz, gets stuck on progress bar (ref#K9XYO0) [Partially Resolved, Qobuz Backend Issue]

Hi Benjamin, Thanks for the update and for looking into this.

I changed the Qobuz streaming quality to CD Quality (16-bit/44.1 kHz), and so far that appears to have resolved the issue. I tested with several tracks that were previously stopping or cutting out, and they now play normally.

This seems to confirm that the problem is related to Hi-Res streaming and the Qobuz CDN issue you mentioned.

Could you please let me know what I should expect regarding a permanent fix? For example, will this be addressed through a future Roon update, or should I periodically test Hi-Res streaming again to see if the issue has been resolved?

Thank you again for your help and for keeping me informed.

Hello @maciasteressa,

Glad CD quality is working as a workaround for now!

To answer your question - this will be fixed on Qobuz’s side, not through a Roon update. Once Qobuz stabilizes their CDN delivery, hi-res streaming will resume working automatically without any action needed on your end. You can periodically switch back to hi-res in Settings → Services → Qobuz to check if it has been resolved. You can also follow progress in the tracking thread Connor linked above.

Hello @maciasteressa ,

Since tracking will occur in the linked thread, we’ll go ahead and close this thread for now. Please reference Connor’s linked thread post for the latest updates. Thank you.