Qobuz still messed up

A track i consistently have trouble with is this one :

"String Quartet No. 36 in B-Flat Major, Op. 50 No. 1, Hob. III:44: III. Minuet" track from "Haydn: String Quartets, Vol. 7" by "Auryn Quartet"

https://open.qobuz.com/track/303444517

Open it on JPLAY: com.jplay.jplay://qobuz/album/jtljht9c2ewtc

The music stops at about 2 min 16 secs; the app thinks it is still playing: goes to the end with silence on the speakers and then the music resumes when the next track plays.  

I’d appreciate it if anybody is willing to try playing that track and to let me know if they have the same issue or not.

@kirkwallace 

I just tried this track and the sound stopped at 1:55. (Qobuz, Jplay) I see the time elapsing a bit after that with no sound, then jumps back to 1:55, then just stops at the beginning of the track. 

I get this with other tracks as well, and switching from Squeeze to Roon to Jplay doesn’t change the outcome. 

Yesterday put on Elton John Madman across the water, hi res, all tracks played just fine except the one I wanted to hear most, the title track. Tried several times and it would not start at all, switched to the redbook version and that played no problem. Today no issues with that album. 

@marcin_gps logs sent. 

@mclinnguy So it’s not just me!  Thanks for running that test.

@Marcin, tried twice this morning and the problem persists today so i have sent the logs and description to [email protected] as you suggested.

BTW, this Haydn track continues to work fine on Roon now.

@audphile1 i haven’t retried BluOS yet today.  Hope to do that later. 

@kirkwallace 

Pretty much confirms if 2 people have the same issue in 2 different places it is not individual network issues. I think. 

@audphile1 

I’ve not had a Qobuz issue since they resolved it couple of months ago. I’m on the east coast. Very possible though that the west coast is served from another cloud region and that is where the problems still persist. 

Is that how it works? Are there multiple servers each with its own database that serve various geographic regions, and maybe each server needs to flushed of the corrupted files? @marcin_gps could you confirm? 

@macg19 

Yours is not the first time Qobuz says it wants feedback and they will fix the problem, but I thought they declared they had already fixed the problem weeks ago. Gives me a sense that this is just lip service to make it look like they're working on it.

The second concern I have is that it sounds like they're asking us to identify individual tracks which they can then perhaps fix on a piecemeal basis. Kind of reminds me of the Roon approach as they depend on their customers to make things work. It's one thing to appreciate customers' input, it's another to depend on it. They should be able to figure this out and fix it on their own. And since I have no problem with Spotify and others say they have no problems with Tidal, it seems to be a weakness with Qobuz.  They need better code.