Thanks @SneakyPete
Interesting problem. I’m not seeing any issue in my region with my Bartok though.
The one thing I might recommend is that folks clear the cache in their Qobuz client app → Qobuz Client Settings page, Music Playing tab, scroll to the very bottom, and “Empty the cache”
By the way, just a couple of corrections to misconceptions posted in this thread;
- Qobuz Connect is not a Server, it’s a protocol.
- Qobuz content is delivered from the same servers regardless of whether you’re running Qobuz as a simple Client App, or pointing the Qobuz Client App to your DAC via Qobuz Connect. The streams come from the same source. The same applies to Tidal, and Spotify
- All streaming music comes from your local regional Content Distribution Networks (CDNs), not “Qobuz Servers in Paris”
- CDNs like Akamai, AWS CloudFront, and Fastly Edge Cloud. It’s possibly that a specific regional CDN cache of Qobuz’ content is corrupt while in other regions they’re not, but that’s generally highly unlikely as cache coherence to primary source is a fundamental function of these CDNs. Again, this is the same for Tidal and Spotify.
- Regardless of whether you’re playing back via Qobuz/Mosaic or Qobuz Connect, the streaming source is the same.
- If the two playback scenarios are showing different symptoms, that likely suggest you have some network communication issue somewhere - between your Qobuz Client and your DAC, or between your DAC and the Internet, or DNS resolution differences between your DAC and your Qobuz Client device, etc.
So all of the catalogue ( or catalogues) of recordings held for the various regions served by Qobuz are both held and distributed by the CDNs? I understand the latter operation but was ignorant of the former. I remember David Solomon then of Qobuz USA talking of setting up the servers prior to the USA service commencing including some mirroring from Paris. So he must have been incorrect.
Played some albums using upnp this evening but that red message that said the track could not be started did not occur. Sorry.
But I am 100 % sure it happened 2 or 3 times yesterday. Am also 100% sure I was using local upnp and not Qobuz. Maybe Mosaic did not get a reply from MinimServer in time? So could be a temporary glitch on my local network,can’t tell. And just to be clear,I only got that red message,which is from Mosaic I guess,and not an accompying one like you had. And the track played fine so I gave it not much thought. Anyway,I’ll keep an eye on it and see if I can recreate it on Qobuz if it happens again. Sorry,can’t be of more help.
1 Like
Yup, 100% of Qobuz’ contents streams to users from CDNs.
Not necessarily. There are a primary set of Qobuz Servers/Storage which serves as the primary source. Likely a couple mirrored across the globe for geo-redundancy and to reduce WAN traffic costs. This is what David Solomon was likely talking about.
The way it works is that when a new album is loaded onto Qobuz’ Servers/Storage and available on the Qobuz Client, the very first time someone tries to play that album, a CDN “cache miss” occurs, which forces the CDN to download and cache that album from the closest Qobuz’ Servers to that region. From that point onwards, all streaming of that album in that region occurs from that CDN.
All this happens completely transparently to us End Users. The way it works is usually through manipulation of the DNS records with geolocation information, which also enables Qobuz to control the various regional playback licensing restrictions.
By the way, this isn’t unique to music streaming services - when folks update their Apple iPhone iOS for example, you’re not receiving the iOS firmware update from Apple Servers, it’s actually coming from a local regional CDNs. Some content players build their own dedicated CDNs, like Netflix, Facebook etc.
1 Like
Today I received an email from Audirvana announcing the new 3.0 version of their software. I decided to visit their user forum and read some comments about the new update. People were complaining about having problems with Qobuz streams.
Me thinks this is not a dCS issue but rather a Qobuz one.
2 Likes
Morning Gregg
Late last night I did more tests.
I played the same album 16/44 version. Via Mosaic. No issues, played perfectly. 
Played the 24/96 version via Mosaic, definite issues. Would not play the first track, but skipped to track 2.
Using Kobuz Connect on iPhone 16. Same album using the iPhone as player/output. Played the album perfectly from start to finish.
I then switched the player/output to Bartók. Issues, would not play the first track!
Does this not point to an issue with my Bartók? 
Morning Anup
I’m thinking it’s A1, as that looks like the same Bot as I spoke to?
However, looks like you got more joy out of them than I did.
They promised that I could speak to a real human being, but I’ve not heard from them for 3 days now.
I have just posted some tests that I did last night.
Some things point to Qobuz, but some to dCS?
Probably not anything to do with dCS. Similar faults are reported on other brand forums such as Naim, Roon Labs etc. and non-brand related ones like Reddit.
1 Like
Good morning David,
I also see a similar issue with Wish You Were Here on Qobuz.
When I try to play either the whole album or just the first track via Mosaic I get the red banner with the “Failed to start playback” message but the track does play. Interestingly my Bartok and Mosaic report that it is 24/96 rather than 24/192. The remaining tracks 2-5 play without issue and at 24/192.
When I try to play the album via Qobuz connect with my Bartok as the player it jumps to the second track. However if I limit the sample rate to 96kHz then the album will play without issue from the first track.
I suggest that there is an issue with the 24/192 version of track 1 that the Bartok cannot handle and that this is a Qobuz problem rather than a dCS issue or an issue specific to your Bartok.
I hope that helps.
1 Like
Wow, thank you David.
What you have said is a 100% mirror of what I get.
Thought I was going nuts!
Thanks
Found another album where this occurs. You can already notice something is wrong there, just the second track is marked as high res, and it’s the only one which plays correctly, with the other two I get the well known error.
1 Like
Checked this on Qobuz UK I am seeing all tracks as hi-res I.e. 24/44.1. I am guessing that you subscribe to Qobuz in a different territory. Qobuz has a different catalogue for each country it adds due to rights issues.
Your issue is different from the other Qobuz problems reported here with only one movement (track) showing as hi-res. I had a similar instance some years ago. In that case the record company provided a pre- release taster in MP3. When the record came out it was replaced by the proper 24/96 version. At least that was the intention. However the record label only sent a replacement for the first track ! Something similar may have happened here for your version of the service.
Clara is the Qobuz support bot (which I have found to be surprisingly good).
1 Like
It was very helpful. But I’m still waiting the promise of speaking to a human being.
Im Swiss, and obviously subscribed as such.
Hello David,
If you tell the Qobuz AI Assistant that you wish to be contacted by a real human, you will be contacted by email within 2 days (at least in France - my recent experience with a download issue for a title I purchased; and they solved my problem BTW).
1 Like
Hiya Erwan… That is what I requested and was promised 3 days ago, not heard back just yet.
Thanks. Love your Wagnerian moniker 
.