Bugzilla – Bug 14239
No ability to set Alarm sound during process when adding a new alarm
Last modified: 2010-05-27 14:45:55 UTC
Squeezebox Radio fw 7671 When adding new alarms, there is no choice to set the Alarm sound (defaults to backup sound). After the alarm created, you can set the alarm sound. Thanks, LaRon
IMO this is not a bug. The happy path should only involve setting the alarm time, and should default to Current Playlist for the sound. There is a separate bug open for the non-obvious nature of the alarm advanced options, so I say this one is a WONTFIX
I disagree. In the case I was testing the Current Playlist was empty, and by default I'm sure I wouldn't want an unknown alarm sound. ("unknown" from a customer's perspective.) Besides, the whole notion of the "current playlist" is _not_ an easily understood idea for our users, IMO. I think a default alarm sound is a perfect idea, but it should be picked the very first time you create an alarm, perhaps? That way going forward I can just create a new alarm and be sure I'm getting what I expect. I'd like this left open for review. Matt, when time permits can you chime in?
just for clarity: you _can_ set an alarm sound. What we need to fix is the obviousness of that setting. I do not agree that setting a new alarm should prompt the user for anything other than the time they want to wake up. the server-side fallback alarm, which sounds when the current playlist is empty or unplayable, sounds like an alarm clock tone.
These bugs have all been marked resolved and belong to a component which is being removed. Therefore they have been moved to the most applicable of the new components.