Thank you for your donation!


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


Introducing pleezer: a Deezer Connect player
Too bad Deezer decided to cancel the connect functionality. I just had started a subscription based on the integration with moOde and was testing alongside of Spotify connect. But now I have no use for Deezer anymore so cancelled the subscription.....
Reply
I just released pleezer v0.19.0. So far, Deezer Connect remains available on iOS when you enable "Remote Control" under "Deezer Lab", and on Android when you use an older APK version. No idea for how long, but let's enjoy it while it lasts!

In v0.19.0 the device enumeration has changed. Therefore the virtual "_audioout" device that moOde uses won't work when you start with "pleezer -d ALSA|_audioout" like moOde is doing now. Instead, use the default output device and this to /etc/alsa/conf.d/default.conf:

Code:
pcm.!default {
   type plug
   slave.pcm "_audioout"
}

ctl.!default {
   type hw
   card 0
}
Run pleezer -d "?" to view the other output devices it now enumerates.

Management summary of the v0.19.0 changes:
  • mostly a maintenance release
  • more robust when output errors occur (for example, when the DAC gets disconnected in the middle of playback)
  • disconnects when playback starts on another device (for Deezer ToS compliancy)
I appreciated your continued donations to help me maintain pleezer and work on a native Qobuz renderer!
maintainer of librespot and pleezer, working on a qobuz connect player. sponsor me: https://github.com/sponsors/roderickvd
Reply
(07-19-2025, 09:34 PM)roderickvd Wrote: I just released pleezer v0.19.0. So far, Deezer Connect remains available on iOS when you enable "Remote Control" under "Deezer Lab", and on Android when you use an older APK version. No idea for how long, but let's enjoy it while it lasts!

In v0.19.0 the device enumeration has changed. Therefore the virtual "_audioout" device that moOde uses won't work when you start with "pleezer -d ALSA|_audioout" like moOde is doing now. Instead, use the default output device and this to /etc/alsa/conf.d/default.conf:

Code:
pcm.!default {
   type plug
   slave.pcm "_audioout"
}

ctl.!default {
   type hw
   card 0
}
Run pleezer -d "?" to view the other output devices it now enumerates.

Management summary of the v0.19.0 changes:
  • mostly a maintenance release
  • more robust when output errors occur (for example, when the DAC gets disconnected in the middle of playback)
  • disconnects when playback starts on another device (for Deezer ToS compliancy)
I appreciated your continued donations to help me maintain pleezer and work on a native Qobuz renderer!

Cool. Even though it's officially deprecated, since Remote Control still works on IOS maybe it's best to reenable it for upcoming moOde 9.3.8. I'll give it some thought.

Is the Ctl block required in the ALSA conf?
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
(07-19-2025, 09:54 PM)Tim Curtis Wrote: Is the Ctl block required in the ALSA conf?

No, it should work without. I believe it just sets the default device when you use tools like alsamixer.
maintainer of librespot and pleezer, working on a qobuz connect player. sponsor me: https://github.com/sponsors/roderickvd
Reply
I can confirm the Remote Control feature still works on IOS so I'll plan to turn Deezer Connect back on in upcoming 9.3.8 with appropriate "deprecated" warnings in the help.

This is using the latest pleezer 0.19.0
   

Code:
# /var/log/moode.log
20250721 075021 DEBUG: startDeezer(): (pleezer --name "Moode9 Deezer" --device-type "web" --device "ALSA|default||S32" --initial-volume "10" --secrets "/etc/deezer/deezer.toml" --noise-shaping 2 --hook /var/local/www/commandw/deezevent.sh -v > /var/log/moode_pleezer.log 2>&1 &)
20250721 075021 worker: Deezer Connect:  started
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
After some testing it looks like the ALSA conf override of "default" in pleezer 0.19.0 causes a conflict with use of the real ALSA "default" setting for the MPD mixer_device param when the output device is HDMI.

Code:
/etc/mpd.conf
mixer_device "default:vc4hdmi0"

This results in pleezer not being able to play to an HDMI device.

There is a workaround that can be used (in moode) which involves replacing "default" with "sysdefault:vc4hdmi0" but other programs for example CamillaDSP will break if users specify ALSA "default" as the output device.

PROPOSAL
I'd propose pleezer revert to the <= 0.18.0 behavior and support ALSA virtual devices like programs including MPD, Bluetooth, Airplay, Spotify Connect, Squeezelite, etc.

Issue of record:
https://github.com/roderickvd/pleezer/issues/100
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
Agreed, working on a hotfix. I'll report progress over at https://github.com/roderickvd/pleezer/issues/100.
maintainer of librespot and pleezer, working on a qobuz connect player. sponsor me: https://github.com/sponsors/roderickvd
Reply
Fixed in v0.19.1 if you build from source. In that case, it pulls in a fix that I've proposed to an upstream library.
maintainer of librespot and pleezer, working on a qobuz connect player. sponsor me: https://github.com/sponsors/roderickvd
Reply
Confirmed 0.19.1 works :-)
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
Hi all,
I am an Android user and, unfortunately, I don't have the option (even in the beta test section). Would you please be so kind to continue to push Deezer to have it in the Android environment too.
Best regards and thanks,
Francesco
Reply


Forum Jump: