3 ms·

I think that shows why Gnome 3 is good. They won't add another knob if that needs tweaking. Somebody needs to fix the actual problem. Sounds to me like there is

by choffee 13y ago

I think that shows why Gnome 3 is good. They won't add another knob if that needs tweaking. Somebody needs to fix the actual problem. Sounds to me like there is an issue with the settings of some sound cards. If you sound card can make your amp cut out a 6% then I don't think that is a software problem. Like Network manager before it I think a lot of the sound problems point back to drivers or hardware not reporting back correctly. This probably needs to be tackled there.

jeremysmyth 13y ago
Sure. Clearly the best solution is one that addresses the actual problem, which is below the level of the UI. However, in conjunction with that (or indeed, in the absence of that, which is the current situation) the optimal solution is a sensible default, along with user-configurable differences for those users who have some opinion and technical acumen to use them. This has been the design philosophy of Linux applications and environments for a very long time, but for some reason is against the wishes of the Gnome 3 team.
chris_wot 13y ago
So not even a workaround whilst someone works on a fix? Has been two years. And wasn't it pointed out that the sound card won't always know the dB level?
hrjet 13y ago
This is not a driver problem, nor a case of hardware not reporting back correctly. The decibel information is not available in many sound setups. And it's never going to be available for these setups. Even for setups where decibel information can be gathered / estimated by the sound card, why should the volume increment be hard-coded? Shouldn't the user get to decide that? Also note that this setting was available in GNOME 2. Remove existing functionality without providing an alternate doesn't make sense to me, given that it is a potential health hazard!

3 ms·

I think that shows why Gnome 3 is good. They won't add another knob if that needs tweaking. Somebody needs to fix the actual problem. Sounds to me like there is

by choffee 13y ago

jeremysmyth 13y ago
Sure. Clearly the best solution is one that addresses the actual problem, which is below the level of the UI. However, in conjunction with that (or indeed, in the absence of that, which is the current situation) the optimal solution is a sensible default, along with user-configurable differences for those users who have some opinion and technical acumen to use them. This has been the design philosophy of Linux applications and environments for a very long time, but for some reason is against the wishes of the Gnome 3 team.
chris_wot 13y ago
So not even a workaround whilst someone works on a fix? Has been two years. And wasn't it pointed out that the sound card won't always know the dB level?
hrjet 13y ago
This is not a driver problem, nor a case of hardware not reporting back correctly. The decibel information is not available in many sound setups. And it's never going to be available for these setups. Even for setups where decibel information can be gathered / estimated by the sound card, why should the volume increment be hard-coded? Shouldn't the user get to decide that? Also note that this setting was available in GNOME 2. Remove existing functionality without providing an alternate doesn't make sense to me, given that it is a potential health hazard!