After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791276 - Include a setting for over-amplification (allowing setting the volume over 100%)
Include a setting for over-amplification (allowing setting the volume over 100%)
Status: RESOLVED OBSOLETE
Product: gnome-tweak-tool
Classification: Applications
Component: general
3.27.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Tweak Tool maintainer(s)
GNOME Tweak Tool maintainer(s)
Depends on:
Blocks: 790988
 
 
Reported: 2017-12-05 17:02 UTC by Allan Day
Modified: 2018-02-07 18:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
sound: enable amplify above 100 percent key (2.14 KB, patch)
2018-01-10 12:41 UTC, Didier Roche
none Details | Review
sound: enable amplify above 100 percent key (2.16 KB, patch)
2018-01-10 13:58 UTC, Didier Roche
committed Details | Review
sound: install the new panel (784 bytes, patch)
2018-01-10 13:59 UTC, Didier Roche
committed Details | Review

Description Allan Day 2017-12-05 17:02:04 UTC
gsettings has a new key that determines whether the volume should be able to be set over 100% (see bug 790281). There have been various discussions about the best place to expose this setting; right now my suggestion is to put it in Tweaks.

The amplified volume setting primarily exists to allow pushing the output volume beyond the intended capabilities of the hardware in question - it's for when your laptop has tiny speakers but you want to use it a stereo.

Pushing the volume over 100% will typically lead to a reduction in sound quality. So, while it's nice to offer going over 100% volume, it is a kind of hack and isn't something that the hardware is designed to support, so Tweaks seems like an appropriate place to have it.

My understanding of what determines the maximum output volume of a device is somewhat rudimentary, so if someone knows a reason why this rationale is wrong, do speak up.
Comment 1 Didier Roche 2018-01-10 12:41:46 UTC
Created attachment 366600 [details] [review]
sound: enable amplify above 100 percent key

Add an option to enable amplifying main volume output above 100% in a new
"sound" category.
Comment 2 Didier Roche 2018-01-10 13:58:57 UTC
Created attachment 366601 [details] [review]
sound: enable amplify above 100 percent key

Add an option to enable amplifying main volume output above 100% in a new
"sound" category.
Comment 3 Didier Roche 2018-01-10 13:59:01 UTC
Created attachment 366602 [details] [review]
sound: install the new panel

Install the new sound panel in Tweaks.
Comment 4 Jeremy Bicha 2018-01-10 14:08:10 UTC
Comment on attachment 366601 [details] [review]
sound: enable amplify above 100 percent key

I'm pushing this without the meson change so that the new sound panel is not installed.

I didn't like having a tweak that doesn't have any effect, but my understanding is that there was some reluctance to make changes to other parts of GNOME before knowing where this UI was going to be for 3.28. Committing now also allows translators to start translating.

Attachment 366601 [details] pushed as 0d0fe3c - sound: enable amplify above 100 percent key
Comment 5 Frank 2018-01-10 23:18:15 UTC
Please consider my feature request #792033, as it targets not the symptoms, but the root of that whole problem.

In short:
• Compressing audio would make it louder – without the outgoing signals being able to go above the specified limits.
• This also would enhance quality in general, as the users then will then see, that louder music looses dynamic (often even drastically), and that they should learn to use the specified „normal level“ of 89 dB.
    – This would help for every audio material to be about the same level in the future – BIG problem nowadays!
    – Compressing the audio files itself is totally stupid, because this could also easily be done by output devices. Doing that in my proposed way preserves quality for people who invest in good speakers. ⇒ Why make the music shit for everyone, just for the reason that it’s louder for just subset of the people?!
• My proposal wouldn’t amplify audio linearly, so your ears won’t get blown away if you click on wrong (i.e. too loud) material while having this amplification active.
• We all know this guy, who always pushes his controllers to the limit – no matter how much distortion damages the speakers.
Comment 6 Jeremy Bicha 2018-01-10 23:38:28 UTC
Frank, thanks for your comments. However, the GNOME Tweaks app doesn't really control sound or volume. This bug is about a simple on/off switch for a feature. Maybe PulseAudio is a better place to discuss your ideas; I don't know.
Comment 7 Frank 2018-01-11 00:07:46 UTC
Yeah, that’s why I put it under g-c-c. ;) Just wanted to advertise it here, as I think it would be a better solution for increasing the volume.
Comment 8 GNOME Infrastructure Team 2018-01-24 15:27:49 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/111.
Comment 9 Jeremy Bicha 2018-02-07 18:31:47 UTC
Comment on attachment 366602 [details] [review]
sound: install the new panel

Attachment 366602 [details] pushed as 7ff3675 - sound: install the new panel