bubbleguuum Posted October 5, 2019 Share Posted October 5, 2019 The problem is indeed that upmpdcli had its Qobuz ids revoked to access the API (it was XBMC/Kodi credentials) for the OpenHome renderer. So the solution is to either to: - use upmpdcli as a regular UPnP AV renderer with a Control Point that has its own Qobuz support (mconnect, BubbleUPnP). This will not work with OpenHome Control Point such as Kazoo - make upmpdcli an OpenHome renderer with BubbleUPnP Server as described in https://audiophilestyle.com/forums/topic/27851-sonicorbiter-tidalqobuz/?tab=comments#comment-880956. This works with OpenHome Control Points such as Kazoo Next update of Android BubbleUPnP will have a workaround for being able to play Qobuz to upmpdcli as an OpenHome renderer, but using the app's own Qobuz support rather than through upmpdcli Qobuz OH support that is now not functional Cebolla 1 Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now