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

@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.

@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. 

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

@bassbuyer it’s not that Qobuz doesn’t work at all. It’s only certain tracks that won’t play  and there are no issues playing from qobuz app.