Introducing pleezer: a Deezer Connect player

[roderickvd]

Hey this is awesome work, just switched to Deezer from using Spotify cast before on Moode.
What i miss is being able to cast from different accounts.
Would it be possible to have an option to have more then one Pleezer instances running for different accounts in my household?
or an idea to solve this in a different way?

Glad you like it.

I've never tested it, but yes: you should be able to run multiple pleezer instances on a single machine. Each with a separate secrets file for the different accounts.

[Gaupen]

Do you mean write Deezer metadata and cover url to the currensong.txt file?

What i mean is , like when i play a radio station i get  into home assistant via the Media Player Demon that runs one Moode  an attribute for example media_title: "NPO Radio2: Paolo Nutini - New Shoes"  
So that is the artist and the title already 
For radio i have to find the cover art myself in home assistant so i could use that if the media title would be put out  
but i guess , since it is allready displayed in moode it could be output via MPD also  (now i am searching a little and i am unsure if home assistant is capable of pulling that in but mediatitle would be oke for me. 

see Protocol — Music Player Daemon documentation 


Oh!  while checking better this i think  pleezer is not connected to mpd :-)  so i guess that is not a simple thing to add

[Gaupen]

Hey this is awesome work, just switched to Deezer from using Spotify cast before on Moode.
What i miss is being able to cast from different accounts.
Would it be possible to have an option to have more then one Pleezer instances running for different accounts in my household?
or an idea to solve this in a different way?

Glad you like it.

I've never tested it, but yes: you should be able to run multiple pleezer instances on a single machine. Each with a separate secrets file for the different accounts.

That seems to work  i tested 

sudo pleezer --name pleezer_user2 --device-type web --device "ALSA|_audioout||S32" --initial-volume 100 --secrets /etc/deezer/user2.toml --hook /var/local/www/commandw/deezevent.sh   

And i managed to have both users being able to cast to moode

Would be nice if the moode  deezer connect renderer config provided for extra deezer accounts in that way.

[Tim Curtis]

Hey this is awesome work, just switched to Deezer from using Spotify cast before on Moode.
What i miss is being able to cast from different accounts.
Would it be possible to have an option to have more then one Pleezer instances running for different accounts in my household?
or an idea to solve this in a different way?

Glad you like it.

I've never tested it, but yes: you should be able to run multiple pleezer instances on a single machine. Each with a separate secrets file for the different accounts.

That seems to work  i tested 

sudo pleezer --name pleezer_user2 --device-type web --device "ALSA|_audioout||S32" --initial-volume 100 --secrets /etc/deezer/user2.toml --hook /var/local/www/commandw/deezevent.sh   

And i managed to have both users being able to cast to moode

Would be nice if the moode  deezer connect renderer config provided for extra deezer accounts in that way.

I think one of the challenges with this approach is that it's not really "session interruption" which I think is how Spotify Connect (librespot) works using just a single instance.

If there were multiple pleezer instances running, each capable of acquiring the audio output and sending metadata to the WebUI, users would have to manually coordinate when they are using Deezer. I could envision a support nightmare.

[Gaupen]

Hey this is awesome work, just switched to Deezer from using Spotify cast before on Moode.
What i miss is being able to cast from different accounts.
Would it be possible to have an option to have more then one Pleezer instances running for different accounts in my household?
or an idea to solve this in a different way?

Glad you like it.

I've never tested it, but yes: you should be able to run multiple pleezer instances on a single machine. Each with a separate secrets file for the different accounts.

That seems to work  i tested 

sudo pleezer --name pleezer_user2 --device-type web --device "ALSA|_audioout||S32" --initial-volume 100 --secrets /etc/deezer/user2.toml --hook /var/local/www/commandw/deezevent.sh   

And i managed to have both users being able to cast to moode

Would be nice if the moode  deezer connect renderer config provided for extra deezer accounts in that way.

I think one of the challenges with this approach is that it's not really "session interruption" which I think is how Spotify Connect (librespot) works using just a single instance.

If there were multiple pleezer instances running, each capable of acquiring the audio output and sending metadata to the WebUI, users would have to manually coordinate when they are using Deezer. I could envision a support nightmare.

Would it be doable to advertize multiple deezer accounts from within one instance instead of running two instances on the same machine in a way that the last one that connects to it takes over the stream.

[roderickvd]

It is not how I designed pleezer, nor how any of the official clients work. It would require significant change and introduce a lot of complexity. I don’t think that I will add it.

[Gaupen]

