If decibels were used only to measure sound relative to "experienced loudness" there would be no complaint.
The complaint is that it is used in many other ways, often without distinguishing what the base unit is.
dB is only confusing if people omit which quantities they are relating. If it's clear like in the case of dBm which relate to 1 mW, it's an awesome tool.
When in analog audio, it usually means dbV, relative to a reference voltage.
And in digital audio, usually dBFS - relative to the maximum amplitude that can be represented.
EDIT if you did let’s say approximate power, or measure and present the consumed power (as some systems do) you would still be in a situation about how to present this data. Do you present your users with a simple 1-10 (logarithmic) or a 10 digit display which sweeps over vast ranges of uninteresting values.
If you opted for a more compact scientific notation … well guess what that’s also logarithmic but in two parts LOL
To me it seems like one of two things: external pressure between hot and cold is mismatched so a small change to one side overwhelms the weaker flow.
Alternatively it might just be a broken or poor quality mixer that isn’t providing the appropriate ‘nuance’ of control, and that may indeed be expressed as some sort of non-linear relationship.
It also a simple thing to check and would be the first step in my troubleshooting routine for this complaint.
Here is a link describing the dangers.
https://www.heatgeek.com/hot-water-temperature-scalding-and-...
I know you mean legionnaires' disease, but the idea of a bunch of soldiers getting to your house because you turned your boiler too low made me chuckle. Good thing the US have the third amendment to protect against this.
... hot water baths ..."
No need for an encoder and software, though, logarithmic pots are readily available for precisely this reason. :)
Ears can register sounds from maybe 20-30 dB upwards of 120ish which isn't a factor of 4-6 in terms of power but rather a factor of 120-30=90 decibels or 9 bels or 10^9 or one billion.
Because your ears have absolutely enormous range you need the potentiometer (pot) to have a logarithmic taper to it. The amplifier has an essentially fixed amount of amplification so that's a fixed sound dB output. Your ears can hear a vast range. A linear pot essentially locks the entire output into the same 10 decibels as the amplifier maximum output through its linearity. Once you've turned it to 10% of the range it has precisely 10 decibels worth of range left. If you want to turn the volume down by 40 decibels you have to do that within the 0-10% part of the pot's range.
A logarithmic pot will give you maybe 40-60 decibels worth of adjustment by dividing things up differently. Every 20% of the range increases the output not by 20% but by a factor of 10 let's say. That gives you a pot with a range of 50 decibels which is enough that it roughly matches the absolutely miraculous range of the ear.
You need a knob that increases power exponentially to hear a linear increase in loudness.
Pots do log and lin scales but they only have a limited angular range.
The volume control on my android phone was acting just like this when my headphones were connected. When changing the volume with the phone only a small section of the bottom quarter of the volume control actually made a difference, but the volume controls on the headphone themselves were acting "normally".
Usually the phone volume is fine, it only screws up on bluetooth devices (my speakers + my headphones). I have to use the volume control on the device itself to have any good control.
This explains the weird behaviour, the phone volume changes are being sent linearly, but the headphone/speaker settings are correct and being set logarithmically.
i.e. somewhere a developer working on the bluetooth integration didn't understand the difference, screwed up and never tested it. That it's happening to both my Edifier speakers and my cheapo headphones probably means it's on the stock Android end (it's a pixel phone).
Try going into Android "Developer options" and enable the option "Disable Absolute Volume". Some devices cannot handle the way Android maps the "master" volume of the system to Bluetooth. With the option enabled you will have a separate slider to adjust the Bluetooth volume, and the volume buttons will instead only control the "Media" volume.
An alternate thing to do is under the same Developer Options is instead of disabling Absolute control is to change the Bluetooth AVRCP version to at least v1.5. v1.5 AVRCP introduces the Absolute Volume control functionality.
But, it could also be what you may have are Bluetooth devices that do not support Absolute Volume, or lack AVRCP v1.5 compatibility. If none of this works, I suggest purchasing the "Precise Volume 2.0 + Equalizer" app. I use this as it gives you more fine-grained control over the number of steps in the volume slider (for example, I now have 100 steps). It also allows you to calibrate the number of steps to a specific device, so you can literally change how many steps from quiet to loud. It's worth all of the $10 it costs, and has other nice quality of life features as well.
OP isn't criticizing logarithmic scale in general but dB in particular.
If dB in particular aligned well with human experience - volume knobs would be labeled with dB values instead of 1-11.
People in the field get this wrong all the time — for instance, the volume control on ChromeOS appears to be a linear multiplier, yielding a control with huge perceived steps in the output between 0 and 3, and negligible perceived change in the output between 7 and 10.
I suspect that the confusing design of the dB contributes towards how often such mistakes get made.
This also doesn’t even begin to touch on frequency response curves.
A linear volume knob would be frustratingly useless as you would have to crank it many many many times the higher up you want to go. Presumably hundreds of times. A traditional pot couldn’t do that of course but maybe you could satisfy your curiosity with a rotary encoder?