Red Hat Bugzilla – Bug 501599
changing output device while device is in use causes volume to jump to 100% = nasty
Last modified: 2009-08-19 14:45:26 EDT
+++ This bug was initially created as a clone of Bug #489049 +++ > 3.) switching sound does reset the sound volume to 100% which is > probably not what should happen... either keep the volume of the > old device or keep track of saved volumes for every device? That's not normal, and I haven't seen that problem. Is it the app volume, or the hardware volume changing? > Any of those worth filing new bugs for? Yes. --- Additional comment from michael.monreal@gmail.com on 2009-05-02 11:38:52 EDT --- (In reply to comment #10) > That's not normal, and I haven't seen that problem. Is it the app volume, or > the hardware volume changing? Here's what I did: - started totem, set app volume to 100% and started a song - set the global output volume to 75% using the tray icon. Totem now reports a volume level of just 8% (why that? totem bug?) - inserted headset, opened sound preferences, switched output => totem, tray icon, "output volume" in sound preferences *all* show 100% volumes now Switching output device back I can reproduce the same thing every time.
This is reproducible on my hardware. audio1: nvidia on board sound -> 5.1 surround amp. Amp turned up full. (this gives the computer the full range of the amp volume). audio2: pci soundblaster live -> headphones Play some audio. defaults to output via audio1, adjust volume sensibly to 30%. gnome-volume-control-applet: in output tab choose audio2. Ears begin bleeding. Reason, main and app volume jumped to 100%. Turn that back down to 50%. Quickly select the audio1 device. Now I've got music at 100dB SPL in the room. alsa-info report at: http://www.alsa-project.org/db/?f=23db04e4a7aeaa23357d00481f38b86638e90b21
This is some interaction between app volume(s) and the sink volume. Disabling the flat volumes probably works around the problem.
Hmm, I think I noticed that g-v-c resets all volumes to 100% each time you change the default device. I am tempted to say that this is a g-v-c bug, not a PA bug.
Does it? Is there any other pieces of code that can do what gvc does to move the stream instantaneously so we can verify this?
(In reply to comment #4) > Does it? Is there any other pieces of code that can do what gvc does to move > the stream instantaneously so we can verify this? pavucontrol does it. Hmm, actually you might be right and this is not a gvc bug. I need to investigate this further I guess.
Any findings, Lennart ?
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
In F12 when moving streams we convert from absolute to relative volumes before moving and then back after. That should make sure that the stream volume is not surprisingly high on the destination device.
Yes, when I tried this the other day, it worked nicely.