Full album playlist doesn't queue if quickly skip first track

Issue description:

Hi, my desired outcome is to have a truly random shuffle of all the albums in my library.

The only way to do that is to use a smart playlist, which is what I do. I use an albums smart playlist rather than a tracks smart playlist as I like the ability to skip album by holding the next track button.

As previously discussed, the queue won’t load the whole playlist if I choose an album from the list, only if I play the playlist from the start with the play button, where it loads a few and then the remainder after a delay.

Obviously there are times when the first random album isn’t what I wish to listen to. If I skip from the first track (using the next track button), the rest of the albums don’t load from the playlist.

Unfortunately I can’t think of a way around this for my use case, which isn’t a particularly niche one. Obviously I can wait without skipping for the rest to load, but that isn’t ideal as it’s a noticeable wait.

Would appreciate any help. Thanks.

Logs:

Upload description: tobyburton96albumskip

Additional information:

 

 

Reproduction steps:

 

 

Media provider:

Local device

Screenshots:

     

Fun fact the more you spam the same thing over and over the less chance it have to happen …

BTW the long press skip album works in track playlists too.

What? I haven’t posted this before. This is me mentioning that if you skip the track using the now playing, after starting the playlist from the play button, it doesn’t load the full playlist. Before, I asked about it loading the rest of the tracks when picking a track from the playlist. Different scenarios. You may see this as functionally the same but I didn’t. I am trying to improve the app, not waste your time, please give me the grace of assuming good intentions.

Long press skipping on a track playlist doesn’t work correctly for me consistently. I will post a issue.

Each and every time :wink:

I was explaining why my workflow was the way it was. Not requesting you change the shuffle buttons - you already know that is something I desire. In the past you have asked people what the outcome they are trying to achieve was rather than them specifically asking what they want changing. So I thought I would explain overall why I was using the functions the way I was before moving on to the exact issue I was facing in this workflow, so as to give you as much information as possible and cover the situation from all angles, and then you could tackle it as you see fit. I was doing this partially to hopefully avoid being criticised but clearly that backfired.

And yes I do mention that a lot as it is the way I like to listen to my music. Therefore it motivates a lot of my specific behaviour in the app and is the reason I find niche things to bring up in trying to work around it. Explaining this gives context so you can understand your users and their desires more easily. Once again, I am trying to help.

Well there’s still the shuffle button for that. You don’t like it but it does shuffle.

Anyway skip next is a playback action and cancel any loading to avoid race, so this is normal, I’ll tweak the queue adding to be more frequent so will have time to queue more before the cancel, but this is still to be expected.

Are you talking about the header shuffle button? I prefer true random. If you mean the now playing shuffle button, that doesn’t keep albums together

Well this is a true random that avoid the worst cases of random :wink:

Personally id prefer the chance of repetition of artist or album accordingly if they are represented that heavily in the library. That’s the beauty of truly random