Bug 11663 – SB3 volume changes while playing synced to Transporter

Bug 11663 - SB3 volume changes while playing synced to Transporter

Summary:

SB3 volume changes while playing synced to Transporter

Status:	RESOLVED WORKSFORME

Product:	SB 2/3
Classification:	Unclassified
Component:	Audio
Version:	125
Platform:	Other Ubuntu Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-04-05 09:13 UTC by Joerg Schwieder
Modified:	2009-11-10 03:26 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 Joerg Schwieder 2009-04-05 09:13:50 UTC

While doing a side-by-side test against Transporter, I noticed that the volume on my SB3 changes on it's own from time to time.

The setup was that I synced SB3 to the transporter and set the volume to the same level on both devices.
When playing at a level of 75, after a while the level on the SB3 (but not on the Transporter) dropped to 74. This was reproducible in that it happened again after a while when I reset the volume to 75.
The difference was audible (that's how I noticed it), not just a matter of displaying a different value.

When playing at an output level of 60 I got similar behavior, but now the volume INCREASED to 61. Again: reproducible.

SC is 7.4 r25118

Comment 1 James Richardson 2009-04-06 09:50:20 UTC

QA to reproduce, and generate logs

Comment 2 James Richardson 2009-10-01 13:49:26 UTC

Joerg: are you still seeing this issue?

What outputs are you using on the SB3 and Transporter

Comment 3 Joerg Schwieder 2009-10-01 13:52:45 UTC

I haven't tried again because my poor SB3 is now my test device and connects to a different server. And I scrapped the amp I used for this so I think I'm not even able to reproduce it anymore.

Since this was side-by-side testing I believe it must have been RCA out on both the SB3 and the Transporter.

Comment 4 James Richardson 2009-10-01 13:53:49 UTC

Thanks, I'll continue to investigate this then...so far I have not seen the issue but will keep trying

Comment 5 James Richardson 2009-10-06 15:58:22 UTC

Some testing done, still can't reproduce the issue.

Comment 6 James Richardson 2009-10-21 20:43:21 UTC

We just released 7.4.1 and while this issue may not have been addressed directly, there was one volume issue that was fixed.   Could you please re test with 7.4.1 ?

Comment 7 James Richardson 2009-11-05 09:44:25 UTC

No additional information from reporter, QA has never been able to replicate this issue.  Marking as works for me.  If you are able to replicate, please feel free to reopen the bug and provide more feed back

Comment 8 Joerg Schwieder 2009-11-05 09:52:06 UTC

Sorry, I would have tried this earlier but I did have a hardware failure on the server I need for this.
I will try either tomorrow or early next week and re-open the bug if it still shows up.
Not sure why it was so hard to replicate though, this was always fully reproducible for me with SC 7.3.3
Is it OK to only try with 7.5.0 beta?

Comment 9 James Richardson 2009-11-05 09:56:32 UTC

7.5.0 should be good // that will be the next release :P

Comment 10 Joerg Schwieder 2009-11-10 03:26:28 UTC

OK, tested this today and it looks fixed to me.
The whole display is of course now different with the "-xxdb" display instead of the "xx" level display 7.4 had when I first reported it, also I can't reproduce the original setup since I don't get any volume display on the device itself anymore when I change volume using the Controller or iPeng.