PDA

View Full Version : Volume control bug



FB67
2008-08-25, 03:27
I have been searching these forums and found out that there were issues with volume control going crazy a few months ago.

I have just found out (by coincidence) that I can reproduce this error by attempting to adjust the volume level while the Controller is occupied by a search for an artist. The volume level turns to 100% without possibility to avoid it be pressing the decrease-button.

It is very unfortunate since I have all my players connected directly to active speakers, some of them quite powerful ;-)

System:
NETGEAR ReadyNAS NV+
SqueezeCenter version: 7.1.1 - 22377 @ Wed Aug 6 01:05:22 PDT 2008 - Netgear RAIDiator - DA - utf8
IP-adresse for server: 192.xxx.xxx.xxx
Perl version: 5.8.8 sparc-linux
MySQL version: 5.0.24a-Debian_3.infrant1

I know the SqueezeCenter is a beta version but I also had this issue with the first official releases of SqueezeCenter for ReadyNAS.

Does anyone know the status of this issue now?

Best regards
FB67

Ben Sandee
2008-08-25, 09:10
On Mon, Aug 25, 2008 at 5:27 AM, FB67 <
FB67.3ep27z1219660201 (AT) no-mx (DOT) forums.slimdevices.com> wrote:

>
> I have been searching these forums and found out that there were issues
> with volume control going crazy a few months ago.
>
> I have just found out (by coincidence) that I can reproduce this error
> by attempting to adjust the volume level while the Controller is
> occupied by a search for an artist. The volume level turns to 100%
> without possibility to avoid it be pressing the decrease-button.
>
> It is very unfortunate since I have all my players connected directly
> to active speakers, some of them quite powerful ;-)


I just tried to duplicate this on the latest 7.2 nightly builds and could
not (based on your description). My server is pretty powerful so the search
does not take long, but pushing volume-up during does not cause the voume to
max out or start increasing out of control.

Ben

Nonreality
2008-08-25, 13:31
I had a different volume control problem and going to 7.2 also fixed mine.