When I initially create a dynamic playlist with some parameters and after that just pull the next song with the session_id of the playlist everything is OK.
But when the user rates a song or wants songs with higher tempo and I make the request, the API returns the next song as well.
If I pull the next song later, would the previously returned song be counted as skipped?
hkdobrev - I don't think I understand your question, could you give a few more details? What calls are you making, what exactly were you expecting and what exactly are you seeing? -- Paul
I have a music player powered by a dynamic playlist from EchoNest. The player has like/dislike buttons.
When the user requests a new playlist (for example selected songs by music style from a custom catalog I have created) I make the request to EchoNest using the playlist/dynamic API call. The API returns the session_id of the playlist and the first songs. For the following songs I make requests to playlist/dynamic with the session_id and everything works fine.
The problem is when the user rates the song (but don't want to go to the next one) and I make the request using the rating parameter and the playlist session_id. The API then not only rates the song but also returns the next song in the playlist. The user may never listen to that song. And if the user requests the next song and I make the same "next song request" from above, would the song returned from the rating be counted as skipped?
I am sorry for no explaining the whole thing in the beginning. Thanks :)
hkdobrev - the dynamic playlist API is designed with the intention that the client will make exactly one call per song. This means when a user rates a song before the song is finished playing, your client should not call the api yet. Only when the song finishes playing should your client call the API method to get the next song. This call should including the rating information for the previous song. -- Paul