[IDEA] Streaming from Qobuz native app

[Nutul]

If you’re into C, I think you’re gonna love Rust.

I definitely must give it a chance, then. Thanks for the contribution to my knowledge; I'll be more than happy (although Jorge Carlin would have something to say about being "more than happy"...) to try something with it. I'll let you know how my experience gets up with it, for sure.

[Aldebaran66]

Hello folks. As Qobuz connect is now out since May this year, any integration perspective in moode soon?
It is integrated in Volumio yet.... but I prefer MoodeAudio personaly....

[the_bertrum]

Hello folks. As Qobuz connect is now out since May this year, any integration perspective in moode soon?

This whole thread is literally about the efforts that @roderickvd is making towards a Qobuz connect solution.

It won't speed things up, but if you chuck a donation his way it will help encourage things.

[Aldebaran66]

Hello folks. As Qobuz connect is now out since May this year, any integration perspective in moode soon?

This whole thread is literally about the efforts that @roderickvd is making towards a Qobuz connect solution.

It won't speed things up, but if you chuck a donation his way it will help encourage things.

I did a donation already....I hope this will help... ;-)

[roderickvd]

In my previous update I spoke about working on Rodio, an audio playback and processing library that pleezer and the upcoming Qobuz player depend on. v0.21 has just been released and we're doing some mop-up now as the library is being picked up by the rest of the open source community.

After that mop-up release, I plan to do a point release for pleezer. Yes, Deezer Connect is still working on iPhones and Android devices too when you've got an older APK. I'll update it with Rodio and do a few quick fixes. Who knows, maybe it'll be the last version before it goes to the archives.

Summer holidays are arriving. I have kind of a personal goal - but no promises! - to publish a repo before I go on holidays with an alpha (!) version of the upcoming Qobuz player that can play music. DO NOT expect this to be integrated into moOde yet: major work will need to be done yet to make it do anything more beyond just playing some music (like: seeking, shuffling, sample rate changes, and so on, and so on).

Whether I'll bring my laptop with me, and whether I'll be able to get some development time in, no idea. That's why anyway it'd be cool to make the next step before I go: downloading a music file and getting it to play remotely.

[TheOldPresbyope]

Unsolicited advice from an old guy who spoiled more than one vacation because he brought work along---leave the laptop at home!

The progress you've been making is awesome. Take your time and do it right. I can keep holding off resubscribing to Qobuz until the moOde plugin is in the testing phase.

Regards,
Kent

[voorstad]

I have a temporary subscription for Qobuz, to test the replacement of Spotify. Looks promising, but indeed Qobuz connect (for Moode) and the absence of lyrics are the current setbacks. Let's see how this progresses.

@roderickvd , is donating via Github the only way? If there is a more privacy friendly way, that would be welcome.

[roderickvd]

@roderickvd , is donating via Github the only way? If there is a more privacy friendly way, that would be welcome.

It's the only one I've got set up right now. Which one or two would you propose?

[Tim Curtis]

Will authentication (secrets file) and metadata (event script + env vars) be the same as for Spotify and Deezer Connect?

If yes I can start coding the Qobuz Connect framework. There are a lot of moving parts and so quite a bit of work.

[roderickvd]

Mostly. This is what I've currently got as secrets.toml.example:

Code:

# secrets.toml.example

# This file contains sensitive information required for authentication.
# Rename this file to `secrets.toml` and fill in the required fields.
# Keep this file secure and do not share it publicly.

# Qobuz account email and password for authentication.
email = "your-email@example.com"
password = "your-password"

# Optional: ID and secret of your Qobuz application to access the Qobuz API.
# If not provided, qonnect will attempt to extract it from Qobuz's public resources.
# app_id = 1234
# app_secret = "your-api-secret"

No token-based authentication for now.

For the track_changed event, what I've got now, subject to change:

Code:

- `TRACK_ID`: Content ID
- `TITLE`: Track title
- `ARTIST`: Artist name
- `ALBUM_TITLE`: Album name
- `COVER_URL`: Artwork URL
- `DURATION`: Length in seconds
- `FORMAT`: Input format and bitrate (e.g., "MP3 320K", "FLAC 1.234M")
- `DECODER`: Output format (e.g., "PCM 16 bit 44.1 kHz, Stereo")

Different from pleezer, note it's COVER_URL instead of COVER_ID.