Bugzilla – Bug 10662
Alarm at volume 0 is possible ... produces silence
Last modified: 2009-01-13 01:05:38 UTC
I have just reproduced this behavior on SC 7.3.1/linux with a Duet. I think I have seen exactly the same on a Boom (same SC version/platform but different machine). It is possible to set volume alarm to 0, so an active alarm will in fact not sound at all when it goes off. Since on slow machines the slider in prefs for volume can be sticky, I suggest setting a minimum volume to avoid user error. Perhaps allow to override/customize what the minimum is. The fact alarm volume is a shared property among all alarms is aggravating the problem, I think. Steps to reproduce: 1) Program an alarm 2) Set volume to 0 3) Apply and wait Alarm goes off, completely silent. Thanks in advance!
there may be a valid reason for a volume=0 alarm, maybe turning on a player triggers some plugin or something, but you don't want it to play anything.
(In reply to comment #1) > there may be a valid reason for a volume=0 alarm, maybe turning on a player > triggers some plugin or something, but you don't want it to play anything. > :) Perhaps you can disclose such a case ? Personally I can't see any use for a mute alarm. Reopen, please.
If you were to fix this, how would you choose a 'minimum' volume. If we removed 0, someone would file a bug that "volume 1 was too soft".
(In reply to comment #3) > If you were to fix this, how would you choose a 'minimum' volume. If we > removed 0, someone would file a bug that "volume 1 was too soft". > The abominable truth. Then I would propose something like the ipod max volume lock, but reversed: - Minimum alarm volume [ 10 ] (editable field, click-to-focus should help avoid errors) - Alarm volume [ 0...100 ] (slider with cursor lowest position stuck at 10) - Lock minimum alarm volume setting: [x] (when checked, the cursor would not go below 10; when uncheck, it could go down to 0) HTH
Editable field?? How about: if you choose 0, you should not be surprised at all when your alarm produces no sound.
(In reply to comment #5) > Editable field?? How about: if you choose 0, you should not be surprised at > all when your alarm produces no sound. > Look at the combo in iTunes. Apple has resolved they can't say "you should not be suprised to turn deaf". I am reporting about possible, inadvertent user action, not a conscious decision. Sarcasm is unwarranted.
I'm not being sarcastic. Alarm volume defaults to 50. I think it's completely clear from a UI perspective that if you move the slider to the left, the alarm will be softer, and if you move it to the right, it will be louder. This setting does not require any hand-holding.
(In reply to comment #7) > I'm not being sarcastic. Alarm volume defaults to 50. I think it's completely > clear from a UI perspective that if you move the slider to the left, the alarm > will be softer, and if you move it to the right, it will be louder. This > setting does not require any hand-holding. > As I said in my 1st message: "Since on slow machines the slider in prefs for volume can be sticky..." Case closed.
Even so, you wouldn't leave the volume at 0 and expect it to actually be some other value. I don't really understand your argument. But I agree, case closed, if you want to discuss this in the forum and make a case with other users, please feel free.