Description of problem: Pulseaudio added a new config setting: flat-volumes= Enable 'flat' volumes, i.e. where possible let the sink volume equal the maximum of the volumes of the inputs connected to it. Takes a boolean argument, defaults to yes. The upshot of this is that if you have set your master volume to 45% for some reason like "other people are trying to sleep" or "you are wearing headphones and that's a good volume" or to 5% because you're in a library and want alert sounds to be just barely loud enough for you to hear, and you start up *any* process that tries to set its own audio volume to 100% (like the default behavior of Banshee), you suddenly find yourself WITH AN EARFUL OF VERY LOUD STUFF. Who thought this was a good default behavior??!? (And no, "fix Banshee" is *NOT* the right answer here - we shouldn't have to hunt down and fix every single client program to work around a poor choice of defaults in the daemon. Version-Release number of selected component (if applicable): pulseaudio-3.0-5.fc19.x86_64 How reproducible: Set master volume to 30% using alsamixer or other tool. Start Banshee and hit 'play' on something. Stand back and be amazed. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 868077 has been marked as a duplicate of this bug. ***
Just my opinion, but apps that reset the global volume are misbehaving (badly).
and I have doubts any PA maintainer would entertain changing this upstream default, closing
"apps that reset the global volume are misbehaving (badly)" Totally agree - which is why flat-volumes= is such a design crock - the only use I can see for it is to allow badly misbehaving apps to screw with the global volume.