Car manufacturers are easily the winners here. If your car’s audio system doesn’t have a simple knob you can grab and twist, well, that just sucks.
Ford moved volume control to the touchscreen, but people wanted a knob. Solution? They stuck a knob to the touchscreen. Under the knob is an artificial "finger" that touches the screen. I haven't used it personally so all I can say is it's a hilarious solution. https://techcrunch.com/2020/12/02/im-obsessed-with-the-ford-...
The worst volume control UI in the world (2017)
31–40 of 490 posts
Re: The worst volume control UI in the world (2017)
#32The one asking the user to make noise as loud as you want the volume to be made me laugh but it does have a hidden feature... It will never be lower than ambiant noise. Perhaps a desireable feature?
Re: The worst volume control UI in the world (2017)
#33In principle, if my headphone volume was actually loud enough to damage my hearing, I'd like to be told about it, but a given reality is the volume setting doesn't produce the same loudness with different headphones, which usually results in an inconvenience when my headphones aren't actually very loud.
Re: The worst volume control UI in the world (2017)
#34Nearly all volume controls suck because by and large the software world is ignorant of the fact that loudness scales logarithmically. 99.9% of volume controls scale the output linearly.
This is in the same category of error as most programmers thinking that sRGB uses a linear light model. They try to do arithmetic like blending or blurring on the raw image data this inevitably does the wrong thing. Similarly, most non-AAA game engines ignore the sRGB tone curve and treat all inputs and outputs as if they were linear, which results in unexpected brightness shifts in textures. Up until very recently,…
Re: The worst volume control UI in the world (2017)
#35Re: The worst volume control UI in the world (2017)
#36But that comes second to the microphone gain control, which Teams similarly exerts unilateral control over - only this time through an automated algorithm that for some microphone types just ends up muting them entirely. It's wild, you can go into the Windows gain control settings and see the slider wiggle around.
Re: The worst volume control UI in the world (2017)
#37Nearly all volume controls suck because by and large the software world is ignorant of the fact that loudness scales logarithmically. 99.9% of volume controls scale the output linearly.
It’s weird how I nominally know this but never really thought about the implications... How does the hardware world do it? I’d expect the normal way to make a volume control would be to have an adjustable-gain amplifier using the standard opamp circuit somewhere, but those aren’t logarithmic in any resistance you could wire to a knob, are they? (Yes, I am deeply ignorant about electronics.)
https://learnabout-electronics.org/Resistors/resistors_09a.p...
Re: The worst volume control UI in the world (2017)
#38Car manufacturers are easily the winners here. If your car’s audio system doesn’t have a simple knob you can grab and twist, well, that just sucks.
Ford moved volume control to the touchscreen, but people wanted a knob. Solution? They stuck a knob to the touchscreen. Under the knob is an artificial "finger" that touches the screen. I haven't used it personally so all I can say is it's a hilarious solution. https://techcrunch.com/2020/12/02/im-obsessed-with-the-ford-...
Now we have a chip shortage, and not even a radio with volume control can be made without a chip that is backordered for 1y+
Re: The worst volume control UI in the world (2017)
#39Earlier quoted context omitted.
This is in the same category of error as most programmers thinking that sRGB uses a linear light model. They try to do arithmetic like blending or blurring on the raw image data this inevitably does the wrong thing. Similarly, most non-AAA game engines ignore the sRGB tone curve and treat all inputs and outputs as if they were linear, which results in unexpected brightness shifts in textures. Up until very recently,…
Could you provide good documentation about such thing?
[0] http://blog.johnnovak.net/2016/09/21/what-every-coder-should... [1] https://news.ycombinator.com/item?id=27721094