1. Home
  2. digital
  3. 198553-90040

Qobuz still messed up

Takes forever to load upon start up and then stops, long pause, and then next song in playlist starts, or rather stutters, stops and the process is repeated. Pretty sure it's Qobuz and not Roon since it happens with both Roon and MConnect. Pity.

tcutter
macg19
1,387 posts
 

From 3 days ago, been back and forth on this for a couple of months with Marina from Qobuz. It’s way better now, only affecting a few tracks when player set to HD+

 

Report the track and streaming platform, it will help

 

There is a offical comunication from the tech team.

Some playback issues are currently affecting Qobuz, particularly when using certain applications or audio quality settings.

 

Our teams have identified the source of the problem. 

 

It is related to a caching anomaly within our content delivery network (CDN). In some cases, certain servers may temporarily deliver incomplete or corrupted audio files. As each audio quality corresponds to a different file, switching quality can sometimes resolve the issue by loading a correct version.

 

We are actively working on resolving this situation. Our teams are currently identifying the affected tracks and progressively clearing the cache. Improvements should be visible very soon.

 

We sincerely apologize for the inconvenience and thank you for your patience and understanding.

 
gkelly's avatar
gkelly
1,056 posts
 

Hank M. sax 🎷 is blowing just fine. 

tcutter's avatar
tcutter OP
415 posts
 

@erik_squires 

Thanks for the DNS tip. I cannot change my Xfinity router. I can on my various control devices (iPhone, iPad, etc). 

@macg19 

Thank you for the update from Qobuz. Wait and see I guess.

audphile1's avatar
audphile1
8,061 posts
 

@gkelly On jplay it fails. On roon it skips to next track. 
however, it plays directly from qobuz app on my phone and to my DAC. this points to API issues with renderers. 
jplay tells the renderer to go get this file from qobuz which triggers the api call. Roon will be performing the api call as well. 
 

when streaming using qobuz connect the renderer just becomes an end point to which the qobuz sends the data. 
another possibility why the file would play is if was cached. In example, it’s part of the Aurender conductor queue and was previously loaded into the cache. Pretty sure if the cache is cleared it won’t play anymore. 
Another possibility why it would work for some and not work for others is qobuz is steering requests to different cloud regions based on customer geographical location or other criteria. And there happens to be no issues with api calls in that region. 
 

It’s a qobuz issue and it is a repeat of the problem from 2 months ago. 

bassbuyer's avatar
bassbuyer
907 posts
 

Sorry to hear.  No issues here playing Qobuz at home, in the car and on the boat.  

More to discover