Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Problem: Qobuz render doesn't work anymore
#17
So I finally realized @magostinelli  is not talking about the BubbleUPnP (for DLNA protocol) app; he's talking about the BubbleDS (for Linn DS.OpenHome protocol) app. Same group of devs; different apps exercising different code paths in upmpdcli. The clues were the specific configuration setting he referenced (which is not in BubbleUPnP) and the hint that he's working with multiple Qobuz tracks in the queue on the moOde player (which is an OpenHome thing).

The moOde project is at the mercy of the whims of the powers-that-be at Qobuz and the coding skills of the upmpdcli devs. I suggest @magostinelli  post his issue to the upmpdcli gitlab site (https://framagit.org/medoc92/upmpdcli). Be sure to include device, version, and settings information as I do below. Note that this is not the first time such an issue concerning BubbleDS and Qobuz has been raised. There was one 11 months ago that got addressed (apparently a coding error in that case).

ETA - There was an issue against upmpdcli-qobuz a month ago which identified a code modification needed to accommodate a change Qobuz made. That modification is present in my moOde player. Perhaps somehow the OPs moOde update from whatever to 8.3.2 didn't include the modified file? (/usr/share/upmpdcli/cdplugins/qobuz/api/spoofbuz.py)

---

FYI -

ATM I'm running *unlicensed* BubbleUPnP 3.8.0.3 arm64-v8a) on my Pixel 6a phone (Android 13). For testing moOde's UPnP capability, I'm running moOde 8.3.2 on a Pi3a with a Creative Tech USB-BT transceiver driving my wireless Sennheiser headphones.

Test 1-
  • enable moOde UPnP Renderer (named 'test UPNP') in UPnP-A/V service mode.
  • set BubbleUPnP to use 'test UPNP' as its Renderer.
  • set BubbleUPnP to use Qobuz as its (Cloud) Media Server.
  • I am able to browse the Qobuz offerings in the usual top-down mode and play selections through moOde to my headphones. The URLs of the tracks reference the phone IP
Test 2 -
  • install the upmpdcli-qobuz package per post #13
  • insert my Qobuz subscription credentials in /etc/upmpdcli.conf [note- stored in plain text! Yuck.]
  • restart renderer
  • set BubbleUPnP app to use 'test UPNP-mediaserver' as its (Local) Media Server
  • I am able to browser the Qobuz offerings and play selections as before. The URLs of the tracks reference the moOde player IP. The UI looks slightly different and its response seems a bit more sluggish, but the Miles Davis tracks I'm listening to sound the same.
There is no BubbleUPnP issue apparent to me.

Regards,
Kent
Reply


Messages In This Thread
RE: Qobuz render doesn't work anymore - by bitlab - 05-09-2023, 12:07 PM
RE: Qobuz render doesn't work anymore - by bitlab - 05-09-2023, 04:22 PM
RE: Qobuz render doesn't work anymore - by TheOldPresbyope - 05-18-2023, 08:29 PM

Forum Jump: