Look for similar bugs
Checked
Description
librespot loses the playing position when tracks are added to the actively playing playlist. It seems to jump backwards in the playlist by the number of tracks that were added to the playlist while the current track was playing. The Spotify provided clients probably re-sync the playlist before they start into the whole next track visual and pre-fetching, or they use an absolute instead of a relative position in the playlist.
Version
33bf3a7 (HEAD -> dev, origin/dev, origin/HEAD) Emit SetQueue event (#1677)
Built with cargo --locked to get around the vergen issue
How to reproduce
Steps to reproduce the behavior in librespot e.g.
- librespot launched from snapserver "source = librespot:///home/jbm/bin/librespot?name=slimshady-snapcast-librespot&dryout_ms=2000&devicename=slimshady-snapcast-librespot&volume=40"
- Running ps: "/home/jbm/bin/librespot --name slimshady-snapcast-librespot --bitrate 320 --backend pipe --initial-volume 40 --verbose"
- In the client, add tracks to the active playlist - I have a Daylist Archive playlist, which I add the current playlist to - so as many as 50 tracks get added, but usually 10s of tracks.
- librespot plays the current track fine, but then jumps back in the playlist at next track change.
Log
- librespot does not function with --verbose in this environment.
Host (what you are running librespot on):
- OS: Linux - Ubuntu 25.10
- Intel mini PC: HP t520 Flexible Series TC
Additional context
I have had this problem forever. My workaround is to record the current playlist position when I add tracks so I can manually restore it when I notice it's in the wrong place. If I forget, I have to dig around in the recently played tracks to figure out where I was. I grow these Daylist Archive playlists throughout the day (when the next Daylist comes out) until they hit the Spotify limit (around 10000 tracks), then I start another Daylist Archive. Most of the time I'm adding to the playing playlist.