What developed when this issue was previously reported? The answer may surprise you!
It seems that PulseAudio takes a "minority view" on what the volume setting means. I have no direct experience with PulseAudio, but my understanding from previous comments is that it views a volume setting of 100% as meaning no amplification is applied, and therefore settings above 100% means that amplification is requested. IIRC (and I'd have to go code diving to be sure) ALSA (and probably most other sound subsystems) takes 100% to be the maximum volume of which the hardware and software is capable, and therefore a setting above that makes no sense (and may damage hardware).
MOC currently has no native PulseAudio sound driver and the PulseAudio ALSA emulation is used which may return a value outside the 0% to 100% range specificly set by MOC regardless. MOC views this out-of-range value as a bug, but, as previously suggested, there may be ways around it. Unfortunately, I don't run PulseAudio so testing is problematic.
A native PulseAudio sound driver is planned for MOC 2.6-alpha5 (although the original contributor seems to have gone silent), so that should resolve the problem anyway.
jcf
Sat, 2017-08-12 21:08
Permalink
PulseAudio's Minority View
What developed when this issue was previously reported? The answer may surprise you!
It seems that PulseAudio takes a "minority view" on what the volume setting means. I have no direct experience with PulseAudio, but my understanding from previous comments is that it views a volume setting of 100% as meaning no amplification is applied, and therefore settings above 100% means that amplification is requested. IIRC (and I'd have to go code diving to be sure) ALSA (and probably most other sound subsystems) takes 100% to be the maximum volume of which the hardware and software is capable, and therefore a setting above that makes no sense (and may damage hardware).
MOC currently has no native PulseAudio sound driver and the PulseAudio ALSA emulation is used which may return a value outside the 0% to 100% range specificly set by MOC regardless. MOC views this out-of-range value as a bug, but, as previously suggested, there may be ways around it. Unfortunately, I don't run PulseAudio so testing is problematic.
A native PulseAudio sound driver is planned for MOC 2.6-alpha5 (although the original contributor seems to have gone silent), so that should resolve the problem anyway.
MegaLite
Thu, 2017-08-17 16:13
Permalink
Thanks 4 answer)
Thanks 4 answer)