· Music won’t play or issues with my library
· Streaming tracks greyed out or unavailable
· Specific track from album won't play, gets stuck doing nothing.
· All Cisco, AP, just dumb switches, Roon is not used over wifi, wifi-5
Notice the activity light is not on, even though album is playing. Forgot to include the track
Hi Hi @vmartell,
Hi @vmartell,
Thank you for your post.
Diagnostics from your Roon Server show that it can successfully reach Qobuz servers, but the requested audio content is not being delivered.
Our team is currently investigating similar reports. Based on what we’re seeing, this appears to be an upstream issue affecting the network pathway between Qobuz and your location.
In the meantime, if you have access to a VPN, you can try connecting through a different region to force an alternate routing path — this can sometimes restore playback.
We’ll update this thread as soon as we have more information. Thank you for your patience.
Appreciated, will re-test today. Question, though, it is just one song that fails - not sure about Roon’s/Qobuz’s architecture and/or API - IF there is a URI for each song, maybe is malformed or gets corrupted on Roon’s side - Qobuz interface plays it OK.
Re-tested using VPN and without. Using VPN tried from different places in US, Europe and UK.
I see the issue happening also with https//open.qobuz.com/track/28187427 and only that song on the album. Went back to the Queen album I used to report, now the reported song works, but a different one, https//open_dot_qobuz_dot_com/track/54091881 now doesn’t work. For both reported songs, this consistent, only that one, always fails, I assume it will until it works, due to unknown circumstances at this point.
[Edit - had to remove the colon from the links above because for some reason, the forum did not allow me to post those links - seems like linking to qobuz should be allowed, IMHO]
Hello @vmartell
Thank you for sending over those additional timestamps! We really appreciate your diligence in tracking this intermittent behavior.
I wanted to share a quick update on what our engineering team has uncovered. As you astutely suspected from glancing at the logs, this behavior is tied to a specific communication nuance with the Qobuz Content Delivery Network (CDN). During these moments, a connection is successfully established with their servers, but the audio data stream is interrupted by an external factor—essentially, the CDN responds but delivers an empty payload. The system then continually attempts to re-request the missing audio blocks, which results in the track failing to start or triggering the “loading slowly” message.
The good news is that thanks to the detailed timestamps and logs from you and a few other users, our R&D team now has all the data they need. They are actively investigating how to optimize and sustain these specific stream negotiations with the Qobuz CDN.
We do not need any further logs at this moment. Since this is actively being worked on by the development team, the best way to track the progress of the resolution is to keep an eye on our Roon Software Discussion > Software Release Notes category. Any optimizations or improvements regarding this Qobuz streaming behavior will be officially announced there in future updates.
Thnx. Will do.
Hey @vmartell
There aren’t any additional details needed at this time, so we will go ahead and close the thread for the time being, and if any other questions arise after the developers have reviewed the case, we will re-open the thread and reach out once more.
Thanks again for your report, and thank you in advance for your patience as the ticket progresses through the development queue for review.