Bug 11106 - Confusing (Alarm) Volume Correlation Between SN and Boom
: Confusing (Alarm) Volume Correlation Between SN and Boom
Status: NEW
Product: SB Boom
Classification: Unclassified
Component: UI
: unspecified
: PC Windows XP
: -- normal with 4 votes (vote)
: Future
Assigned To: Unassigned bug - please assign me!
http://en.wikipedia.org/wiki/Up_to_el...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-16 13:38 UTC by Richard Tomlinson
Modified: 2011-11-06 23:23 UTC (History)
3 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Tomlinson 2009-02-16 13:38:57 UTC
Alarm volume settings in SqueezeNetwork go from 1 to 11.  On Boom, it goes from 0 to 100.  This becomes confusing when setting alarms.  

For example, when the alarm volume in SqueezeNetwork is set to "2", the alarm goes on at Boom volume level 10.
Comment 1 Chris Owens 2009-02-23 09:51:37 UTC
Matt, we're not saying we should abandon our long-held 'it goes to 11' joke, but just so you're aware.
Comment 2 Chris Owens 2010-05-06 16:05:08 UTC
Matt Weldon isn't available to us any more.  Please vote for this bug to make sure it appears in our priority list!
Comment 3 Richard Tomlinson 2010-05-06 17:07:21 UTC
I submitted the bug and I am totally aware and in agreement that the "it goes to 11" joke is appropriate, however, why don't we make the joke on both the SN and on the Boom.  For example, if the SN goes from 1 to 11, then the correlation to the Boom would be 0 to 110.

So,

1 on the SN would be a 10 on the Boom
2 on the SN would be a 20 on the Boom
etc...
11 on the SN would be a 110 on the Boom

Right now a 2 on the SN is a 10 on the Boom...
Comment 4 James 2010-05-06 19:03:39 UTC
To be fair, the 'turn it up to 11' isn't even a good joke.

I want a product that works, with a consistent interface between the Web UI and Local UI.

Currently there is no consistency and it sucks that it is this way.


The suggestion here that you modify both the Boom and the Web to get around the problem doesn't work.

There is a big difference in when setting the volume on the boom at 20 or 30!

Just bite the bullet people - set the Web UI to be the same scale as the boom?

Oh, and this bug has been open for how long now?
Comment 5 Alan Young 2011-11-06 23:23:10 UTC
Unassigned bugs cannot have a priority.