Bug 9490 – Alarm fallback behaviour fails when connected to SN

Bug 9490 - Alarm fallback behaviour fails when connected to SN

Summary:

Alarm fallback behaviour fails when connected to SN

Status:	CLOSED FIXED

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	Alarm
Version:	Prod
Platform:	All All

Importance:	-- normal (vote)
Target Milestone:	Falco
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-09-15 07:11 UTC by Max Spicer
Modified:	2008-12-15 12:24 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Use hardcoded sound effect for fallback when connected to sn (1.74 KB, patch) 2008-09-16 11:17 UTC, Max Spicer	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Max Spicer 2008-09-15 07:11:11 UTC

The alarm's fallback behaviour for failed alarm sounds is to pick 10 tracks at random and play them.  This fails when connected to SN.  We should use a suitable sound effect instead.  We still need to use the 10 random tracks when connected to SC as the internet connection could be down.

Comment 1 Max Spicer 2008-09-16 11:17:59 UTC

Created attachment 4004 [details]
Use hardcoded sound effect for fallback when connected to sn

The following patch uses the train whistle effect as a fallback when connected to sn.  I've hardcoded the fallback sound, but I bet someone will want it as a pref.  ;-)  Alternative sound for the fallback would be the foghorn.  I did a scientific survey of 1 other user and they preferred the train whistle.

I can't test this so I'll pass this bug on.

Comment 2 Andy Grundman 2008-10-10 09:27:15 UTC

Fixed, using backup alarm sound.

Comment 3 James Richardson 2008-12-05 13:53:35 UTC

Verified fixed in (sv) r5241/r24218

Comment 4 James Richardson 2008-12-15 12:24:21 UTC

This bug has been fixed in the latest release of SqueezeNetwork!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.