Introducing pleezer: a Deezer Connect player

[roderickvd]

Hi guys,

I'm excited to share pleezer, a new headless streaming player built around the Deezer Connect protocol. 

In fact, I would like to ask you moOde guys some specific help. Currently, pleezer does not emit player events, though it's got the plumbing to do it. I would like to design the output according to moOde's needs and have that be The Way for all the rest.

So question is: what would your ideal player event emitter look like?

• Should it call a script, or output to stdout?
  
• Which events would you like emitted?
  
• Which information would you like to have, per event?
  
• For recurring messages, what should the frequency be? (not event-based, maybe like playback progress)
  
• What should the script command look like (which command-line arguments, in which order)?
  
• Or, if to output to stdout: how should the messages be formatted?
  

I would highly value to build this in collaboration with you here: https://github.com/roderickvd/pleezer/issues/27


The v0.1.0 release is available on GitHub here: https://github.com/roderickvd/pleezer/re...tag/v0.1.0.

While you might encounter some issues with this first release, the core functionality works well, and contributions are welcome to help improve it further. Please file bugs and further feature requests with GitHub issues.

Note: This is an independent project, not affiliated with Deezer.

[Tim Curtis]

Super nice :-)

I'll go through the project today and post back to your repo.

[roderickvd]

Super nice :-)

I'll go through the project today and post back to your repo.

Awesome. I created this placeholder feature request: https://github.com/roderickvd/pleezer/issues/27

[Tim Curtis]

To summarize my response: Preference would be that pleezer replicate the librespot event model (env vars + callable script) This makes it straight forward to understand and implement :-)