Bug 11234 - Boom Tone controls reset to default after removing power
: Boom Tone controls reset to default after removing power
Status: RESOLVED DUPLICATE of bug 11261
Product: SB Boom
Classification: Unclassified
Component: Audio
: 43
: PC Windows XP
: -- normal (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-02 13:54 UTC by Michael Kraft
Modified: 2009-03-12 11:02 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Kraft 2009-03-02 13:54:31 UTC
When setting Boom tone controls, after removing power, tone playback reverts to default levels. Boom user interface indicates tone control at previously set levels, and will change to user set levels once another change to the set level is introduced. 
I.E. user sets bass to level +15 and moves player to another room. In the other room, sound playback is at "normal" tonal levels. User will then change bass level, at which point, bass level will then change to new level.

Introduced by customer 
RN # 090225-001628

My testing : 
Retested while connected to SN with Boom user interface : same behavior
retested while connected to SC using Boom user interface : same behavior.
	did not test SC interface tone control

reproduce : 
Set tonal levels from Boom user interface or SN
remove power from unit
reapply power
Playback reverts to default tonality levels
SN and Boom user interface reflect levels previously set
modify levels from interface and Boom playback changes to new levels.

Thinking the preset tonality levels should stay in place, no?
Comment 1 Michael Kraft 2009-03-04 14:59:59 UTC
Was able to retest with another Boom connected to SqueezeCenter and using the tone controls from within SC.

Also experienced the same behavior of tonality output being reset to default values after a power cycle.

Cheers!
Comment 2 Michael Kraft 2009-03-12 07:46:59 UTC
Another customer experiencing this issue.
RN #090311-000976
Comment 3 EricH 2009-03-12 10:52:15 UTC
Just FYI, this is the same bug as #11261 reported by Felix Mueller. Can they be combined for ease of tracking? Thank you - Eric Huesman
Comment 4 Michael Herger 2009-03-12 11:02:51 UTC

*** This bug has been marked as a duplicate of bug 11261 ***