relieved perhaps, but don’t hold your breath waiting…
This track always stops！
Qobuz (Japan) stream
-
Artist:
Scandal -
Album:
Echo -
Track:
06 - Heaven -
At:
Stop at Top -
Log:
Playback was interrupted because a track failed to load.
Regards.
I am in the US.
Album: Fearless (Taylor’s Version)
Artist: Taylor Swift - 96kHz 24bit
Track: Love Story
Qobuz track stops playing and skips at 0:47
(I was going to report another one for The Alan Parsons Project, Eye in the Sky, Qobuz track Eye in the Sky, but it started working after a week or so just within the last 5 minutes)
I’m still having issues with playback from Qobuz. I play an album and if I switch songs mid stream I get errors or “playback was interrupted because a track failed to load”. This happens over and over and over…mostly just random BUT it never happens on Tidal I will repeat that Never. Is Roon ever going to admit this problem and fix it? I use Qobuz as my primary source but if I can’t I need to move on from Roon this is basic level service please fix it.
This has been acknowledged for months and the problem is with Qobuz, who are working on it, but different tracks and different locations are still affected differently. Roon asked to report affected tracks, their version, and your location here in this thread so that they can report them to Qobuz:
Speaking as a longtime software engineer, why isn’t Qobuz already collecting this information automatically?
It is standard practice in software development to log errors on the server whenever they occur. If an issue occurs during playback and skips the track, the code should be reporting it back to the server along with any relevant information for analysis. Qobuz should have a database that can be analyzed of all errors happening anywhere in the world. If this is not the case, then it is a major hole in their software architecture.
Don’t we agree it’s a bit unreasonable this day and age this won’t work? And I’m sure there is a lot of finger pointing. Just fix it. Simple. Easy button.
So now I have list each track this happens!? Will take up my entire day!
Here is latest:
Artist: ear
Track: Coil
Location: US
location : US
artist: ear
Track: coil
Please fix this already!
- I’m not arguing
- There is no finger pointing. The error mode as far as Roon and other third-parties who use Qobuz are concerned seems to be understood precisely: sometimes the streaming URL that Qobuz provides points to zero data on the Qobuz CDN.
- However, if this happens so often for you, I don’t believe that you are expecting this issue at all. For most others it is by now a quite intermittent to rare event. If I were you I’d open a new tech support case in Support > Get Help
- In any case, reporting it here in the user discussion category in Roon Software Discussion will have zero effect. It’s not being monitored by Roon staff. You’d have to go to thread I pointed you to. But see point #3 above.
Album, Version? (Usually it effects only a particular version, and tracks don’t exist just on one album)
this Qobuz track won’t play on roon but works fine direct on Qobuz
Artist: Pink Floyd
Album: Meddle 24bit/192kHz
Track: One of these days
Location: Melbourne, Australia
Please, go to the proper thread for reporting:
Here:
artist: ear
Album: Rumspringa
Version: Qobuz FLAC 96/24
track: coil (only this track)
Location: US
Can you tell me why the issue NEVER happens with Tidal?
Because Tidal is a different service than Qobuz. They are not at all connected, although they both can be streamed through Roon.
Because, if the issue you experience is the common known one:
This started after Qobuz reorganized their CDN (Content Delivery Network). Apparently, some of the files cached on the CDN contain zero data, so when Roon receives an streaming URL from Qobuz and tries to use it, there is no data (or broken data) there. Different CDN nodes serve different geographical regions, and this is why users in different regions are affected differently. (For instance, I myself have never run into the issue, but I’m in Germany).
It affects mostly the third-party services that use Qobuz (like Roon, but also others), and not so much the Qobuz app because Qobuz uses different servers for its own app and the third-parties. (Though sometimes the Qobuz app is affected, too). Qobuz has acknowledged this problem on their support forum, and they said that they have been purging their entire data cache, but perhaps this is ongoing or they have not fully fixed the root cause.
However, like I wrote, if this is super frequent for you, it might not actually be the same issue and opening your own topic via Support → Get Help might be better. It would probably still be a Qobuz server problem, but maybe not the same one. (For instance, occasionally it turns out that the internet routing from a particular user to the next Qobuz CDN node is broken, and this would be something that the user’s ISP may have to fix). The official support staff could find out exactly what the cause is, if you open a case.
Tidal is not affected by the Qobuz issue because, well, Tidal is not Qobuz and the Tidal servers don’t exhibit this Qobuz problem.
I absolutely agree. And the notion that users from all over the world should be continually sending individual reports on Qobuz playback failures is frankly hard to sustain. The instances are too many, the onus should not be on the end users and, obviously, a central mechanism for collecting these data should have been in place.