I have the view the same, it should be so easy to resolve this problem
in the config file, it must be so simple to implement
In addition to the problems you mention, developers of third party
applications have to publish this fix and respond to queries of why
altering the volume level in their applications also alters the system
volume level.
For example, using Kodi, it would set the volume level every time a new
track was played, resulting in the user having to keep readjusting the
system volume level every time. My keyboard has these up/down volume
control buttons I use to set the system volume. Every time a track
started to play I would have to keep turning the system volume level
down because the software had raised it. I should be able to set a
maximum volume level for the system and not have it altered by applications.
So the question is how easy is it to change this default value and what
is stopping it from being implemented.
On 01/02/18 01:01, Roland Hieber wrote:
I came here because I was just playing [1] on headphones, and Firefox
seemed to think that it would be a good idea to set the master volume to
100%. My ears are still ringing. At least now I know what to do.
[1]: https://en.wikipedia.org/wiki/File:AFSK_1200_baud.ogg
The fix of changing "flat-volumes = yes" to "flat-volumes = no" in
/etc/pulse/daemon.conf seems to be fairly easy to implement, considering
the fact that this bug is blocking a great number of other bugs, and no
one here apparently has to say any word against it in the comments. Is
there something else blocking it?
- Roland
