Qobuz Setup

[tetchey]

Is there a guide/howto available for how to integrate Qobuz with moOde?

Looking over the forums, I get the impression that it can be done but requires BubbleUPnP and installing some extra packages on the moOde server. I understand this is less than ideal, but I wanted to give it a try.

Is this documented somewhere?

[TheOldPresbyope]

Is there a guide/howto available for how to integrate Qobuz with moOde?

Looking over the forums, I get the impression that it can be done but requires BubbleUPnP and installing some extra packages on the moOde server. I understand this is less than ideal, but I wanted to give it a try.

Is this documented somewhere?

Not sure what you expect here.

As it happens, moOde includes a UPnP renderer. The software that implements this renderer is upmpdcli.

If one edits the file /etc/upmpdcli.conf to include one's Qobuz credentials, then a UPnP control point, of which BubbleUPnP is just one example, can access Qobuz (via the upmpdcli proxy) as if it were a local UPnP media server. 

Note that BubbleUPnP, in particular, can also access Qobuz (and TIDAL) directly. They're listed in the BubbleUPnP library under "Cloud". 

If you already use UPnP control points, UPnP media servers, and UPnP renderers in your LAN then this might be a convenience, but I prefer siimply to use the Qobuz app on my phone or tablet and stream the tracks to moOde via Airplay or Bluetooth. 

Granted, there are technical differences in the different approaches. These differences have been discussed in the moOde forum before.

Regards,
Kent

[Tim Curtis]

I see the entries below in upmpdcli.conf that reference Music Services.

Code:

# IP port for the tidal/qobuz local HTTP service.

#plgmicrohttpport = 49149

Code:

# Highresaudio streaming service parameters

# Hra user name.
#hrauser = your hra user name
# Hra password.
#hrapass = your Hra password
# Hra language setting (en/de).
#hralang = en

# Qobuz streaming service parameters

# Qobuz user name.
#qobuzuser = me@some.place
# Qobuz password.
#qobuzpass = agoodpassword
# Qobuz stream quality.
#qobuzformatid = 6

# Deezer streaming service parameters

# Deezer user name.
#deezeruser = me@some.place
# Deezer password.
#deezerpass = agoodpassword

It's relatively easy to add input fields for these services to UPNP Config but I would need requirements for example the validation formats and ranges for the items, and any additional packages that need to be installed to support or enable the services.

And most importantly a way to test and verify that each of them actually works before any code is written. I don't have subscriptions to any of these services so this part would need to be done by others.

[TheOldPresbyope]

Ah, it's been so long since I dived into the UPnP morass that I'd forgotten the upmpdcli-qobuz package is needed for Qobuz. Fortunately it's available in the Debian repo.

Hence, the usual

Code:

sudo apt install upmpdcli-qobuz

From the upmpdcli manual

Qobuz streaming service parameters

qobuzuser

    Qobuz user name. Your Qobuz login name.

qobuzpass

    Qobuz password. The password for your Qobuz account.

qobuzformatid

    Qobuz stream quality. 5 for mp3/320, 6 for FLAC, 7 FLAC 24/96, 27 for hi-res (if your subscription allows streaming each of the formats).

I edited my credentials into /etc/upmpdcli.conf and set qobuzformatid = 6. 

I went to moOde Renderers config view and enabled the UPnP Renderer.That was sufficient to be able to access Qobuz via UPnP using mconnectLite on my iPad.

Note that the proper setting for moOde's UPnP service type (UPnP-A/V versus OpenHome) depends on the UPnP Control Point being used (bletch!).

I cannot comment on any other streaming service accessible via upmpdcli. Quoting again from the currrent upmpdcli docs

Streaming Services

The Media Server function in Upmpdcli gives access to external streaming services: Highresaudio and Qobuz currently work fine (1.6.2).

The Deezer plugin works for low quality (but still usable) streams (128 kb/s mp3).

You will need a valid subscription for any service that you want to use.

...

NOTE: I have no reason to believe that upmpdcli is technically mis-using the streaming services in any way, but it is definitely not approved by any of them, and you are using it under your own responsibility.

As I said before, unless one is already using  UPnP because of other equipment, the extra fiddlefaddle seems unnecessary. All of the streaming services offer apps for the same devices I'd use to run a UPnP Control Point and moOde already offers Bluetooth and Airplay renderers. It doesn't help that the history of services disabling access from opensource programs is troubling.

Different strokes for different folks, I guess.

Regards,
Kent

[TheOldPresbyope]

FYI,

Here's two screen shots from my iPad using mconnectLite as the UPnP Control Point.

The first shot shows the mconnectLite Library menu, e.g., the Browser, which includes both the direct access to Qobuz and TIDAL, under Internet Music and access to my moOde player UPnP Media Server (hostname sunroom) under Local Server.
   

The second shot shows the mconnectLite play view after drilling down through Qobuz to select a track and also selecting the moOde player in the Play To menu (otherwise you get the Airplay renderer cuz this is an iPad).
   

Regards,
Kent

[Tim Curtis]

Is this thread still relevant?
https://moodeaudio.org/forum/showthread....ight=qobuz

There was never any conclusion as to whether the qobuz package and moOde-side qobuz credentials were actually needed, and which client app was being used bubbleDS or bubbleupnp.

I see you are using mconnect and not any of the bubble aps. Does it even have a way to enter qobuz credentials client-side or does it require them to be entered on the renderer i.e. moOde upmpdcli?

We do have the upmpdcli-qobuz=1.7.7-1moode1 package in our repo but it's not currently part if the image build.

[TheOldPresbyope]

