Typing “pause” gives an error “an error occured since reading the track” and jumps to the next track (in volumio UI, no error but skips to The next track).
For me, Multiroom Off causes pause to stop working in Qobuz Connect, and.turning Multiroom On fixes it (as described in the thread I linked). If Multiroom On causes other problems, then Volumio have a bigger problem to fix.
Thanks for your help.
Indeed, Multiroom was off.
Setting it on solves the problem.
I dont understand what’s the connection between Multiroom and Qobuz connect but it’s a fact.
I think that Multiroom Playback doesn’t have a direct connection with Qobuz Connect, but has a side effect that allows it to work. My speculation is that playback commands sent to the Qobuz Connect endpoint operate with a bit of delay, and it may be receiving a new command before the previous command has completed, causing errors. Multiroom Playback has a couple of delay buffer parameters, and the delay it adds may be allowing Qobuz Connect to work properly.
In the case of @egal, he is using FusionDSP which is processing intensive and may introduce a delay of its own, but in combination with Multiroom Playback may interfere with Qobuz Connect.
Interesting. I never have multiroom switched on, and I use Qobuz Connect for 90+% of my listening. I’ve never seen this problem.
But I have a very basic setup - just a headless RPi4b feeding a USB DAC, and only 3 plugins, Bandcamp, Music Services Shield, and System Info. Maybe if you provided logs, one of the experts on the forum would be able to figure it out.