I am well aware we’ve had this discussion before, and I’ve been employing different workarounds to get a truly random shuffle in different situations.
Just considering the fact that I have submitted a few issues that are only relevant to me due to this, I was wondering how you feel now about providing a settings option to make the shuffle header buttons a truly random shuffle. I know that I, and a lot of others, would greatly appreciate this option, and it being a settings option means that your desired algorithm can still be the default.
Thank you for your work and responsiveness as ever! Long live symfonium
Problem solved:
It aligns with expectations of those who want a truly random shuffle and avoids issues where the algorithm isn’t always suited to the context.
I don’t actually see a feature request for this when I search, but perhaps I’ve missed it. I know it’s been brought up within other discussions
Edit: I see that you mean duplicates of other issues. Sorry, I didn’t mean to. I’ve been away for a little while so jumped a few app versions and wanted to report everything.
Hi there,
I was going to post a new feature request for implementing a true shuffle, but since it was already requested, just going to second it, because current shuffle implementation generates a full randomized queue and plays it sequentially.
This works well for fairness, but removes the feeling of true randomness (e.g., you won’t listen to the same song again, till the whole list is complete).
Problem solved:
It’s not really a problem per se, it’s more a QOL improvement.
Brought benefits:
This would benefit users with large, diverse libraries by providing a more “alive” listening experience.
Other application solutions:
Winamp (that’s why I’m still using the legacy version, even before Llama bought it and started updating it)
Most car audio players - My old one (JVC KD-R691) was applying randomness first on container level (album/folder), then track level.
Current one (Sony DSX-A410BT), indexes everything in a common pool and then applies it. Both work great, although I like randomizing the container first and then its contents better.
To achieve true randomness, you shouldn’t create a queue, it should calculate the next song in real-time. If true randomness is achieved, then you can get the same song multiple times, before you even played through the whole library/playlist.
But in relation to creating a shuffle queue that is truly random Vs algorithmic, since you ask for info on how other players implement feature requests, I’m letting you know that Spotify has implemented this with a toggle in settings
I don’t wish for songs to be repeated in a shuffle queue, or dynamically shuffled at each song.
I would like a queue where at the start of the queue each song is assigned a place randomly, rather than with a weighted algorithm which is currently the situation. I still only wish for each song to be played once in the queue.
@Tolriq
Do I need to open a separate feature request, since it turned out we ask for little different things, or you can combine an implement both when and if decide to do so?
I’d also apreciate a toggle for a truly unbiased shuffle-mode.
As it is, the Shuffle algorithm is prefering already played songs so much that it creates a feedback loop problem. Or at least it did so in multiple of my playlists… Even songs I like tend to get annoying when they are recommended as often as they are in my case.
