[IDEA] Streaming from Qobuz native app

[roderickvd]

Another thanks for the latest donations!

Today I've managed to parse the first message after registering the device. This message pushes the initial state to us: loop mode, playback mode, the renderer ID assigned to us. A significant step, because that means I've got the fundamental incoming message format figured out.

Enjoying the banter about the names 

[Tim Curtis]

Why is Qobuz called Qobuz?
https://www.qobuz.com/us-en/about#:~:tex...Kazakhstan.

[Snoil]

Why is Qobuz called Qobuz?
https://www.qobuz.com/us-en/about#:~:tex...Kazakhstan.

"...Linked to the shamanic ritual, and therefore endowed with supernatural and magical powers so as to ward off evil spirits and disease..."
very audiophile!

[Christophe999s]

I've spent a few hours digging into Qobuz Connect and it looks doable to build a headless player for it - along the lines of librespot or pleezer.

No promises yet, but I'll start exploring it further. If you'd like to support the effort, I'd appreciate sponsorship at https://github.com/sponsors/roderickvd. It'll help cover the Qobuz subscription and tools needed for protocol analysis and development.

Hi, made a little donation to support your work!

[roderickvd]

Hi, made a little donation to support your work!

Thank you for donating.

I have begun chugging away at the messages. Meanwhile, I'm changing the codebase to accommodate for differences in the way Deezer and Qobuz handle things. Right now I'm in the middle of some major renovations to the queue ("the playlist") and track metadata. Interesting: the tracks have ReplayGain metadata for normalization, but the official apps don't seem to support that yet. This one will, of course!

[Snoil]

Hello @roderickvd
will the upmpdcli Qobuz plugin play a roll in "well hello there" or will it "just need upnp" (if that makes any sense..)?

[roderickvd]

They are separate projects and will continue to be.

[Snoil]

ok thank you. I obviously dont know a thing about all of this but I was curious because (as in your screenshot) in audio output/network devices (now) other instances of the native qobuz app ( I presume that's whats happening on that iPhone) are shown. I thought maybe well hello there will recognize upmpdcli Qobuz plugin as 'standalone' Network device.
Anyways, again, just curious.

[roderickvd]

UPnP and Qobuz Connect are quite distinct.

UPnP is a universal protocol on local area networks for registration and discovery of network services. As far as I understand, upmpdcli registers itself on the network as a UPnP audio renderer, that feeds into mpd for actual audio playback. Then you can use an app like BubbleUPnP which has its own Qobuz integration, can discover upmpdcli on your network using UPnP, and send track URLs to it for playback.

Qobuz Connect is a Qobuz native protocol. Qobuz Connect devices connect to the Qobuz servers, where they keep the playback queue and progress synchronized between all devices. Official Qobuz apps can select which Qobuz Connect device becomes the active renderer, and control them remotely.

With what I'm creating, moOde (or anything else) also becomes a Qobuz Connect device that you control directly from an official app.

[Snoil]

...quite distinct...
Qobuz Connect is a Qobuz native protocol. Qobuz Connect devices connect to the Qobuz servers, where they keep the playback queue and progress synchronized between all devices....

thank you for taking the time to clear that up for me.