It is not how I designed pleezer, nor how any of the official clients work. It would require significant change and introduce a lot of complexity. I don’t think that I will add it.

I understand, it is  though then that pleezer is only usable for one user in a household. where as the spotify solution could be used by anyone. 
the big advantage with pleezer is that you still use the deezer mobile app as the main control with all the functionality that comes with it. 

I find pleezer therefore way more usable in comparisation with like how denon heos has solved it with the functinality in the heos app or music assistant which i can also use in hom assistant too and and also allows for multiple accounts like heos 
But both of these have  the same problem that they miss the functionality of the native app. ( like changing the flow form and telling it to not recommend a certain artist or song anymore) Hopefully somebody capable with rust can assist you with that in the future, as i think it is the best way to stream deezer to other platforms. 

Although i am also of the opinion that it should have been the functionality of deezer cast (in the same way as spoticast ) , so yes you would be solving a shortcoming which is never a good way and will mostly lead in to problems easier. So i understand your hesitation there.

[roderickvd]

I've just released pleezer v0.17.0 on GitHub. You might call it the "Audiophile Edition" and I'm pretty proud of it.

This release introduces TPDF dithering. That should be standard practice when requantizing audio, but is often overlooked. Beyond simple dithering, I made it a dithered volume control so that it scales with the magnitude of the actual signal. I was pretty astonished by its audible benefits: cymbals gained clarity, ghost notes became more distinct. That alone would have been worth it.

Encouraged, I went on to implement Shibata noise shaping, using newer curves than those found in SoX. There are 7 selectable shaping levels, making pleezer one of the most capable open-source dithering systems out there. To my knowledge, only SoX and a handful of other tools offer comparable functionality.

Output format (S16, S32, etc.) guides the dithering logic. By default, noise shaping is set to level 3, which balances noise suppression with stability.

Advanced users should fine-tune:

Code:

--dither-bits: set to your DAC's effective resolution (or 0 to disable)
--noise-shaping: select level 1–7 (or 0 to disable)

To estimate dither bits from spec sheets:

From THD+N in dB: (-dB - 1.76) / 6.02 → e.g., -118 dB ≈ 19.3 bits
From % THD+N: (-20 * log10(%THD+N) - 1.76) / 6.02 → e.g., 0.0002% ≈ 18.6 bits
Smooth Playback, Zero Fuss

And one more thing: a long-standing bug caused pleezer to ignore S32 output settings on moOde, silently reverting to S16. This is now fixed.

[Tim Curtis]

I've just released pleezer v0.17.0 on GitHub. You might call it the "Audiophile Edition" and I'm pretty proud of it.

This release introduces TPDF dithering. That should be standard practice when requantizing audio, but is often overlooked. Beyond simple dithering, I made it a dithered volume control so that it scales with the magnitude of the actual signal. I was pretty astonished by its audible benefits: cymbals gained clarity, ghost notes became more distinct. That alone would have been worth it.

Encouraged, I went on to implement Shibata noise shaping, using newer curves than those found in SoX. There are 7 selectable shaping levels, making pleezer one of the most capable open-source dithering systems out there. To my knowledge, only SoX and a handful of other tools offer comparable functionality.

Output format (S16, S32, etc.) guides the dithering logic. By default, noise shaping is set to level 3, which balances noise suppression with stability.

Advanced users should fine-tune:

Code:

--dither-bits: set to your DAC's effective resolution (or 0 to disable)
--noise-shaping: select level 1–7 (or 0 to disable)

To estimate dither bits from spec sheets:

From THD+N in dB: (-dB - 1.76) / 6.02 → e.g., -118 dB ≈ 19.3 bits
From % THD+N: (-20 * log10(%THD+N) - 1.76) / 6.02 → e.g., 0.0002% ≈ 18.6 bits
Smooth Playback, Zero Fuss

And one more thing: a long-standing bug caused pleezer to ignore S32 output settings on moOde, silently reverting to S16. This is now fixed.

Fantastic :-)

I see from the readme:

--dither-bits is a user calculation using 6.02 as the divisor in the two formula options
--noise-shaping are preset options:

Level 0: No shaping
Level 1: Minimal shaping
Level 2: Conservative shaping
Level 3: Balanced shaping (default)
Level 4–7: Aggressive shaping — reduces in-band noise further but shifts energy >15 kHz (use with caution)

I'll add these to the settings and bump to 0.17.0 for upcoming release 9.3.3

[roderickvd]

Released v0.17.1 with some refinements to dithering and noise shaping.