Is this thread still relevant?
https://moodeaudio.org/forum/showthread....ight=qobuz

There was never any conclusion as to whether the qobuz package and moOde-side qobuz credentials were actually needed, and which client app was being used bubbleDS or bubbleupnp.

I see you are using mconnect and not any of the bubble aps. Does it even have a way to enter qobuz credentials client-side or does it require them to be entered on the renderer i.e. moOde upmpdcli?

We do have the upmpdcli-qobuz=1.7.7-1moode1 package in our repo but it's not currently part if the image build.

That thread is relevant only in the sense that it states upmpdcli-qobuz is required.

Looking at apt-cache I see I actually loaded our own package (I thought it came from the Debian repo cuz the upmpdcli docs say it's available there)

Code:

pi@moode:~ $ apt-cache show upmpdcli-qobuz
Package: upmpdcli-qobuz
Source: upmpdcli
Version: 1.7.7-1moode1
Architecture: all
Maintainer: Jean-Francois Dockes <jf@dockes.org>
Installed-Size: 68
Depends: upmpdcli, python3, python3-requests
Section: contrib/sound
Priority: optional
Homepage: http://www.lesbonscomptes.com/upmpdcli
Description: upmpdcli Qobuz plugin
upmpdcli-qobuz allows upmpdcli to proxy access to the Qobuz music
streaming service.
Description-md5: aa0a3edae5a2605ca215f053c2b9dd5a
Filename: pool/bullseye/main/u/up/upmpdcli-qobuz_1.7.7-1moode1/upmpdcli-qobuz_1.7.7-1moode1_all.deb
Size: 19892
MD5Sum: 704126378c1e8d6f06b1630063652bf7
SHA1: abbbcb353e7b7f016c739f975c06411038b95d44
SHA256: 8b2fab754854883ecc1bfb944b1cc7e3bdf08cffa4974fd6a2ac55f03125b6d2

Yes, I used mconnectLite, It turns out they too now offer a direct connection to Qobuz "in the cloud" the same way BubbleUPnP does.

If one wants moOde (via upmpdcli and its plugin) to be the proxy Media Server for Qobuz, then one must enter one's subscription credentials in /etc/upmpdcli.conf.

If, instead, one is using an appropriate Control Point app and wants the remote Qobuz servers to be the Media Server, then one must enter one's subscription credentials in the App.

In my opinion, the user interface is better using the second option and best of all using the native Qobuz app instead of either option, but to each his own.

Regards,
Kent

[Tim Curtis]

Is this thread still relevant?
https://moodeaudio.org/forum/showthread....ight=qobuz

There was never any conclusion as to whether the qobuz package and moOde-side qobuz credentials were actually needed, and which client app was being used bubbleDS or bubbleupnp.

I see you are using mconnect and not any of the bubble aps. Does it even have a way to enter qobuz credentials client-side or does it require them to be entered on the renderer i.e. moOde upmpdcli?

We do have the upmpdcli-qobuz=1.7.7-1moode1 package in our repo but it's not currently part if the image build.

That thread is relevant only in the sense that it states upmpdcli-qobuz is required.

Looking at apt-cache I see I actually loaded our own package (I thought it came from the Debian repo cuz the upmpdcli docs say it's available there)

Code:

pi@moode:~ $ apt-cache show upmpdcli-qobuz
Package: upmpdcli-qobuz
Source: upmpdcli
Version: 1.7.7-1moode1
Architecture: all
Maintainer: Jean-Francois Dockes <jf@dockes.org>
Installed-Size: 68
Depends: upmpdcli, python3, python3-requests
Section: contrib/sound
Priority: optional
Homepage: http://www.lesbonscomptes.com/upmpdcli
Description: upmpdcli Qobuz plugin
upmpdcli-qobuz allows upmpdcli to proxy access to the Qobuz music
streaming service.
Description-md5: aa0a3edae5a2605ca215f053c2b9dd5a
Filename: pool/bullseye/main/u/up/upmpdcli-qobuz_1.7.7-1moode1/upmpdcli-qobuz_1.7.7-1moode1_all.deb
Size: 19892
MD5Sum: 704126378c1e8d6f06b1630063652bf7
SHA1: abbbcb353e7b7f016c739f975c06411038b95d44
SHA256: 8b2fab754854883ecc1bfb944b1cc7e3bdf08cffa4974fd6a2ac55f03125b6d2

Yes, I used mconnectLite, It turns out they too now offer a direct connection to Qobuz "in the cloud" the same way  BubbleUPnP does.

If one wants moOde (via upmpdcli and its plugin) to be the proxy Media Server for Qobuz, then one must enter one's subscription credentials in /etc/upmpdcli.conf.

If, instead, one is using an appropriate Control Point app and wants the remote Qobuz servers to be the Media Server, then one must enter one's subscription credentials in the App.

In my opinion, the user interface is better using the second option and best of all using the native Qobuz app instead of either option, but to each his own.

Regards,
Kent

Ok, got it.

I'll add to the TODO list to update UPNP Config and include the qobuz package.

[tetchey]

I prefer siimply to use the Qobuz app on my phone or tablet and stream the tracks to moOde via Airplay or Bluetooth

Thinking about it, this is exactly what I was after. I didn't really want or need the UPnP stuff, I just wanted to be able to stream Qobuz to my stereo via moOde.

Thank you for the idea.

[masari]

Wouldn't audio quality suffer? Why pay all that money for streaming 24 bit 96Khz or higher when those bits are not going directly into your DAC?  It's certainly a great option for parties where guests might want to connect to your system simply and easily.

I was seeking a way to connect Moode and Qobuz as well, and am confused as you are with the uPnP information out there