Shuffle buttons don't work on some clients. about librespot HOT 8 CLOSED

Comment by plietar
Wednesday May 11, 2016 at 18:38 GMT

The playback time issue was caused by some stupid unit conversion mistake, and fixed by b8b0f9c

Shuffle and repeat are not implemented at all IIRC

from librespot.

Comment by xthursdayx
Saturday May 27, 2017 at 16:42 GMT

I'm finding that shuffle won't work when playing from Spotify on a Macbook Air using librespot with the Moode audio player OS on a Raspberry Pi. Have there been any updates on this? Thanks!

from librespot.

Comment by Bebowi
Sunday Sep 17, 2017 at 15:47 GMT

When I enable shuffle mode due to Spotify Clients on Mac and iPhone there is no effect to Librespot. Starting the next track leads to an automated disabling of this mode in all cases.

from librespot.

Comment by kayue
Monday Sep 18, 2017 at 02:52 GMT

@Bebowi Because it has not been implemented yet. :(

from librespot.

Comment by mickvdv
Wednesday Oct 25, 2017 at 15:59 GMT

When will this be implemented?

from librespot.

Comment by nicokimmel
Wednesday Dec 06, 2017 at 18:24 GMT

Is there any way to get shuffle working? I want this feature so bad. Im using SpotOn (spotify alarm clock) and without shuffle its not that nice.

from librespot.

Comment by djmaze
Wednesday Dec 06, 2017 at 18:32 GMT

It works for me when I start playing on a local device (Android or desktop) and then switch output to the librespot device while playing.

from librespot.

Comment by kingosticks
Wednesday Dec 06, 2017 at 19:04 GMT

That 'works' because the official client just hands librespot the already shuffled track list. Librespot doesn't really have to do anything in that case.

You can see my naive (and very incorrect) implementation of shuffle and repeat at plietar/librespot@master...kingosticks:master. I got stuck trying to implement shuffle properly and I've some questions for anyone familiar with how it (spirc?) is supposed to work regarding this.

The incorrect aspect of what I did is that mime treats 'queued' tracks like any other track in the list. This is wrong as 'queued' tracks should keep their positions and it's only the remaining tracks that need to be shuffled. That's a simple enough improvement to do.

My problem is how do you restore the original track order when the user disables shuffle? You don't know what that original order was. Are you meant to use the context uri state to reload the track list (assuming you also fix librespot to keep that state). And then what do you do with any 'queued' tracks that are still present, just insert them at the front? I could probably answer the latter question with some more experiments but the context uri thing is a total guess.

from librespot.