I wanted to share this fix Roon support provided as it has helped me force some of these tracks to play after doing all of the troubleshooting in the link below. I downloaded a free VPN and that is forcing it to work. The biggest issue for me is that tracks that were working one day seem to not work the next day. New tracks seem to no longer be streaming. Its very inconsistent but connecting to a VPN does usually seem to force the track to play most of the time. It may be worth a shot until a better fix is found.
I have the same issue . The first album I noticed it on is Wrong way up by ENO / CALE The track spinning away on the normal-album plays fine but the same track on the extended,version doesn’t play.
Very,weird .
I’m experiencing the same thing. No apparent logic why certain tracks do not work. I tried to play the ‘not working tracks’ again and again but could not get them to work and even blamed it on the pi. Good to read i am not alone in this.
also having random playback fails with Qobuz. This plus the ongoing saga of old albums being re-added and messing up the date added view.
Try playing the Etta James version. It’s better anyway. 
I’ve been seeing many silent failures lately. This is not the renamed album issue that Qobuz is infamous for. In this case, it is typically a specific song, other tracks on the same album can play without issues.
This is what I see in roon server log:
03/24 01:05:54 [Local 03/23 19:05:54] Debug: [easyhttp] [95578] GET to https://streaming-qobuz-std.akamaized.net/{...} returned after 108 ms, status code: 200, request body size: 0 B
03/24 01:05:54 [Local 03/23 19:05:54] Debug: FTMSI-B got length for qo/5F48014E; 84.5 MBytes
03/24 01:05:54 [Local 03/23 19:05:54] Debug: FTMSI-B-OE set min bandwidth for qo/5F48014E to 3992 kbps
03/24 01:05:54 [Local 03/23 19:05:54] Info: FTMSI-B-OE qo/5F48014E rid:2135 response took 108ms
03/24 01:05:54 [Local 03/23 19:05:54] Debug: FTMSI-B-OE qo/5F48014E rid:2135 request ended -- first block: 0 blocks read: 0 download speed: -256kbps response time: 108ms
03/24 01:05:54 [Local 03/23 19:05:54] Debug: FTMSI-B-OE qo/5F48014E interrupted req 2135; missing block 0
03/24 01:05:54 [Local 03/23 19:05:54] Debug: FTMSI-B-OE qo/5F48014E created new req 2136 for block 0 p 0; active requests 1
03/24 01:05:54 [Local 03/23 19:05:54] Debug: [easyhttp] [95579] GET to https://streaming-qobuz-std.akamaized.net/{...} returned after 166 ms, status code: 200, request body size: 0 B
03/24 01:05:54 [Local 03/23 19:05:54] Debug: FTMSI-B got length for qo/5F48014E; 84.5 MBytes
03/24 01:05:54 [Local 03/23 19:05:54] Debug: FTMSI-B-OE set min bandwidth for qo/5F48014E to 3992 kbps
03/24 01:05:54 [Local 03/23 19:05:54] Info: FTMSI-B-OE qo/5F48014E rid:2136 response took 166ms
03/24 01:05:54 [Local 03/23 19:05:54] Debug: FTMSI-B-OE qo/5F48014E rid:2136 request ended -- first block: 0 blocks read: 0 download speed: -256kbps response time: 166ms
First GET is for a song that doesn’t work (Blind Guardian, Secrets of the American Gods), the second GET is for a normally working song for comparison purposes.
Here to report the same. NUC running ROCK with Wiim Ultra as an endpoint. Have come across multiple files that will not play at all.
Example. Michael Jackson - Human Nature 24/192
Hi! What’s not quite right with Roon?
· Music won’t play or issues with my library
Music won’t play or issues with my library
· Streaming tracks greyed out or unavailable
Tell us what's going on
· I'm having a problem with roon and Qobuz. Roon won't play certain tracks from Qobuz, but other tracks on the same album will play fine. It won't skip the track, it gets stuck on that track and progress bar shows a light going back and forth. You must manually skip the track.
This started a couple weeks ago. At first, it was just a few tracks, but now it is happening more and more. When a song doesn't play, it seems to be a permanent issue. That song never plays again.
I have tried logging out of Qobuz and deleting the cache, restarting the roon server, and I even switched to different roon core (from a sonicTransporter I7 to my old roon Nucleus) and the same tracks wouldn't play. If I bypass my roon server and stream directly into my DAC, all the songs play without an issue. It seems that many others in the community are having the same issue.
I'm running roon version 2.62 (build 1641) on a Small Green Computer sonicTransporter I7 running version 2.9.
Tell us about your home network
· I'm using a NetGear Orbi 970 router, but the roon server and my DAC are connected via ethernet cables to the Orbi. My internet source is a cable modem from Xfinity running at 2 gb. No other components or VPN.
I’m experiencing the same. My Dark Hour by the Steve Miller Band 24/96 on Qobuz is not playing while the rest of the album, as well as the 16/44 version, is.
Same here. After 28 replies I would have hoped that someone from roon would have stepped in and tell us what’s going on.
There’s a growing discussion thread on this very issue.
https://community.roonlabs.com/t/roon-unable-to-play-some-qobuz-tracks/317429
Same issue, a couple of tracks into Young Americans and Roon just sat there doing a cylon impression. Track it got stuck on was Fascination (2016 remaster) on both 192 and 96 versions.
The Support Team do not monitor discussions here in Roon Software Discussion > Qobuz. Requests for support are made by following this link to provide the details of your case to Technical Support: Technical Support Request
I see that a request for this issue has been raised, so the Support Team will be following it up there.
Same issue here, add me to the list…
I have the impression that things are progressively getting worse…
And me too. Qobuz has been very slow and skipping some tracks.
Hello @Robert_Lowe,
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.
Same for me.
Same issue for me.
For no obvious reason the troublesome tracks will occasionally be playable, but a few hours later they’re back to failing again.
Hi @Phil_Schapiro,
Thanks for getting in touch.
We’ve identified this issue as a widespread problem and have initiated an internal investigation.
It doesn’t appear to be caused by anything on the user side at the moment.
If we need further details from you, we’ll be sure to reach out.
We appreciate your collaboration on this matter.