Bugzilla – Bug 669
Allow Sleep Option to Stop Music Rather than set OFF state
Last modified: 2011-11-06 23:24:21 UTC
Further to bug 649, it would be nice if there were an option to have the sleep timer simply stop playback and leave the Squeezebox in the ON/IDLE state. Currently, the sleep timer will set the Squeezebox to the OFF/STANDBY state, which negates the effect of the idle screensaver introduced in the resolution to bug 649. Having the sleep timer set the Squeezebox to OFF/STANDBY currently also can create issues with some universal remotes (such as the Harmony 688) which maintain state information and thereby expect the device to remain on. I would envision this as a player option that would globally affect how the sleep timer operates (on that particular player) rather than simply creating an additional sleep timer process.
perhaps this kind of thing is better done in a plugin, like PowerSave.
Perhaps, but Powersave serves a very different purpose, which is to take a device from the IDLE state to the STANDBY state after a specified amount of time, regardless of whether the user has set the sleep timer or not. All I'm really suggesting here is a slight modification to how the existing sleep timer operates. Rather than setting the player to STANDBY (OFF) when the sleep timer expires, simply have it stop playing the current playlist and stay in IDLE mode. Since the real purpose of a sleep timer is to make the device stop playing audio, this would still fulfill that objective, but allow those who want to make use of an "off-mode-style" screensaver to do so. One additional option under "Player Settings" in the SlimServer could be used to define whether the Sleep Timer should turn the device OFF or simply STOP playback.
the server now has an option for a screensaver in 'off' mode. check out the nightly build and see if that satisfies your requirements.
Almost. That would solve the screensaver issue, however the other issue I around stateful universal stateful remotes isn't as easily solved by this. I don't consider this to be a high-priority issue, but here is the situation I find myself in: I have a Harmony 688 universal remote. I have setup the "Play Music" button to turn on the SB, Stereo Receiver, set appropriate inputs, etc. The H688 is one of these remote controls that maintains on/off state information about devices, and sends commands based on what mode is *thinks* the device is in (ie, what it last set the device to). So I go to bed and hit the "Play Music" button, which turns on the SB, receiver, etc. I pick a playlist, start playing it, and then set the sleep timer. After about an hour, the SB shuts itself off. However, in the morning when I get up and hit the OFF or "Watch TV" button, the SB will of course toggle back on (as the remote thinks it's in the "ON" state still), and then when I go to listen to music again, of course it turns the SB OFF again. I have to either find the SB remote itself, or find the "PwrToggle" button on my H688 in order to flip the SB back to the correct state so that it works with everything else. I have programmed my remote around this situation *somewhat* (I effectively told the H688 that I want the SB left on all the time, and then put a "PwrToggle" button on the main display so that I can turn it back on after the sleep timer turns it off), but while that works fine for me, it adds confusion for my wife (who was the reason I bought the H688 in the first place), and therefore isn't really a very elegant solution.
Oh, the other workaround I've used for the time being is to use the "Alarm" function to turn the SB back on in the morning, which is great on weekdays (when I actually want to wake up), but not particularly desirable on weekends :)
Jesse, I understand your problem. I can certainly see how a feature like this would help. teh point behind my suggestion of a plugin is something along the same reasoning as that which lead to the AlarmPlugin. Some specialised functions that are needed by only a few users are often best handled with a plugin, rather than loading the server with option after option. Eric Koldinger (kolding@yahoo.com) posted a wonderful Sleep Timer plugin that allowed much longer intervals for timeout. If he is still maintaining this plugin, he might be willing to make this an option in the plugin. Take this only as an option for possibly having the feature sooner as a plugin author often can edit plugins sooner than a new feature can make it into the server (which sometimes requires a certain level of demand). If left here long enough, likely, it will eventually come along.
Marking items that aren't going to be addressed immediately in 6.1 as future. Please update if this is in error or the bug has already been addressed.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.
Dean doesn't work here any more :)
Unassigned bugs cannot have a priority.