Bugzilla – Bug 14846
Radio does not use correct alarm volume after playing music
Last modified: 2009-10-22 11:23:27 UTC
SBS 7.4 tunk @ SVN 28939, Radio at 7.4.1 r7866 - Radio was silent - created an alarm on Radio, set the volume to 40 with web UI - set Radio volume to about 15 - played music on Radio, set volume to 20 - turned off Radio (off mode) - wait for alarm When the alarm fired, it was at volume 20 I was subscribing to "alarm" and "mixer" CLI events and saw no mixer events when the alarm sounded.
I can't even set the volume to 40 in the MySqueezebox.com web GUI for the Radio and SB3. It only offers my values between 1 and 11 which are obviously scaled up in a way, but this is pretty strange (if at all you would expect 0..10), unpredictable and also too coarse.
Looks to be a problem where SP-side is getting erroneously "out of sequence" with the server after soft power off, so when alarm hits the out of sequence code kicks in and resets the local volume to what it was previously, rather than accepting the alarm volume setting. Tom and I both agree this bug is bad enough to hold up 7.4.1 release.
Created attachment 6175 [details] patch for Ben's review
Assigned to Ben for review. -- Power commands coming from the server were being looped back to the server, causing a temp player state out of sync state. Fix is to not update the sequence number and not loop the power command back to the server.
patch has my blessing. recommend checking it into 7.4/trunk
== Auto-comment from SVN commit #7907 to the jive repo by tom == == https://svn.slimdevices.com/jive?view=revision&revision=7907 == Fixed Bug: 14846 Description: - don't loopback power commands that came from server.
This bug has been marked as fixed in the 7.4.1 release version of SqueezeBox Server! Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.