Bug 1577 – player volume gets reset to 0 if you power off/on when snoozing

Bug 1577 - player volume gets reset to 0 if you power off/on when snoozing

Summary:

player volume gets reset to 0 if you power off/on when snoozing

Status:	CLOSED FIXED

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

Importance:	P3 normal (vote)
Target Milestone:	---
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-05-18 13:17 UTC by Kevin Pearsall
Modified:	2008-12-15 12:13 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
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 Kevin Pearsall 2005-05-18 13:17:32 UTC

could it maybe go back to what it was before the alarm actually went off?

Comment 1 Blackketter Dean 2005-06-13 17:53:47 UTC

kevin: can you give a specific button sequence?  I think that this is because we fade out...

Comment 2 Kevin Pearsall 2005-06-14 09:35:54 UTC

it's not too complicated.  set an alarm for a couple minutes out, let the audio
come on, hit the power button, then hit power again to turn the player back on
and the volume will now be very low.

Comment 3 Dan Sully 2006-08-23 15:33:25 UTC

Is this still an issue with 6.5?

Comment 4 Marc-Aur�le Brothier 2006-12-07 11:34:18 UTC

Hi,

I have the version 6.5.0 and also the extra Alarm plugin, and the sound doesn't go to 0, but stay at 50, and I can't change it without removing the player configuration from the slimserver.conf file!
I tried to edit the volume control in the file to 100, but if I change the volume on the web interface, it drops to 50 and I can't change it anymore.... Neither with the remote, or the web interface.

I'm running:
SlimServer Version: 6.5.0 - 9916 - freebsd - EN - iso-8859-1

Comment 5 James Richardson 2008-06-30 14:42:07 UTC

Retest with SC 7.2

Comment 6 James Richardson 2008-07-09 10:23:51 UTC

Unable to reproduce, please retest then reopen the bug if you still experience errors

Comment 7 James Richardson 2008-12-15 12:13:47 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.