Introducing pleezer: a Deezer Connect player

[roderickvd]

Following from this morning: for lossy formats I could report "32 bit", because that's what the decoder is working in then. While technically correct, I think it would only confuse users.

[Tim Curtis]

Agree. Best to leave it at 16

[mathieuruellan]

I see we have to set login password in the config.
Does that means that only the user with the right account can connect to? With Spotify, anybody with a premium/family suscription can play on a shared connector.

[roderickvd]

Correct. The Deezer Connect protocol does not have that feature - not a shortcoming of pleezer.

[roderickvd]

I just released v0.15.0 with a new command-line option that I think is very interesting to Raspberry Pi users: "--max-ram <MB>".

--max-ram: Maximum RAM (in MB) to use for storing audio files in memory. If not specified or if a track exceeds this limit, temporary files will be used. Example:
   pleezer --max-ram 64  # Store tracks in RAM if under 64MB

   As a guide for sizing:
   - For 320 kbps MP3: ~15MB for a typical 5-minute track
   - For FLAC: ~30-50MB for a typical 5-minute track

   Consider allowing at least double these amounts to accommodate both current and preloaded tracks. For example, --max-ram 100 should comfortably handle most MP3 tracks, while --max-ram 200 would handle most FLAC tracks.

Before, tracks were always stored in temporary files. Storing in RAM should greatly improve SD card lifetime.

[TheOldPresbyope]

Cool.

Regards,
Kent

[Tim Curtis]

I just released v0.15.0 with a new command-line option that I think is very interesting to Raspberry Pi users: "--max-ram <MB>".

--max-ram: Maximum RAM (in MB) to use for storing audio files in memory. If not specified or if a track exceeds this limit, temporary files will be used. Example:
   pleezer --max-ram 64  # Store tracks in RAM if under 64MB

   As a guide for sizing:
   - For 320 kbps MP3: ~15MB for a typical 5-minute track
   - For FLAC: ~30-50MB for a typical 5-minute track

   Consider allowing at least double these amounts to accommodate both current and preloaded tracks. For example, --max-ram 100 should comfortably handle most MP3 tracks, while --max-ram 200 would handle most FLAC tracks.

Before, tracks were always stored in temporary files. Storing in RAM should greatly improve SD card lifetime.

Nice :-)

Where is the default on-disk location for tracks?

[roderickvd]

Where is the default on-disk location for tracks?

Default system temporary directory, so /tmp.

This is also the case for librespot, although I remember I made it a command-line option to choose another temporary directory. RAM storage I did not implement in librespot.

[Tim Curtis]

Where is the default on-disk location for tracks?

Default system temporary directory, so /tmp.

This is also the case for librespot, although I remember I made it a command-line option to choose another temporary directory. RAM storage I did not implement in librespot.

The /tmp dir at least on PiOS is mounted by systemd as type tmpfs which AFAIK is a RAM based file system.

[roderickvd]

The /tmp dir at least on PiOS is mounted by systemd as type tmpfs which AFAIK is a RAM based file system.

On my moOde install it seems mounted on the SD card:

Code:

roderick@headphones:~ $ findmnt -T /tmp
TARGET SOURCE         FSTYPE OPTIONS
/      /dev/mmcblk0p2 ext4   rw,noatime

If it were tmpfs, then yes that would also work well to save the SD card.