Bugzilla – Bug 4934
Volume display in web interface shows 1-11
Last modified: 2009-01-05 21:54:31 UTC
The volume display shows 1-11 as choices, which map to 0%-100%. It would seem much more logical to label these 0-10, and with one small change to volumecontrol.html, it pops out: add a '- 1' to the 'loop.count' display. here's a diff, but it's hard to see because of the run-on line. See the -1 in the [% loop.count %] clause. ------- volumecontrol.html ------- 4c4 < [% IF volume != vol || activelink %]<a href="status.html?p0=mixer&p1=volume&p2=[% vol %]&player=[% playerURI %]&start=[% start %]">[% END %][% IF volume == vol %][% activeon || '<b>' %][% END %][% loop.count %][% IF volume == vol %][% activeoff || '</b>' %][% END %][% IF volume != vol || activelink %]</a>[% END %] --- > [% IF volume != vol || activelink %]<a href="status.html?p0=mixer&p1=volume&p2=[% vol %]&player=[% playerURI %]&start=[% start %]">[% END %][% IF volume == vol %][% activeon || '<b>' %][% END %][% loop.count - 1%][% IF volume == vol %][% activeoff || '</b>' %][% END %][% IF volume != vol || activelink %]</a>[% END %]
Watch Spinal Tap. You'll get the joke. http://www.youtube.com/watch?v=AhVWJgIzftE
The amusing side effect of "it goes to 11" notwithstanding...
Sorry that you don't like it, but that is the design. There are other skins that handle it differently if it bothers you too much. I'll leave this open, in case QA decides to flag it as an 'enhancement request' for some reason.
I'll go ahead and change it to an enhancement request. Who knows, at some point we may decide that having a sense of humor is unacceptable, or users may genuinely wish to have it fixed, in which case they can vote on it as usual. But as KDF mentions, as surprising as it may seem, this feature is by design.
We have changed our mind. In the future, if warranted, we may choose to re-open the bug. But for now I have set its status to WONTFIX.
Wow. That is just one steaming pile of prissy commentary, isn't it? I'm not torqued by it one way or the other. I actually went looking for a comment, expecting to find one. Since I didn't, I assumed it wasn't intentional (since, to really be the joke, it should go from 0 to 11 anyway). But for God's sake, don't let me get in the way of humor. I certainly never cared enough to keep this bug open. But you guys *might* imagine that not everything is obvious, and start out with an attitude of "I wrote this, and I intended to" next time, instead of assuming complete ignorance and humorlessness on your audience's part. I likely saw the movie before a few of you were born. and you might leave a comment to make your intentions clear. or, you know, whatever. "having a sense of humor is unacceptable" indeed. I'd have expected better from the authors and maintainers of such a fine product.
I look at a lot of bugs every day, and when several members of our team and community point me at one in particular, I try to give it prompt attention. In addition I try to take every bug seriously, so I prefer to be open to the possibility that a bug is a real problem. For instance, there have been discussions recently that 11 is not enough granularity (which would cause this issue to disappear automatically if that is addressed). There have also been discussions on the forum that Logitech will ruin Slim Devices, which I also hope does not happen. That concern may have colored my response as I considered what this product would be like if some misguided corporate manager dictated to us that we couldn't slip in a joke now and then. I apologize if I came off brusquely.
Okay this bug has come up again, and the new issue is this: not so much that the volume is 1-11, but that '1' is mute.
0 should be mute. i love the going to 11 thing, so if granularity is needed, why not do: 0.0 to 11.0 that way you could have 05.7 but still end at 11. that would give you 110 levels of db, yes?