Implement some sort of State handler with some sort of RO-API about librespot HOT 4 CLOSED

Comment by sashahilton00
Monday Jan 18, 2016 at 23:59 GMT

Agreed, this is a must have for the library given that it is going to be standalone. As per the gitter chat, here is a list of possible event emitters that it would be good to have:

• Track Start
• Track Finish
• Track Change
• Track Play
• Track Pause
• Track Stop
• Track Rewind/Fast Forward
• Track Seek Position
• Track Shuffle/Repeat enabled/disabled
• Device Connected [See above]
• Device Disconnected [See above]
• Device Disconnected no music [See above]
• Current Track Metadata
• Playlist Metadata [Track, Artist, Album, Duration]
• Queue updated
• Queue Metadata
• Volume Up/Down

I'm sure there are more, but I think this is more than good enough to start with.

from librespot.

Comment by CoDEmanX
Tuesday Jan 19, 2016 at 00:08 GMT

Native Spotify clients seem to periodically report playback progress to their servers, maybe that's another possible event (some kind of a heartbeat).

There are also a couple error events, like not authorized (anymore), song not available in target market, too many requests, premium required, app key invalid/banned...

from librespot.

Comment by sashahilton00
Tuesday Jan 19, 2016 at 00:08 GMT

Good point, I forgot about the errors.

from librespot.

Closing this, as it comes under the broader issue of Metadata, which is being tracked in #7

from librespot.