06-08-2025, 11:00 AM
(This post was last modified: 06-08-2025, 12:27 PM by roderickvd.
Edit Reason: hit Reply to soon
)
Shouts out to another number of donations, thank you!
A short progress update:
Qobuz Connect works with a shared state between all connected devices ("renderers"). So each one has a copy of the playlist, current track position, etc. at each time. Then it states which renderer is the active one.
It seems I've got 99% of all incoming messages deciphered, so we can now follow the playback on another device. Autoplay and shuffle have some idiosyncrasies: we receive them OK, but I'm pretty sure it'll take a few iterations before we accurately copy the behavior from the official Qobuz apps.
This is a pretty big step, and I know move to the next phase: becoming the active renderer and actually playing some music!
A short progress update:
Qobuz Connect works with a shared state between all connected devices ("renderers"). So each one has a copy of the playlist, current track position, etc. at each time. Then it states which renderer is the active one.
It seems I've got 99% of all incoming messages deciphered, so we can now follow the playback on another device. Autoplay and shuffle have some idiosyncrasies: we receive them OK, but I'm pretty sure it'll take a few iterations before we accurately copy the behavior from the official Qobuz apps.
This is a pretty big step, and I know move to the next phase: becoming the active renderer and actually playing some music!
maintainer of librespot and pleezer, working on a qobuz connect player. sponsor me: https://github.com/sponsors/roderickvd
