Hi, with this version in test mode with Qobuz Sublime, the issue seems to be resolved at least for 3 of the albums I encountered it before. Many thanks
Hi!
Can you please send me a log? Save it just after the issue
send to: techsupport at volumio dot org
Please report your post in the email text, thanks
Davide
3.233 new fixing build released!
See:
1 Like
I just start playing this album again and am waiting for playing will interrupt. I will send log directly from “Player state” (/dev)
!!IMPORTANT!!
Look at this:
Working on it!
Stay tuned for updates!
Sorry for the inconvenience
Davide
Volumio Tech Support
2 Likes
This release fixed my Qobuz issue, which would occur when I played the new Tears for Fears album. Playback would stop and had to reboot the raspberry pi as it seemed to be confused. This now no longer occurs! Thanks.
Unfortunately, there is even worse when playing this album using QOBUZ streaming: Open Qobuz Playing stops quickly (second or third title).
Regardless of where from Volumio is controlled - from Android or from PC.
But this tittle for example plays smoothly: Open Qobuz
What distinguishes it from the previous ones?
It is a multiple of 44.1 kHz, not 48 kHz.
Starting to have some doubt if this is strictly Volumio related.
Experience similar drop-outs using LMS+pCP (skipping/stalling/stopping)
Thanks, works perfekt… till now 
Same with BubbleUPnP to renderer other then Volumio…
Thanks for the feed-back:
So this issue is now confirmed with:
- Volumio
- LMS+pCP
- BubbleUPnP
@volumio
Found a different pretty annoying thing with the Qobuz integration, which I can only reproduce in Volumio.
When loading a playlist, enable randomize and skip 2-4 tracks (so songA >| songB >| songC >|
…), the integration get stuck and moves back to SongA. Audio get muted and interface (ManifestUI Coverview) stops responding. (Navigation buttons) The only way to get it working again, is going to the list view and select a new track, or click on the time bar. But then the played file is not in line with the coverview and the timebar is way off. Then it just start a song (guess the one it get stucked to). But then doing the same exercise, the whole interface get stuck again,
This is not related to Qobuz, but to Volumio. If I use the same playlist with LMS+pCP and do the same exercise, it just plays.
V3.233: http://logs.volumio.org/volumio/NmOrM1H.html
V3.236: http://logs.volumio.org/volumio/UTowsdo.html
info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current qobuz Received mpd
info: ------------------------------ 22ms
info: CoreCommandRouter::volumioPrevious
info: CoreStateMachine::previous
info: CoreStateMachine::updateTrackBlock
info: CorePlayQueue::getTrackBlock
info: CoreStateMachine::serviceClearAddPlay
info: CoreCommandRouter::serviceClearAddPlayTracks
error: WARNING: No clearAddPlayTracks method for service qobuz
info: CoreCommandRouter::volumioPrevious
info: CoreStateMachine::previous
info: CoreStateMachine::updateTrackBlock
info: CorePlayQueue::getTrackBlock
info: CoreStateMachine::serviceClearAddPlay
info: CoreCommandRouter::serviceClearAddPlayTracks
error: WARNING: No clearAddPlayTracks method for service qobuz
info: getStreamUrl took 5170 milliseconds
Thanks!
I’ll check it out today 
Davide
1 Like
I don’t have log yet, but want to report that playback is stopping from Radio Paradise as well… most of the times it lasts 20 minutes on my RPI 3b+ based streamer on 3.233
Should I try 3.236?
I would try this.
I updated an hour ago,
and it seems to be stable now.
3.233 didn‘t work for me too
1 Like
Unfortunately, my Primo still stops after an irregular time. Lastly lasted 11 movements of Mozarts Figaro. My Primo works as a bridge to an external DAC.
[image] there is still hope.
[imag
1 Like
“MuscLife” from ARCAM also couldn’t handle it.
But, my RPI setup (Squeezelite with LMS+pCP) dealt with this problem - not out of the box, but after little tuning it works: Buffer size settings - stream:output (99000:560000).
Plays non-stop from more then 24 hours.