Bugzilla – Bug 4835
current playlist is reshuffled upon reconnecting a player
Last modified: 2011-11-06 23:22:26 UTC
I've found that when softsqueeze loses its connection to the server my playlist is stopped and reshuffled. I'm guessing this is more of a slimserver thing rather than a softsqueeze thing? This is a common problem for me since I'm running the client (softsqueeze) on a laptop. I noticed the web interface has a setting for what to do with the current playlist on power off and power on, but that setting doesn't seem to be applying to this scenario. I could live with starting the song over from the beginning when reconnected, but it sure would be nice if it would remember where within the song it was too.
I'll see if I can reproduce this later today.
Could you please elaborate more specifics on your scenario? How exactly is SoftSqueeze losing its connection to your server? I connected a SoftSqueeze client to my SlimServer, then killed the network connection on SlimServer, of course SoftSqueeze lost connection, then I re-enabled the network connection on my SlimServer computer and the remote SoftSqueeze didn't lose the playlist, it picked up right where it left off as it should. In other words, I'm not able to reproduce this.
I just tested a couple of methods of lost connection (disconnecting from network and going into sleep mode). They both had no problem remembering the playlist state, so now I'm suspecting it relates to the duration of the disconnection. For example, I took my laptop home over the weekend, never took it out of sleep, brought it back to work today, and the playlist was "reset" (same songs but reshuffled and back to the beginning of the first song). I will investigate further by testing my suspicion and get back with results. Sorry for the unreproducible report - I thought it was simpler than it apparently is.
Not a problem Jeff. Let me know if you have clearly reproducible steps or if you have any other things you'd like us to try. It seems to me that at some point of being disconnected the player should be effectively reset. If I connected a player I hadn't used in some time and it quickly started playing an old playlist, I could see room for confusion.
OK, it just so happens that I ran an errand this afternoon for a couple of hours and therefore had disconnected my laptop and put it into standby. When I came back, plugged into the network, and turned it back on, it had reset. So it sure appears to be some sort of timeout, which seems to be shorter than around 2 hours and 15 minutes. I would not expect it to resume playing after a 2 hour disconnection, but I would expect that the playlist doesn't reshuffle and go back to the beginning. And it's not like it's clearing the playlist entirely, so it almost seems like a corner case that wasn't completely thought through. I hope that's helpful enough information. If you want me to try to nail down the timeout duration more precisely it will take some time obviously as this is a machine I use in daily work and therefore can't be performing these disconnection tests all the time. Let me know if you do need me to perform that work, but hopefully you have a machine you can tie up with such a test for a couple of hours. :)
I've managed to reproduce this, and indeed it does appear to be a bug. When the player re-establishes a connection the song will start again from the beginning, but it should not have a different playlist. Sorry Jeff but when a player is disconnected it will not remember where within the song it was, but it should remember the playlist as it was. I reproduced this with SoftSqueeze as well as a Squeezebox v3 so this isn't a SoftSqueeze specific issue. Also, I'm making a few changes to this bug to more accurately describe the problem, and mark this as an enhancement. Thanks for your patience Jeff!
Unassigned bugs cannot have a priority.