Bugzilla – Bug 13473
Setting sleep time on Boom can skip 30-minute mark
Last modified: 2009-10-30 16:15:58 UTC
If I've turned on my Boom, and directed it to play an album from my library on my SqueeceCenter server, and I press the top bar in order to make it go to sleep in a certain amount of time, each press cycles to the next in a series of minutes. However, the 30 minute mark is passed over during this cycle, unless the Boom's screensaver has kicked in. Basically, if you start an album playing and right after that, press the top bar, you get, in succession: 1. 15 Minutes 2. End of Song 3. 45 Minutes 4. 60 Minutes 5. 90 Minutes 6. Cancelled The cycle continues back at 15 minutes and so forth if you keep pressing the bar. However, if, after you've selected the album to play, you wait until the screensaver kicks in, THEN press the top bar; OR if you start pressing the bar, but stop, and let the screensaver kick in; the cycle goes: 1. 15 Minutes 2. End of Song 3. 30 Minutes 4. 45 Minutes 5. 60 Minutes 6. 90 Minutes 7. Cancelled Is there any reason why "30 minutes" would be dropped if the screensaver has not yet kicked in? I'd consider this a bug. - Tim
Tim: what version of SqueezeCenter are you running? The proper sequence should be: 1. End of Song 2. 15 Minutes 3. 30 Minutes 4. 45 Minutes 5. 60 Minutes 6. 90 Minutes 7. Sleep Canceled -------------------- If you connect your boom to SqueezeNetwork, do you get the above sequence? -------------------- While connected to your local server, check the log file for any errors. Enable (player.display) - Player Display information and test again. Check the log for errors.
James... I'm on vacation at the moment, so can't tell you precisely. It was a recent nightly of 7.3.4. Is that enough info? I had seen this problem before, in earlier versions of 7.3, as well. - Tim
P.S. I *did* once try this against SqueezeNetwork, and the sequence was correct. However, I only tried it for one case (listening to a radio station). When I get back home (in 3 weeks) I can test this; in the meantime, I'll keep checking here to see if the cause was discovered. - Tim
Oh, and finally - I didn't see that you said the proper sequence was supposed to be "end of song" 1st, then 15 minutes, etc. I've never seen it work that way on my local squeezecenter - it's always been "15 mins/end of song/..." - Tim
OK..I'll wait for you to get back from vacation then, I tried with 7.3.4 but could not see this behavior. Log file would help diagnose the issue further :)
Tim: have you had a chance to retest this? Also, 7.4 has release now, please verify the issue with that version of SBS..
I will try this out with 7.4 (I'm running the 7.4.1 nightly right now). It seems to be fixed, but let me try a few more alarm changes to check, over the next week or so. - Tim
7.4.1 is good to test with as well, let me know next week if you have issues or if I can close this one.
Tim: any update on this one? can I close it or are you still seeing an issue.
James... I'm not seeing this intermittently, still, in 7.4.1. Shall I enable the debugging you mention and let you know what I see? - Tim
Yes please, then attach the relevant parts of the log
Still trying to get it to fail. It's behaving much better than it used to. :-) But I'll try for the next few days, and leave the logging on, and if I see any problems I'll post them. If none by the end of the week, I'll comment that you can close this bug. - Tim
Damn, I turned on that logging level, but then installed a newer version of the nightly 7.4.1, and it happened again, but it appears to have reset the player.display logging level. And during the time I was modifying the logging level, the requisite time happened for it to go the screen saver display, which caused it not to happen the next time. Keep this bug open, because it's still happening. I won't install a new nightly, and keep trying to make it happen. - Tim
Created attachment 6167 [details] server log when cycling sleep times - skips 30 minute mark onscreen Ok, got it to do it again. Note after some time of letting it play something, go to Screen Saver, then cycle through sleep time selection, it goes from 15 to 45 (though onscreen it goes from 15 to "sleeping at end of song" to 45). The 1st cycle you will see 30 minutes mentioned, but then after I wait for the screen saver to take effect and do it again, you will see future cycles SKIP the 30 minute mark. - Tim
By the way, I'm too tired to do another test, but this MIGHT be connected to the fact that I played 1 song, let it go to screen saver, then chose a DIFFERENT song, and then cycled through sleep times before the screen saver had become active. This changing of songs after screen saver activated in 1st song, but not before activated in 2nd song, may trigger the problem (just guessing). - Tim
Tim: thank you for the extra effort in quantifying the issue.