Bug 15662 – Alarm-Volume-Level with synchronised Booms

Bug 15662 - Alarm-Volume-Level with synchronised Booms

Summary:

Alarm-Volume-Level with synchronised Booms

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Alarm
Version:	7.4.2
Platform:	PC All

Importance:	P3 normal (vote)
Target Milestone:	7.5.1
Assigned To:	Alan Young

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-02-08 11:35 UTC by stephan.grahl
Modified:	2010-09-13 12:01 UTC (History)
CC List:	1 user (show)

See Also:
Category:	Bug

Attachments
Proposed patch (599 bytes, patch) 2010-03-10 07:27 UTC, Alan Young	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 stephan.grahl 2010-02-08 11:35:38 UTC

When two full-synchronised Booms stopped together at night with sleepmode, the next morning the alarm-volume-level is the level of the night and not the level of the alarm-settings.

Comment 1 Alan Young 2010-03-08 23:43:07 UTC

Is that for (a) both Booms, (b) only the one for which the alarm is configured, (c) only the one for which the alarm was not configured?

Do you have one or both booms configured to synchronize volume (Settings / Player / <player> / Synchronize / Synchronize Volume, in the WebUI)?

Comment 2 stephan.grahl 2010-03-09 07:55:19 UTC

It's on (a) both booms and the volume level is synchronized on both settings (booms)

Comment 3 Alan Young 2010-03-10 07:27:10 UTC

Created attachment 6628 [details]
Proposed patch

Comment 4 Chris Owens 2010-04-07 18:10:19 UTC

Targeting for 7.5.1 at Ben's suggestion that all patch_waiting bugs be fixed

Comment 5 SVN Bot 2010-04-08 01:27:28 UTC

 == Auto-comment from SVN commit #30506 to the slim repo by ayoung ==
 == http://svn.slimdevices.com/slim?view=revision&revision=30506 ==

bug 15662: Alarm-Volume-Level with synchronised Booms 
Use CLI 'mixer' command to set volume levels for alarms.

Comment 6 Chris Owens 2010-09-13 12:01:48 UTC

Since these are fixed, they must not be patch_waiting after all