g-s-d Uneven volume hotkey weighting

Bug #45743 reported by Aaron Whitehouse
22
Affects Status Importance Assigned to Milestone
control-center (Ubuntu)
Invalid
Wishlist
Paul Sladen

Bug Description

If I press the hotkey to change the volume up (Fn+PgUp) then it does so in much smaller increments than the ones it has when I press the hotkey for volume down (Fn+PgDn).

As an illustration, it takes 31 presses to increase from mute to full and only 12 to reduce it back to mute.

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

NB: This is the same whether I have the headphones plugged in or not.

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

Using a fully updated Dapper Beta.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Changed in control-center:
assignee: nobody → desktop-bugs
status: Unconfirmed → Rejected
Revision history for this message
Paul Sladen (sladen) wrote :

This one isn't related to the interaction with the hardware-mixer on ThinkPads. It's related to there being far too many notches to ramp the volume up and not enough to ramp it down.

For reference, Apple have 16 steps on Mac OSX. IBM have 14 steeps on the ThinkPads. Twelve is not enough and thirty-two is too many.

In an ideal world I'd just set these back to (a) be the same, (b) both be sixteen. The Mute button is there for anyone who wants a quick solution to turn the music down and this is the only argument I've heard in favour of the unbalanced volume weighting.

No other piece of software I've come across has this functionality, so while it is novel and probably unique; I'm not sure that it should be deployed out-of-the-box.

Changed in control-center:
status: Rejected → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

rejecting the bug then, that's a duplicate and I don't want to spent 10 minutes to figure which one. Basically that's a feature, volume down goes fast because when the volume is too high you might want to go quickly to an acceptable volume, volume up has the granularity since there is no hurry that way

Changed in control-center:
status: Confirmed → Rejected
Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

Hi guys,

I have re-marked it as a duplicate of the other bug so that people interested in that one have a link to this one. If they are the same bug, however, then the title and description in that one really should be changed to reflect the fact that the behaviour occurs on all machines and not just thinkpads.

I know that my opinion here doesn't count for much, but I will give it anyway. I can see the logic in your reasoning why down should be faster than up but completely disagree that it should be like that. I have used literally hundreds of devices for which the logic would equally apply and *none* of them share this approach as it is counter-intuitive and user-unfriendly.

On this logic, my car stereo (often very important that I can turn it down quickly), my personal audio player, my stereo system, my TV, my clock radio and a plethora of other devices should all reduce volumes faster than they increase them. In all my interaction with media devices, my Ubuntu machine is the only thing that takes this approach.

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

To be clear, I own a Dell Inspiron 510m.

Revision history for this message
Paul Sladen (sladen) wrote :

Unduped from bug #39098 which is regarding syncronisation of thinkpad hardware and software mixers.

Paul Sladen (sladen)
Changed in control-center:
assignee: desktop-bugs → sladen
Revision history for this message
Patrick Horgan (phorgan1) wrote :

An ideal situation would be if gnome would give us something in the sound gui to set the step size. Then people that want equal/unequal, large/small, could all be happy. I found this trying to figure out where I would set the step size, I'm amazed that it's not user configurable. Could someone point me at the software I could rebuild and set the step size? I'm even willing to put in the ui and contribute it back if someone would give me a pointer to where to look.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.