Bugzilla – Bug 7532
Sleep option does not save current position (like the Hard OFF does)
Last modified: 2008-12-18 11:42:22 UTC
I think I have found a bug in the software. I have played around with the settings, and have the player settings (in config) so that at Poweroff, its set to "Pause/ Pause at power on". that way, for long albums, if remembers where it was. Now, when I power off manually, all is fine and it saves the location. All is good. But, when it sleeps (using the sleep after say 15 minutes), it does not save the position. Is this a bug?
To clarify, you're asking if SqueezeCenter could remember the final track in the playlist played before going to sleep, so that it may resume on the following track should you continue where you left off later. I just tested this and it works for me. I had a playlist of an album, it was playing the second track and I hit sleep once to sleep at end of track, which worked. I waited 5 minutes and hit play, track 2 started up again. Could you give it another try?
Re-tried and verified. To verify this, I played 4 long tracks (each 40 minutes), with sleep set to 30 minutes. When It went to sleep, I left it for a while (about an hour), and did the following... 1) Pressed power on button 2) Pressed Play to resume 3) Message on screen "Nothing"
I've now tried this with 2 players, with 4 tracks each 40 minutes, and I'm still not able to reproduce this. What sort of files are these, is there transcoding going on? When I set it to sleep, it sleeps then I hit power, then play, and it starts playing where it left off as I expect.
What version are you using of SqueezeCenter? You say you have the preference for this player set to "Pause/ Pause at power on" but this is not a valid setting. Are you sure that this is what you have set?
The current code does: Slim::Control::Request::executeRequest($client, ['stop']); Slim::Control::Request::executeRequest($client, ['power', 0]); I cannot understand why the 'stop' is needed.
Jaffa: we are unable to replicate this bug, please re-test with the latest daily build of 7.1. If you can still see this error, please reopen the bug with the details requested by Alan Y.