Bug 9405 - Restore original volume when alarm ends
: Restore original volume when alarm ends
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Misc
: 7.2
: All All
: -- normal (vote)
: 7.x
Assigned To: Max Spicer
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-05 07:26 UTC by Max Spicer
Modified: 2009-09-08 09:32 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments
alarm.log (2.83 KB, text/plain)
2008-10-26 03:35 UTC, Markus Schiegl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Max Spicer 2008-09-05 07:26:15 UTC
The alarm volume should only apply during an alarm.  At the end of the alarm, the original volume should be restored.

Only do this if music isn't playing when the alarm ends.  Also only do it if the user hasn't changed the volume during the alarm.
Comment 1 Jim McAtee 2008-09-05 22:47:29 UTC
I'd vote thumbs down to this one.  Sounds more confusing that practical.  The user hears music (the alarm) at one volume, plays something else (during or after the alarm playlist has ended), and then suddenly hears playback at a different volume level.

Or else make it an option.  If the alarm were playing a non-music tone then it might make sense, but since you're playing music, why would you need to do this?  
Comment 2 Andy Grundman 2008-09-06 05:50:32 UTC
My use case is this: Boom in the bedroom at around volume 10.  Alarm set to one of the sound effects at volume 40 (music will never wake me up).  Alarm goes off, starts fading in, hit snooze or power before it reaches 40.  Next time I go to play something (before bed the next night), the volume is at 40 and it's way too loud.

But you're probably right, it won't work for everyone.
Comment 3 Max Spicer 2008-09-16 11:32:38 UTC
My original idea was that the alarm volume would only be restored if the action that ended the alarm also stopped the music.  This would mean that there's always an off period between the alarm volume and the restored volume.  If the user ended the alarm by playing different music (bug 9364), then that would be seen as accepting the alarm volume.  Also, if they did anything to change the volume during an alarm, that would also stop the original volume being restored at the end of the alarm.  Would this work?
Comment 4 Andy Grundman 2008-09-16 11:34:32 UTC
Sounds great.
Comment 5 Andy Grundman 2008-09-18 12:10:49 UTC
*** Bug 9469 has been marked as a duplicate of this bug. ***
Comment 6 Max Spicer 2008-10-21 01:21:35 UTC
Behaviour described in #3 implemented in 7.3 as change 23634.  Volume is restored one second after alarm ends in order to avoid the volume fade that occurs on a stop/power.  Things get messy otherwise!
Comment 7 Markus Schiegl 2008-10-26 03:35:22 UTC
Created attachment 4170 [details]
alarm.log

i think there may be a regression because of this change.

system:
- SC 7.3trunk
- transporter connected with digital+analog outs
- volume control: volumes control adjust outputs
- volume: 100%

use case:
- alarm goes off (11:20)
- press power button to stop alarm (11:21)
- wait 10 seconds
- press power/play buttons to resume manual playback (11:22)
- (volume is muted/no sound)
- press volume up/down one time to restore the volume level (100%)

i've attached a logfile. What's suspicious is that the volume level seems to be extremely low (2.6e-06) which is not the case (SC shows all bars, same applies to the transporters display). any ideas?
Comment 8 James Richardson 2008-12-15 12:07:19 UTC
This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 9 Chris Owens 2009-07-31 10:29:11 UTC
Reduce number of active targets for SC