Tracks skip unexpectedly when using Qobuz with Roon (ref#VAH4HM)

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 use qobuz with roon and a few times today tracks suddenly stop and skip to next track

Tell us about your home network

· I use a FritzBox 7530AX

Hey @Paul_Flanagan,

Thanks for writing in and sharing your report! We’d like to take a closer look into what might be going on behind the scenes, if you could please bring your Roon Server back online, we’ll enable diagnostics and analyze further.

Thank you! :raising_hands:

Hi @Paul_Flanagan,

Diagnostic logs show some of the track failures to which you’re referring.

In some cases, you’re encountering a known issue with the Qobuz API’s third-party content deliver network serving Roon. We’re working directly with the Qobuz team as they work to resolve this problem.

https://community.roonlabs.com/t/roon-wont-play-certain-tracks-from-qobuz-gets-stuck-on-progress-bar-ref-k9xyo0-partially-resolved-qobuz-backend-issue/317491/

In other cases, the Qobuz servers are refusing to serve the request content, possibly because your Qobuz account tier is not authorized to play that particular file format, or because Qobuz is in the process of replacing the underlying object in their catalog.

Are you able to share the name of a track that failed to play over the weekend?

We noticed you have a Roon trial; please let us know if you require additional time on your trial period to allow for troubleshooting.

We’ll watch for your response. Thank you!

Thank you for looking into this; much appreciated! I had my room server set up on a Mac in a room other than my listening room. I checked the internet speed for that computer and it was slow so I moved my Roon server to a different computer in my listening room where the internet speed is super fast. I’ll see if this makes a difference.

I’m enjoying my trial, despite these initial issues and of course any additional time would be appreciated.

Many thanks,

Paul

Hello @Paul_Flanagan,

Thank you for the update! Moving your Roon Server closer to your listening room is always a good idea for general performance, but in this particular case, it’s unlikely to make a difference with the track skipping issue. As Connor mentioned, the root cause is on Qobuz’s side - specifically, how their content delivery network handles third-party applications like Roon. We are actively working with the Qobuz team to get this resolved.

In the meantime, if you notice specific tracks that fail to play, feel free to share the names here, and we can check whether it’s a CDN issue or something else.

Thanks for your patience!

Hi @Paul_Flanagan, thank you for working through the issues with us. To give you a bit more time, we’ve gone ahead and extended your trial. You can check your account page for the new expiration date.

Hi @Paul_Flanagan,

Logs do show evidence that some of the dropouts are, unfortunately, a result of the upstream delivery issue affecting the Qobuz API’s content delivery network. Qobuz is working hard to resolve this issue. We have a tracking thread here:

In other cases, we see the Qobuz API returning unauthorized for some requested tracks. Usually, this occurs when a user has a Qobuz trial account, or is attempting to play hi-res content about their subscription tier. If you’ve already verified your Qobuz subscription, then I recommend forcing a sync in Roon Settings → Services → Qobuz to make sure your Roon library reflects any changes.

Do you only experience dropouts with one Zone, or does this occur regardless of the output selected?

We’ll watch for your reply. Thank you!

Hi @Paul_Flanagan,

Wanted to follow up on this and see whether you’ve had a chance to check the Qobuz side of things and, if needed, force a sync in Roon Settings → Services → Qobuz so your account changes are reflected. We’d also still like to know whether the dropouts happen in just one Zone or across whichever output you choose. Let us know what you’re seeing, thanks.

Hello @Paul_Flanagan ,

We have not heard back from you, so we will go ahead and close this thread due to inactivity. If you need further assistance, please submit a reopen support request via the technical support help form link and specify that the issue be reopened. Thank you.