Bug 16354 - Backup / Fallback Alarm Play inappropriately
: Backup / Fallback Alarm Play inappropriately
Status: CLOSED FIXED
Product: SB Radio
Classification: Unclassified
Component: Alarm
: Include FW version in comment
: Macintosh MacOS X 10.6
: P1 critical (vote)
: 7.6.0
Assigned To: Ben Klaas
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-09 11:59 UTC by Len Whitten
Modified: 2011-05-06 10:58 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Len Whitten 2010-07-09 11:59:50 UTC
Loud "funky" music is playing instead of audio that was set. 
2 alarms: 1st came on correctly. 2nd had the incorrect funky loop w/o fade-in come in very loud.

i can reproduce this behavior by setting up an ethernet link, removing the cable, and letting the alarm trigger.

i have a reliable network, and it does not matter whether i am connected to mysqueezebox or squeezebox server. 

the other morning, i had turned off the 1st alarm (set for 4:38), but when the squeezebox server (mac) woke up at 4:30, it triggered the backup alarm.

My wife has literally said the radio must be replaced, in no uncertain terms. I've tried to discover the problem/work-around for months now, and she's finished.
Comment 1 Alan Young 2010-07-16 02:48:19 UTC
The 'Loud "funky" music' is what you get when an alarm fails to fire. It is the backup alarm to ensure that you get woken up.

What kind of stream was being used for the second alarm that failed? This is possibly a duplicate of bug 16190.

What was the interval between the two alarms? Had the first alarm finished before the second was due to start? This could be bug 15832.
Comment 2 Len Whitten 2010-07-17 12:33:30 UTC
Alarm #1 was for 4:38am. Selected "turn off alarm" almost immediately. Source was one of the natural sounds, network was mysqueezebox.com.
Alarm #2 was 5:15am, still one of the natural sounds.
I had selected the natural sounds because I thought they were built-in, and would not be subject to network erro.

I have now switched to the SB server, made sure the server wakes up at least 15 mins before the alarm, and for the most part, things work well. However, I noticed on SB server that alarm was set for 4:37. I changed it on the server to 4:38.

At 4:37, the failover alarm came on, followed (after that was turned off) by the correct alarm at 4:48. 

Things seem to work a bit better if I reboot after I change an alarm source or time. Which luckily doesn't occur often.
Comment 3 Ben Klaas 2011-04-12 09:14:31 UTC
Is this a bug anyone is still experiencing?

For the record, the behavior of a squeezebox radio alarm when either a) not connected to the network or b) without a connection to the server, is to play the internal alarm sound, which is that "funky" music.

There have been changes in the code in current versions of firmware, particularly 7.6.0 where I've tested this, for that fallback alarm to obey the volume setting for the alarm, as well as fade in. So the loud aspect of that should be fixed, unless of course the configured alarm is also set to be loud.

Marking this bug as resolved, pending further information
Comment 4 Paul Chandler 2011-05-06 10:58:22 UTC
Verified on 7.6 32390  with Touch FW r9430

Uses 'fall-back' alarm if no network connection is found