Introducing pleezer: a Deezer Connect player

[Falco]

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.....

[roderickvd]

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!

[Tim Curtis]

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?

[roderickvd]

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.

[Tim Curtis]

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