Major player rewrite + event service implementation

[devgianlu]

This PR wants to implement the event-service framework because of librespot-org/librespot#342, in order to accomodate the required metrics a major player rewrite has also been done.

All requests are sent to hm://event-service/v1/events via a POST request. The request has three headers: X-ClientTimeStamp, Accept-Language, X-Offset. I'm yet to figure out what the last one does. The body of the request is generally as follows: some chars to identify the type of message and the actual data. The 0x09 character is used to separate various fields.

I have also enhanced the Wireshark scripts to parse event service requests: https://github.com/devgianlu/spotify-analyze

List of client events: https://gist.github.com/devgianlu/8371de4449e90fc18e9bef1a0745bd18

TODO:

• Re-implement crossfade
• Fix repeat track not working
• Fix reporting when source end is different from trackdone
• Implement known metrics

[backspac]

Just a wild guess. Following this doc, X-Offset might be the track position in an album or a playlist.
https://developer.spotify.com/documentation/web-api/reference/player/start-a-users-playback/

[devgianlu]

Just a wild guess. Following this doc, X-Offset might be the track position in an album or a playlist.
https://developer.spotify.com/documentation/web-api/reference/player/start-a-users-playback/

Doesn't look like the values are usually even higher than the playlist size.

[devgianlu]

This is finally working!! Except when the "ended how" field is different from trackdone. There is probably some more research to do to figure out what those extra fields are for.

[Yuhanun]

Hello,

Is there currently any way to report back to spotify that you listened to a song using the API that this daemon provides?

Right now I'm switching song because it should send the tracking stuff to spotify but it doesn't seem to register on spotify's side.

Thank you,
Yuhanun

[devgianlu]

Is there currently any way to report back to spotify that you listened to a song using the API that this daemon provides?

Yes, when this is going to be merged the client will have complete reporting functionalities.

[Yuhanun]

Is there currently any way to report back to spotify that you listened to a song using the API that this daemon provides?

Yes, when this is going to be merged the client will have complete reporting functionalities.

Any ETA? Is there any way to do this with the current branch?

[devgianlu]

@Yuhanun No idea when this will be finished. The protocol right know is under development.

[Yuhanun]

@devgianlu So right now there is absolutely no way to do the listen reports?

[devgianlu]

There is, but why would you need it outside of the player?

[Yuhanun]

Because I'm building my own CLI tool and I'd like to contribute to the artist their stream count.

[Yuhanun]

Looks like you've got some infinite recursion going

edit: nevermind, nto the same class.

[Yuhanun]

Heyo this doesn't work for me, it doesn't report back "audio streams" (like the listens counters) to spotify, it never gest updated on their end even when listening for 60 seconds+

[hbouhadji]

+1 @Yuhanun

[humanperzeus]

+1 still not fixed? anywhere to figure out and help to retrieve how the original workflow works?

[devgianlu]

+1 still not fixed? anywhere to figure out and help to retrieve how the original workflow works?

It kind of works, but it's not perfect. If you want to try and analyze the request chain you need to hookup spotify-analyze and dump the Mercury requests.