Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by downerending on Tuesday February 18, 2020 @03:29PM
(#22360043)
For me, I listen only from "Songs" (my entire collection, which is about 3000 tracks). Even when shuffled, almost everything I hear is something I've heard within the last week or two.
When I use the Amazon app under the same conditions, I often hear a track I haven't heard for a long time. Which is what I'd expect when random sampling from 200 hours of music.
(I don't use playlists, as they're simply too much work.)
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by fuzzmz on Tuesday February 18, 2020 @03:14PM
(#22359873)
It's not really random, in the sense that if you have a playlist and hit shuffle it'll always play in the same order instead of randomizing the play order each time you listen to that playlist. Basically, with the current behavior, once you learned the order of the shuffled songs you can always know what comes next.
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by joegahona on Tuesday February 18, 2020 @03:49PM
(#22360253)
Is there a technical reason it does this, and why it's so difficult to correct?
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by tjoff on Tuesday February 18, 2020 @04:03PM
(#22360384)
Technical debt.
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by The_Latecomer on Tuesday February 18, 2020 @03:25PM
(#22359999)
Google stopped supporting Play Music a while back to be fair. Have you tried using YouTube music? Would you say you find this same issue there?
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by anoonmoose on Tuesday February 18, 2020 @03:47PM
(#22360229)
What do you mean, stopped supporting?
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by reciprocornous on Tuesday February 18, 2020 @04:28PM
(#22360595)
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by mrkeen on Tuesday February 18, 2020 @03:19PM
(#22359920)
It may be the case that 100 tracks are sent to the device and the shuffle logic chooses from them locally.
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by kingosticks on Tuesday February 18, 2020 @04:40PM
(#22360687)
Not sure why you are being down voted, this is essentially how Spotify's shuffle works. At least, if you MITM the official client and load a large playlist/context you'll only see a small window worth of tracks being loaded. And you won't see any request from the client when you then shuffle that playlist, it's done locally.
This may, of course, have changed. My experiments while (badly) implementing librespot's shuffle functionality were a few years ago now.
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by downerending on Tuesday February 18, 2020 @05:19PM
(#22361003)
In my case, all of the tracks are already on the device. But yes, it's possible that they're doing something like this anyway.
edit: Did a search, seems like there's quite a few problems (only playing recently added songs, only playing 100 songs out of the playlist, etc.). I know google music has also had long standing issues with shuffle play - and in fact I left it over these kind of issues. Is it really difficult to implement a shuffle?!