I'm running Upmpdcli on different Raspis with BubbleUpnP as controlpoint. After upgrading to 1.4.5 the renderer stops playing music when i select a differnt renderer in Bubbleupnp. Any idea what cloud be wrong?
What version were you upgrading from ? I have no idea what could cause this, only the control point can tell the renderer to stop, so it's probably a joined upmpdcli-bubble issue.
I would need to have a look at the debug log for the renderer which stops (use loglevel=4 in /etc/upmpdcli.conf, and set some file name or keep stderr and just use journalctl)
You seem to have CSS turned off.
Please don't fill out this field.
please find attached logfile
I see no file attached :) You can also send it by email if you have trouble with the site, which is sometimes a bit flaky. email@example.com
From the log, and for some unknown reason, bubble upnp controls upmpdcli as an UPnP/AV not an OpenHome renderer. So the playlist will stop anyway if the control points switches to another renderer (as the UPnP/AV playlist is controlled by the CP). Also I see a pause command, probably bubble sends it when it switches.
Check that you have openhome = 1 in /etc/upmpdcli.conf, and you could possibly try to set upnpav=0 too to see if it fixes the issue.
If this does not work, you should contact bubble, I don't know what's happening there.
This may have something to do with the Qobuz trouble, but this way of doing things should not be the default, only when using qobuz. You're not using Qobuz by the way ?
I configured Upmpdcli upnpav=1 openhome=0 because with openhome=1 authentication from BubbleUpnP to Tidal and Qobuz doesn't work with upmpdcli 1.4.5. But with upnpav=1 openhome=0 and upmpdcli 1.4.5 the renderer has the initially described problem to stop if I change the renderer. Older version of upmpdcli don't stop when changing the renderer. I have found out that with upnav=1 and openhome=1 I have to install upmpd-tidal to get authentication from Bubble to Tidal working. Login from Bubble to Qobuz seems to work. Somehow confusing for me
Upmpdcli can't work directly with Qobuz any more, because Qobuz revoked all the pubicly known access keys.
Effectively, the only way to play a Qobuz track on upmpdcli is to use a separate gateway, for example letting bubble upnp manage the streaming. For this to work, upmpdcli has to be accessed in upnp/av mode because the playlist must be managed from the place which controls the Qobuz access.
As far as I know, Tidal streaming still works fine, both when accessed through the upmpdcli media server, and when logging it with the openhome credentials (as happens when you select "Tidal" in Kazoo). I have not checked with bubble, but I just verified that this worked fine in Kazoo, so, if it does not in Bubble, it is a Bubble issue.
Finally, it is quite normal that the UPNP/AV playing will stop some time after the CP disconnects, because the CP is in charge of loading the next track from the playlist it manages. Depending on the CP, this can happen at once (it appears that Bubble sends a Pause command), or later on, when the current track, or possibly the next, finishes. Of course, if the CP is also the data source (like would be the case with Bubble gatewaying Qobuz or Tidal), then it is quite natural (but not absolutely mandatory) that the playing would stop at once when the CP switches to another renderer.
You can refer to the "Streaming services and UPnP" section in the manual for a bit more detail
I need to update the manual concerning the Qobuz situation by the way...
Closing this as there is nothing more to be done.