Qobuz still messed up

for more details, from the Jplay thread April 9 2026:

Hi everyone,

I wanted to share an update on the Qobuz playback issues that many of you have been experiencing over the past two weeks or so. To be clear upfront: this is a Qobuz-side issue, not a JPLAY bug. I’ve been receiving a lot of support requests about tracks that won’t play, playback stopping mid-album, "error sending action to renderer" messages, and similar symptoms — and they all trace back to the same root cause.

Qobuz has officially confirmed the incident to their partners. Here’s what they shared initially:

"We have identified a technical issue affecting the availability of certain audio files on our API. The problem specifically concerns files larger than 50MB. It results in a size mismatch error between the requested and received data, linked to a partial object caching issue. Our technical team is currently investigating to identify the root cause and the scope of impacted files."

And an update from yesterday:

"We have identified the source of the playback errors: it is a caching anomaly with our CDN provider. In practice, some distribution servers are hosting a corrupted or incomplete file. Since each audio quality corresponds to a separate recording, switching quality often allows you to fall back on a healthy file and work around the issue. Our teams are currently listing the affected tracks and carrying out a gradual cache purge. The situation should be resolved very shortly."

A few practical takeaways:

- The issue mainly affects files larger than 50MB, which is why hi-res tracks (24/96 and above) are hit the hardest while CD-quality content is mostly unaffected.

- As a workaround, switching the streaming quality from 24/192 to 24/96 or even 16/44 (CD) can often help — each quality level is a separate file on Qobuz’s CDN, so a different quality may give you a healthy copy.

- Qobuz is performing a gradual cache purge, so affected tracks should start working again progressively over the coming days. (fingers crossed)

- There’s nothing we can fix on the JPLAY side — this needs to be resolved by Qobuz at the CDN level.

Thanks everyone for your patience. I’ll post another update once Qobuz confirms everything is back to normal.

Marcin

Interesting.  Last month, I had issues with Qobuz stopping/fluttering, but only when playing Hi-Res tracks.  The issue had nothing to do with Roon (Roon Nucleus Plus), or my network.  The issue was solely a Qobuz issue.  There was absolutely nothing I could do on my end to resolve the issue.  I was totally helpless.  Apparently, there was some kind of a short lived glitch with Qobuz that caused the issue.  Thankfully, after a relatively short period of time, the issue resolved itself and just disappeared.  I've had no further issues since.  Happy listening.          

I dumped Qobuz

From time to time Qobuz stops streaming, then about 10-15 seconds later it starts again.  I don't know why.  It doesn't happen every dayI guess it depends upon how long I'm listening.  If it's on at home for several hours it will stop and start.  

Is this the same problem that’s causing the “EOB” error I occasionally get on the BluOS app ? Ozzy’s “Bark At The Moon” wouldn’t play. The only song that wouldn’t play in my session today.