Qobuz still messed up

Realized I described virtually the same phenomenon when I started this thread on 5/25. Clearly a slow learner...

"The Rain Song on Houses of the Holy at 96K" plays perfectly from start to finish.

One of my favorite Zep tracks and albums btw.

The version I just played was from "Houses Of The Holy (HD Remastered Deluxe Edition)"

@tcutter I am pasting here a response i got from @marcin_gps after i submitted the logs to JPLAY about that Haydn String Quartet track.

”The track you’ve identified ("String Quartet No. 36... III. Minuet" by 
Auryn Quartet, track ID 303444517) is the exact same track another JPLAY 
customer reported trouble with recently — on completely different 
hardware. In both cases, the stream stalls partway through, the renderer 
loses sync while JPLAY still thinks it’s playing (matching what you 
describe — it runs silently to the end, then the next track kicks in), 
and in both logs Qobuz’s own metadata for this specific track carries a 
"FormatRestrictedByFormatAvailability" flag.

In your log specifically, JPLAY repeatedly fetches a brand new stream 
URL from Qobuz (fresh token each time) and restarts the track, yet it 
consistently stalls around the same point (roughly 1:41) no matter how 
many times it’s retried. Two different customers, two different 
renderers, same exact track stalling — that’s about as clear as it gets 
that this is a problem with how Qobuz’s CDN is serving this specific 
file, not a JPLAY, renderer, or network issue on your end.

A couple of things worth trying in the meantime:
1. Switch the track’s streaming quality (e.g. to CD quality) and back to 
hi-res — this sometimes forces Qobuz to re-serve the file from a 
different source.
2. Try again after some time — CDN-level glitches like this are usually 
resolved on Qobuz’s end without any action needed.

Given we now have two independent reports on the exact same track ID, I 
think this is worth reporting directly to Qobuz as a broken/truncated 
stream for that specific track. I’ll flag it on our side as well.”

interestingly, after I submitted the logs, it seemed like Qobuz had fixed the issue without my doing anything.  The track played fine.  But i went back to check it today and BINGO same exact problem. (I tried 3 times to be sure.)  I have now reported it to Qobuz, to the chat bot that pops up when you click on Support, including an Activiity Report; you can only generate an Activity Report however from the app on a Mac or PC desktop or laptop.  It can’t be done from phone or tablet, which is annoying.

@kirkwallace Thanks for posting, that other customer was me of course, and I did not get the same response from Marcin directly, but I more or less pointed him to this thread, so all good. 

For others reading this (and for @marcin_gps) it was confirmed kirkwallace and I are both on the West coast of North America, so those on the East coast, or other global areas may have different Qobuz behaviour if this different cloud delivery for various regions hypothesis is accurate. Yet a sample of data which throws a wrench in this is that Marcin said he had the same issue, and he is in Europe... (?)

 @tcutter 

Qobuz. Still not ready for prime time. Expires 10/27/26. Have to remember to cancel.

That is about the same time for my renewal also, and I will cancel as well and go with Tidal for a year. Maybe by November 2027 the issues Qobuz are having will have been resolved by then.

Bloody shame, I do like Qobuz more but I am fed up. 

@mclinnguy thank you for reporting it to JPlay; it helped to have both experiences in front of them; and i suspect my having reported it to Qobuz at the same time (roughly) as JPlay did will result in a swift fix.  

I’m not ready to give up on Qobuz just yet; they have some tracks and formats that TIDAL doesn’t. I like having both. No product is always perfect 100% of the time, and it does seem like they are monitoring the problems and quick to act.