Remix.run Logo
lambdaone 2 days ago

It's a bit like hating numbers, and saying "What do you mean by 'three'; what is it - three volts, three amps, three metres? Clearly 'three' is meaningless, and we should stop using it and all the other numbers besides."

decibels are simply a dimensionless ratio, used as a multiplier for some known value of some known quantity.

In every context where decibels are used, either the unit they qualify is explicitly specified, or the unit is implicity known from the context. For instance, in the case of loudness of noise to human ears in air, the unit can be taken to be dBA (in all but rare cases which will be specified) measured with an appropriate A-weighted sensor, relative to the standard reference power level.

And similar (but different) principles apply to every other thing measured in dB; either theres an implicit convention, or the 0 dB point and measurement basis are specified.

People who assume that everyone is an idiot but themselves are rarely correct.

I look forward to the author discovering about (for example) the measurement of light, or colorimetry, and the many and various subtleties involved. The apparent excessive complexity is necessary, not invented to create confusion.

sanderjd 2 days ago | parent | next [-]

> In every context where decibels are used, either the unit they qualify is explicitly specified, or the unit is implicity known from the context.

The author's whole point is that this is not true.

To adapt your analogy, it's not like being mad at the number three, it's like being mad about people not attaching any units to the number three, arguing that it's clear in context. It isn't!

drob518 2 days ago | parent | next [-]

Just because the author is ignorant of the context doesn’t mean that the engineers working in those fields are. They use it because it all makes sense in context.

LastTrain 2 days ago | parent | next [-]

Yeah hence his comment “If you know you know.” The author is far from ignorant on the subject, he’s pointing out the unit is often used without context.

hulitu 2 days ago | parent [-]

[flagged]

marcosdumay a day ago | parent [-]

You may have missed the short article explaining how it could mean 3 different things in an audio context, or 3 other different things in a radio context. Or how it doesn't actually mean anything by itself and yet people insist on using it that way.

Nevermark a day ago | parent | prev | next [-]

The point of units is to indicate both what dimension, and relative magnitude in that dimension, is being talked about clearly.

In virtually any other situation, leaving off units and counting on context to fill them in would be considered to be at the extreme end of unacceptable.

The unit problems in question, are only accepted because they are an historically created anomaly. Not because they are a good idea, or anyone wanted that outcome.

sanderjd 2 days ago | parent | prev [-]

This is literally the same as saying that you don't need to explicitly specify units in any field because "it all makes sense in context" to "engineers working in those fields".

No. We've painstakingly figured out the right answer to this through the generations of doing science and engineering: You always specify units.

drob518 2 days ago | parent [-]

But obviously we don’t. So, there’s your counter proof.

strbean 2 days ago | parent | next [-]

Except the various disasters caused by assuming the wrong units (Mars Climate Orbiter, for example).

monster_truck 2 days ago | parent | next [-]

The team that wrote their code in English units instead of Metric defied specifications, that has nothing to do with this.

> The Software Interface Specification (SIS), used to define the format of the AMD file, specifies the units associated with the impulse bit to be Newton-seconds (N-s). Newton seconds are the proper units for impulse (Force x Time) for metric units. The AMD software installed on the spacecraft used metric units for the computation and was correct. In the case of the ground software, the impulse bit reported to the AMD file was in English units of pounds (force)-seconds (lbf-s) rather than the metric units specified.

From https://llis.nasa.gov/llis_lib/pdf/1009464main1_0641-mr.pdf

seanhunter a day ago | parent [-]

Hey don't blame the English for that. I would be prepared to wager you couldn't find a single English engineer who uses lbfs or anything similar. Everyone in physics or engineering uses metric for everything to do with forces even those who might use mph for a speed informally.

monster_truck 12 hours ago | parent [-]

Nobody is blaming the english for anything, those are simply the units they used.

drob518 2 days ago | parent | prev [-]

Which proves what? That misunderstandings happen? Yes they do. Get over it. But most amplifiers and recordings don’t crash and burn, so there’s your counter proof. Use units when they might be ambiguous. But in many fields they aren’t.

Nevermark a day ago | parent | next [-]

> But in many fields they aren’t.

I am lost. What fields you are talking about?

1. I am unaware of any field operating within its own echo/context chamber using unit-less numeric notation for anything but actual unit-less quantities. Except for informal slap-dash arithmetic, on trivial calculations.

2. Units indicate the dimension being measured, not just the relative magnitude within that dimension. Nobody is going to know from any shared context, except in person, what a bare number measures.

3. Virtually every measurable quantity has multiple possible units of different relative magnitude, depending on micro context, so even people within a field, who agree on the dimension measured, still need units. Meters, light years, AU, angstroms?

4. You cannot apply standard formulas of physics, or anything else, without specific units. Formulas operate on dimensions, but to interpret and calculate any numbers, you need to know the specific unit being used for each dimension.

(In any context, but a late night napkin argument between two well acquainted colleagues in a bar, units are universally used. And in that case, the opportunity for serious misunderstandings is more likely to be from missing units, than the quantity of scotch each has imbibed, or how much they have spilled on the napkin.)

drob518 a day ago | parent [-]

You’re arguing both sides. If nobody does it then it’s not a problem.

ashoeafoot 2 days ago | parent | prev [-]

No, this are the sounds of underspecification.

sanderjd a day ago | parent | prev [-]

The meaning of my last sentence is "You (should) always use units (or else there will inevitably be some mistake eventually due to confusion about the units)".

klodolph 2 days ago | parent | prev | next [-]

Sure, but the author is wrong.

“How old is your son?” “He’s 3.”

Clear in context. People write things like dB SPL (A-weighted) in spec sheets because spec sheets benefit from being unambiguous. Most of the time it’s really clear, like you’re talking about insertion loss or amplifier gain and there’s only one reasonable way to interpret it.

timeinput a day ago | parent | next [-]

But for insertion loss and amplifier gain it is "just" dB, it's the ratio of the input to the output. The amplifier has a gain of 35 dB means its output is 35 dB higher than the input. If the input is -30 dBm the output is +5 dBm, etc. The reference for an amplifier, or insertion loss is clear in context since you're talking about the gain / loss of a device, and isn't referenced to any fixed scale like db relative to 1 mW, SPL (A-weighted), or 1 volt.

On detailed spec sheets they list the gain of amplifiers as xxx dB.

RichardLake 2 days ago | parent | prev | next [-]

That depends, the dropped unit could be either a year or a month.

jchw 2 days ago | parent | next [-]

You don't drop the unit for months, so it's not ambiguous in context.

klodolph 2 days ago | parent | prev [-]

It’s understood in context, that’s the point.

pzo 2 days ago | parent [-]

no it's not - it's assumed by maybe taking the most likely unit (year). But if the conversation is in hospital with your kid having emergency I guess doctor would appreciate to know if they will have to do surgery on 3 months child or 3 years kid.

observationist 2 days ago | parent | next [-]

If the doctor has trouble figuring out the difference between 3 months and years, there are bigger problems than specificity.

There are places specificity is necessary, and there are places the implicit assumptions people make are specific, and only need additional specification if the implication is violated. That's how language works - shortcuts everywhere, even with really important things, because people figure it out. There are also lots of examples of this biting people in the ass - it doesn't always work, even if most of the time, it does.

icehawk 2 days ago | parent | prev [-]

A 3 month old kid looks very different to a 3 year old kid.

pzo 2 days ago | parent [-]

and thats the exact point - you assume doctor see the kid instead of you calling doctor or doctor is getting briefed by emergency stuff.

thowawatp302 2 days ago | parent [-]

Exactly! It makes sense in context.

marcosdumay a day ago | parent [-]

As long as you construct a strawmen strict enough that can be no ambiguity, and refuses to acknowledge any context where it's not enough, yeah, it always make sense in context.

conorjh 18 hours ago | parent [-]

[dead]

jayd16 2 days ago | parent | prev | next [-]

When you say 35 it would be strange for it to be anything but years.

3 days, weeks, months or years are ironically all common units when someone is "3".

seanhunter a day ago | parent | next [-]

No one actually says "my child is 3" meaning anything other than 3 years. They would say "3 days", "3 weeks" or "3 months" meaning the other lengths of time.

MyOutfitIsVague a day ago | parent | prev | next [-]

Not where I live. You'd never specify how old somebody is with a bare number and have it mean anything other than years in the US. "My kid is 3" is always 3 years. So is "How old is your Tammy?" "Three". That only ever means years. Every other unit is always explicit. In my decades as a parent and being around other parents of kids and newborns, I've never experienced an exception to this.

sanderjd a day ago | parent [-]

That's the point. If you are talking colloquially to someone where you live, sure, whatever, this doesn't matter. But if you are writing something down in some publication for a wide and unpredictable audience, you should use units.

bigstrat2003 a day ago | parent | prev [-]

Most of the time if someone says "he's 3", it is a good bet that they mean 3 years. People usually specify if they mean days/weeks/months with respect to someone's age. Not always, of course, but it's definitely uncommon to drop the unit when it's anything except years.

viraptor 2 days ago | parent | prev | next [-]

That only works if you're already familiar with the context and system and assume other people are too and don't care about anyone new to that area. (Good luck coming to the audio equipment datasheet with no experience and figuring out what the dB means in each case) "He's 3" works because of the previous question and because everyone had experience of talking about age.

dB for anyone not already knowing the answer is like going to another planet and hearing "he's 3". Of course it's on a logarithmic scale, offset to -5 as starting point, counting the skin shedding events - clear in context and you should've known that.

klodolph 2 days ago | parent | next [-]

Maybe I just live on the planet, but I don’t have this problem with dB and to me, it sounds like you’re the alien. Maybe you could elaborate, or give a motivating example?

I just don’t remember encountering the problem you’re describing, and it’s unfamiliar to me. There’s something about your experience that I don’t understand, but I don’t know what it is.

viraptor 2 days ago | parent | next [-]

Moving from EE to audio to radio is enough to go through a few iterations of "people just write dB but mean completely different things". I got used to it, but that doesn't stop me from saying it's a bad idea and we should improve things for the next person.

klodolph a day ago | parent | next [-]

Audio, the only gotcha I’ve seen is that -10 is -10 dBu and +4 is +4 dBV. That one is sloppy.

But this comment doesn’t illustrate your point, and I still don’t really understand where you’re seeing this.

sanderjd a day ago | parent | prev [-]

Yeah exactly. Lots of people here can't seem to distinguish between "thing that I'm used to" and "thing that is good practice".

But these are totally different. I'm used to and thus comfortable with lots of things that are nonetheless terrible!

00N8 a day ago | parent | prev | next [-]

I often see pop sci articles saying something like '400 dB would represent a sound strong enough to tear the world apart', or 'military sonar is X dB -- strong enough to liquefy your organs at Y distance'. It's rarely clear to me which of these usages of 'dB' are directly comparable. I think the dB measurement for sonar is a different scale/unit than the one for hearing damage thresholds in air, but I couldn't figure out how to convert between the two last time I spent a few minutes trying to look it up, so in my opinion it can be fairly confusing.

sanderjd 2 days ago | parent | prev [-]

The explanation and motivating examples are in the article.

klodolph a day ago | parent [-]

The article only had bad examples in it, I was hoping for perspective from someone that made sense.

The voltage / power example doesn’t make sense. It’s always power or voltage squared, which are equivalent when the load is resistive.

sanderjd a day ago | parent [-]

The articles examples were fine. You (and lots of others here) are being obtuse.

drob518 2 days ago | parent | prev | next [-]

Then your complaint is with the dropping of units, not dB.

sanderjd 2 days ago | parent | next [-]

Yes. The point is that for some reason dB seems particularly susceptible to people dropping the units.

For instance, I've heard loudness of sounds described in decibels for my whole life, and first saw the actual units people are describing when I read this article and thread today.

drob518 2 days ago | parent [-]

That’s because you’re a casual observer. If you’re an audio engineer, recording things, designing microphones, amps, or speakers, then you’d know it. Trust me. I’m a digital electrical engineer (computer engineering, basically). I thought that dBs were weird, too. My dad worked in microwave communications systems for his career and dBs are perfectly natural for him. Ditto my daughter who is an audio engineer. Dropping units when you’re working in a particular field is quite common, as who wants to be needlessly wordy when it’s redundant and everyone in the industry understands it? IMO, this article is just the author raging about his own ignorance.

sanderjd a day ago | parent | next [-]

That's the whole point. You're failing to communicate clearly. You think it's fine because you're used to it. But it's bad. That you are used to and comfortable with something does not imply that it is not bad.

viraptor 2 days ago | parent | prev [-]

There are two paths: "it was weird but then I got used to it, you're just ignorant" or "it was weird, I got used to it, but we should improve the situation". I know which side I want to be on. Even if it takes decades like the data SI prefixes.

drob518 2 days ago | parent | next [-]

You’re discounting familiarity as being stupid. The real path is “it was weird but once I spent some time with it, it made perfect sense.”

sanderjd a day ago | parent | next [-]

No, it doesn't make perfect sense. It's a bad practice to leave off units. You just got used to it and seem to have developed pride in being in the in-crowd of people comfortable with an unclear jargon, and that has now blinded you to a bad status quo. Many such cases!

JadeNB a day ago | parent | prev [-]

> You’re discounting familiarity as being stupid. The real path is “it was weird but once I spent some time with it, it made perfect sense.”

I don't think either of your parent's paths say that:

> There are two paths: "it was weird but then I got used to it, you're just ignorant" or "it was weird, I got used to it, but we should improve the situation". I know which side I want to be on. Even if it takes decades like the data SI prefixes.

I believe that they're saying that, yes, experts get used to it, after which it makes complete sense (as would any arbitrary but consistent convention, once you got used to it), but, in any living field, there will constantly be non-experts looking to become experts. If there is a way to make the process easier for them while not introducing any lack of precision that would hamper experts, then why not?

klodolph a day ago | parent | prev [-]

What’s to improve? I think the situation works well for people who work in the fields that use dB.

sanderjd a day ago | parent [-]

The improvement would be to specify the units you're working with, as is well known best practice in all science and engineering disciplines.

viraptor 2 days ago | parent | prev [-]

Yes, that's what the whole article is about...

drob518 2 days ago | parent [-]

But it’s not. He’s raging against dB.

viraptor 2 days ago | parent [-]

Yes. He's complaining against dB with no reference, not against dB(A) for example. (Apart from the naming of some of them being silly)

davrosthedalek a day ago | parent | next [-]

But dB without reference makes sense in many many occasions. Either because the reference is implicit (not ideal, but we have many implicit assumptions in communication), or because it's genuinely a ratio. Attenuation, gain.

If you every find an "official" written document that uses dB not as attenuation/gain and is not specifying the reference (at least in a footnote), it's written either by idiots or for idiots, or both.

sanderjd a day ago | parent [-]

No it doesn't. It's always bad for the actual unit to be implicit.

davrosthedalek a day ago | parent [-]

The unit of a gain/attenuation is [1]. There is no implicit unit in that case.

klodolph a day ago | parent | prev [-]

dB(A) is a weighting. It’s not a reference and it’s not units. I think some of the confusion here comes from people not actually understanding units.

A-weighting describes how different frequencies are summed up. It’s like saying “RMS”. RMS is not units, A-weighting is not units. You can apply A weighting to voltage, digital signals, or audio. They all have different units but can all be A-weighted.

You could invent a new unit for A-weighted audio, but you would need several.

formerly_proven 2 days ago | parent | prev [-]

Can you show one of those audio equipment datasheets where it just says "<number> dB" a bunch of times and it's really unclear and confusing?

sanderjd 2 days ago | parent | prev [-]

If you were writing a research paper or engineering artifact rather than having a casual conversation, you should specify the units ("years old") for age as well.

BobaFloutist 2 days ago | parent | prev | next [-]

I mean it's always a little bizarre when the default unit used to measure something is dimensionless. Why not set a default (like STP) that's assumed to be the baseline unless otherwise specified? It would be like if Celsius had no reference point and every time you said water boils at 100 degrees Celsius people came out of the word work to smugly correct you "Only if you first say 0 degrees C is when water freezes, which you can't assume. What if 0C is actually absolute 0?"

beloch a day ago | parent | prev | next [-]

Many scientific measurements are entirely contextual. e.g. What is 0 V? Ground? Is ground across the globe always at the same potential? Nope. What's ground on a space station? Ground potential is whatever we want it to be. You don't need to define what ground potential is in, say, a computer, relative to some global standard for things to work.

How about velocity? What's 0 m/s? What does it mean to be absolutely still? All motion is relative, and being still is entirely a matter of perspective. You might be sitting still on a train, but traveling very quickly relative to a cow standing still while you blow by.

Bels are a relative measure that confuse some because they pop up in different contexts that seem unrelated. However, they are useful when dealing with quantities for which most pertinent relationships are exponential. e.g. They work for sound because humans perceive exponential increases in volume in a linear fashion. Something that is 3dB louder is twice as loud in terms of pressure levels, but we only perceive it as a little bit louder. Sound pressure levels are both relative measures and an attempt to reflect human perception . That makes them, necessarily, a bit odd.

sanderjd a day ago | parent [-]

None of these other examples are contextual in the same way.

2 days ago | parent | prev [-]
[deleted]
weinzierl 2 days ago | parent | prev | next [-]

"decibels are simply a dimensionless ratio, used as a multiplier for some known value of some known quantity."

Except they are not. 1 dB can sometimes mean a ratio of ~ 1.26 and other times it can mean a ratio of ~ 1.12.

"In every context where decibels are used, either the unit they qualify is explicitly specified, or the unit is implicity known from the context."

Maybe in university, but certainly not in the real world.

hgomersall 2 days ago | parent | next [-]

It's a power ratio. 1dB always means a power ratio of 1.26. That might mean a voltage or current ratio, say, of 1.12, but that is because the relationship between voltage ratios and power ratios is a simple square.

arghwhat 2 days ago | parent | next [-]

The problem isn't really the ratio, but the use in arbitrary contexts that require a lot of pre-existing knowledge. The reference value is sometimes a rather arbitrary value in an arbitrary unit, neither of which is communicated by the "dB" unit suffix.

The SI way to write `10 dBm` is to write `10 dB (1mW)`, clearly communicating both the power level and the reference point and unit. This ensures that you do not have to just memorize a bunch of decibell suffixes and their magical reference values.

twelvechairs 2 days ago | parent | prev | next [-]

The other side of the authors discussion is the use of 'decibels' to describe 'loudness'. The big difficulty there is that 'loudness' is a sense perception that varies between people and in different contexts. The article touches on this 'weighted to mimic human hearing...' but doesnt mention the systems to do this - DB(A) and others, none of which achieve scientific perfection.

Our senses are all like this - for the same reason we have dozens of systems to describe color. And why perfume and wine makers can never agree descriptions.

lxgr 2 days ago | parent | prev | next [-]

That’s maybe what it “is”, but not the only thing people use it for in many fields. Very often, it’s a ratio between a measured quantity and some (implied) base unit of the same quantity.

hgomersall 2 days ago | parent [-]

In which case they're misusing it, which is hardly a problem with the notation.

lxgr 2 days ago | parent [-]

As I read it, the criticism of TFA is directed at how people actually use the notation, not how it ought to be used in an ideal universe.

hgomersall 2 days ago | parent [-]

But people misuse words and notation all the time without anyone arguing they're ridiculous. I use dBs on a daily basis with plenty of other people and never have any trouble. Indeed, we'd struggle if we had to use something else.

lxgr a day ago | parent [-]

> But people misuse words and notation all the time without anyone arguing they're ridiculous.

That only indicates that you haven't found the many angry blog posts yet, not that they don't exist :)

weinzierl 2 days ago | parent | prev | next [-]

I understand that and it just reinforces my point. What 1 dB essentially means is highly dependent on a most of the time silent context.

hgomersall 2 days ago | parent [-]

No, it always means a power ratio. That sometimes can imply something else, but that's on you to work that out.

lxgr 2 days ago | parent [-]

Yes, but that, i.e. putting the burden of disambiguating some meaning from context on the receiver instead of the sender, is just bad communication.

hgomersall 2 days ago | parent [-]

What? Blaming a bad communicator for bad communication is fine. Blaming their words because they used them badly is not.

lxgr 2 days ago | parent [-]

What about blaming a common but confusing usage of some words pervasive in some fields?

klodolph 2 days ago | parent | prev [-]

Exactly. I’ve never seen it otherwise.

20k 2 days ago | parent | prev | next [-]

I have a feeling that a lot of people here haven't read the article. There's lots of "Its just a dimensionless ratio" comments

tpoacher 2 days ago | parent | prev | next [-]

This sounds more like a problem with the 'real' world then.

lambdaone a day ago | parent | prev [-]

In the "real world", techically competent people understand decibels just fine.

But this is not arcane knowledge only known by a priesthood. Since you are clearly confused about what a decibel is and how and why it is used, you can read

https://en.wikipedia.org/wiki/Decibel

and all will be revealed.

jampekka 2 days ago | parent | prev | next [-]

> For instance, in the case of loudness of noise to human ears in air, the unit can be taken to be dBA (in all but rare cases which will be specified) measured with an appropriate A-weighted sensor, relative to the standard reference power level.

This was covered in the article. But also it was discussed why things aren't this simple.

> People who assume that everyone is an idiot but themselves are rarely correct.

Indeed.

timerol 2 days ago | parent | prev | next [-]

> multiplier for some known value of some known quantity

Of course, unless it's a multiplier for an unknown value of a known quantity, like every amplifier, filter, and sensor specified in dB.

> For instance, in the case of loudness of noise to human ears in air, the unit can be taken to be dBA

Unless you're using dBB or dBC, but of course we all know exactly why you'd use dBC (more suitable for figuring out safety of high impulse, short events) or dBB (it's somewhere in between - you'll know it when you see it).

> The apparent excessive complexity is necessary, not invented to create confusion.

Wait, so writing dB instead of dBA is now necessary, not just convenient?

lxgr 2 days ago | parent | prev | next [-]

> It's a bit like hating numbers, and saying "What do you mean by 'three'; what is it - three volts, three amps, three metres?

No, it’s a bit like saying “for chocolate M&Ms, 3 obviously means 9, to compensate for the fact that they’re much smaller than the peanut ones”.

timerol 2 days ago | parent [-]

Can I get 3 M&Ms? Obviously I mean 3 serving sizes, how else would you measure M&Ms?

WhitneyLand a day ago | parent | prev | next [-]

People who assume things are not complex because they understand them are rarely correct.

The complexity absolutely is not necessary. Maybe you mean to say it’s understandable or it’s coherent if you know the rules.

Physics doesn’t require us to create ambiguity by assigning DB to mean multiple possible ratios. If it needs to be disambiguated, then they both didn’t need to be DB in the first place.

baxtr 2 days ago | parent | prev | next [-]

> People who assume that everyone is an idiot but themselves are rarely correct.

Print this, frame this, put this up on walls in schools, offices, heck even outdoor on large billboards!

anthomtb a day ago | parent [-]

And before doing any of that, get it tattooed onto your own forearm.

ok_computer a day ago | parent | prev | next [-]

I think college undergrad physics and engineering is an important time to gain exposure to a variety of concepts and measures. Then you learn the people who discovered or invented these concepts were writing by candlelight and not washing their hands and didn’t have modern mathematics or computers and didn’t want to piss off the church. Oftentimes working at the pleasure of a rich sponsor family or king.

Like you have to describe relative intensity of waves in some way and these were experimental scientists, not commerce merchants looking for absolute interchangeability like weights and measures.

Computer blog people like standards and languageisms but science isn’t determined by big tech sponsored committee. It’s the best tool put forward so far and db is a physics concept and with a reference denominator you can calculate the absolute value. It’s fine. If you dabble with physics and expect the universe to make intuitive sense then you need an education.

Read books not blogs.

skrebbel 2 days ago | parent | prev | next [-]

To be frank, your comment just reads to me as a "stockholm syndrome" type reaction to a needlessly complex unit that you're intimately familiar with.

You see the same in HN threads where people complain that eg Git or Rust are needlessly complex, there's a swath of people who are so emotionally invested in how well they understand the ins and outs of Git resp Rust that any suggestion that maybe things could be better makes them angry.

It's possible for decibels to be usable and generally fine and also for them to needlessly complex, ie for there to exist better alternatives in each place they're used.

As an example, it makes no sense to me that eg in audio software, volume sliders start at 0 dB and then go down to negative $MUCHO, until complete silence at -Infinity. And then this same unit is also used to measure how loud my coffee machine is, somehow, but then it's suddenly positive and not a relative number at all? That's just weird shit, it's like expressing the luminosity of a pixel (in HSL terms) in lumen instead of a unitless percentage.

In the audio software context, it would be much more intuitive for "no sound" to be 0, and "full volume" to be 100, a bit like percentages. The "but volume needs to be logarithmic because that's how we hear it!" argument doesn't disallow that at all. Just because a slider goes from 0 to 100 doesn't mean that a 10 must mean 10% of the power output. Decibels are ridiculous.

klodolph 2 days ago | parent | next [-]

If you want 0 = no sound, then you can’t use a logarithmic scale. You end up with sound being measured as Pascals in the micro to unit range.

“0 dB SPL” is 20 micro pascals which is roughly the threshold of hearing. A loud rock concert at 120 dB SPL is 20 pascals (no micro). The dB figures are a lot more convenient to work with.

It’s intuitive for 0 to be silent and 100 to be full, but if you work with audio you learn that dB are more convenient. Long-term convenience for experts tends to win out over short-term intuition for non-experts. This is why musicians continue to use sheet music and all of its seemingly ridiculous conventions—and likewise, decibels only seem ridiculous to people who don’t work in audio.

I don’t know what more usable alternative there would be, to decibels.

_kb 2 days ago | parent | prev | next [-]

> volume sliders start at 0 dB and then go down to negative $MUCHO, until complete silence at -Infinity. And then this same unit is also used to measure how loud my coffee machine is.

They're not the same unit, at all.

The audio software is a skeuomorphism from an analogue mixing console that is applying a change to a signal. 0 is unity gain and deviation from this describes an amplitude variation. This is important, as it means you are either discarding information by lowering the level and reducing dynamic range, or interpolating new information (/ decreasing SNR) by applying gain. This is less important today with floating point, but has strong historical reasons for existence across both analogue and digital domains.

If you look at an audio power amp, you will likely have some form of positive number as this is applying gain. Depending on the context this may have some specific meaning or it may be a screen print of a Spinal Tap logo and the numbers 1..11. These are all just UI decisions and part of doing that well is presenting coherent information for the target user group.

When you're talking about an acoustic noise source this is dB SPL which is a quantifier against a physical reference. That reference level quantifier is omitted a lot, which leads us to a lot of the angst in this post and the comments here. These are precise measurements, with very specific meaning. Their expression is often sloppy, but the units aren't to blame.

(excuse me while I got "full HN" here - I appreciate the irony in this response noting your first few sentences)

The reason people respond strongly to comments like this (or those about Git, or Rust) is because details matter. When you immerse in a domain, you learn the reason for those details. That does not mean things can't be improved, but this also does not imply those details can be removed or are wrong. A lot of the world, particularly when working outside of the bounds of a computer, depends on necessary complexity.

lxgr 2 days ago | parent [-]

> They're not the same unit, at all.

Exactly, so why label two different things using the exact same letters in a potentially ambiguous context.

jwagenet 2 days ago | parent | next [-]

How about using kg for both mass and weight? At least as an American we learn lb is actually lb_f and lb_m or slug is used for mass. The weirdness is consistent with the rest of the system. In metric Newton exists as a separate and sane measure of force…

_kb 2 days ago | parent | prev [-]

Because it’s not ambiguous.

If I pay for something in Australia and the bill comes to $50 this has meaning within that context.

I receive a bill in Zimbabwe for $50 this also has meaning within that context.

These values are not equivalent.

Ditto if I were to say it’s 30 degrees out. You may interpret that as either a good day for the beach, nice weather for ice skating, or we need to bear north-northeast depending on what context we share.

Language is messy.

skrebbel a day ago | parent [-]

This is unnecessary complexity. My rant is against that exactly. You're defending confusing shit that doesn't get any better from being confusing. If all countries had a different currency, things would be clearer too. Ask any Australian shopping for digital products on international sites. Half of the sites write $ but forget to specify whether it's "we geolocated you and guessed AUD" or "haha it's USD but we just wrote $ because we forgot that there's a world outside the US". If Switzerland would rename the CHF to Euro but not change its value to match the existing Euro, everybody would agree that that's a terrible idea. There wouldn't be edgy HN commenters explaining that well, actually, there's precedent so it's fine! No, it'd just be bad. The dB ambiguity is a mess for the same reason. The situation has no benefit and in the world of units, where most other things (eg the most of the SI) are actually relatively usable and non-ambiguous, it's a fuckup. And the power vs voltage aspect of it makes it even worse than the $ situation.

Your argument that it isn't so bad in practice doesn't change the fact that it has no benefits whatsoever.

It's just ambiguity for the sake of it, because way back when people started measuring sound stuff, nobody bothered to go "but wait is this actually handy?" and then we got stuck with whatever the first guy came up with. It's just like the whole kilobyte/kibibyte crap and the whole Wh vs mAh vs kilojoule soup. It's all downside.

amluto 2 days ago | parent | prev | next [-]

> As an example, it makes no sense to me that eg in audio software, volume sliders start at 0 dB and then go down to negative $MUCHO, until complete silence at -Infinity.

This one doesn’t bother me. Those sliders, and especially the real analog sliders they’re modeled after, don’t have an absolute scale — they are attenuators that reduce voltage. So 0dB is the same as no slider at all, -20dB reduces voltage by a factor of 10, etc.

davrosthedalek 2 days ago | parent | prev | next [-]

Ok, I bite. Please come up with a mapping of 0 to 100 to -inf dB to 0 dB attenuation.

And then put two in series. Is there a simple formula to calculate the total attenuation?

This works flawlessly with dB. Just add. And it doesn't matter how you break it: -20dB and -20 dB in series is the same as -40dB and 0dB.

nyeah 2 days ago | parent | prev | next [-]

It makes perfect sense that the sliders start at 0dB and go down to -inf. Maybe you don't understand it, but it definitely makes sense. Everyone who uses dB has also tried a % scale with 100% as 0dB, and then later made a conscious choice to figure out how dB work.

Maybe they're all in a conspiracy to make things needlessly complex. But that's not the only possibility.

viraptor 2 days ago | parent [-]

> and then later made a conscious choice to figure out how dB work.

You're just projecting your ideas here. I've not made that choice, it's just the only option in a lot of software - I'd like my % slider back.

seba_dos1 2 days ago | parent | next [-]

% slider sounds like a good idea until you actually have to use it.

formerly_proven 2 days ago | parent | prev | next [-]

Windows has 0-100 volume sliders if you like that better.

They are still some kind of faux-logarithmic*

*behavior depends on drivers/hardware.**

**for some hardware 50 in Windows will be neutral and 100 will be something like a +30 dB digital gain, that's probably in part because Windows is mapping the 0-100 range in some way to the USB audio control range, which is at most +-127 dB or something like that.***

***with some audio interfaces (the non-USB-Audio-class kind) the 0-100 actually becomes a linear factor of 0-1, making the windows controls very useless indeed, as 70% of the slider range does approximately nothing.

nyeah 2 days ago | parent | prev [-]

Right. Decibels are my idea.

viraptor 2 days ago | parent [-]

Projecting in that context means you claimed what other people think/do, because it's what you think/do. It's about describing the conscious choices of others (where my experience disagrees for example) not about decibels specifically.

nyeah 2 days ago | parent [-]

Agreed, you are using the word "projecting" fine. But you're ignoring the actual behavior of people using dB in the real world.

regularjack 2 days ago | parent | prev | next [-]

There is no such thing as full volume, and there is not such thing as zero volume.

nyeah 2 days ago | parent | next [-]

To be fair, since we can go to +3dB out of 0dB, we could also go to 200% on a 100% scale. In the era of software it would not be completely insane to allow users to choose how their faders are marked. (It would be insane to use 3/4 of a slider's travel for the range 100% to 400%. So the locations of the markings on usable sliders would remain mysterious to %-only folks.)

Ultimately people who use this a lot would choose to become familiar with dB, as they always have. But there's no rush.

jameshart a day ago | parent | prev | next [-]

‘There is no such thing as zero volume’ - can you expand on that?

Surely constant unchanging air pressure has zero volume?

Volume is the range of variation in air pressure, right? That can surely go down to zero.

It can also only meaningfully go up to about double the absolute mean air pressure, before what you are talking about becomes shockwaves of overpressure.

tadfisher a day ago | parent [-]

Air pressure is a statistical measure; given a room with zero net variation in pressure, I can always find a volume in that room with positive pressure, down to measuring Brownian motion of atoms. Now try to design a measurement apparatus that can only sample a small volume to measure variations in pressure, and you can understand why (sound) volume can never go to zero.

jameshart a day ago | parent [-]

Over meaningful statistical sampling areas, like an eardrum, say, pressure can be effectively constant, surely?

Volume can be a statistical property, like temperature.

crazygringo a day ago | parent | prev | next [-]

I don't know what you're talking about. Both of those exist.

Zero volume is when a speaker's diaphragm is still. On an 8-bit PCM audio file, it corresponds to a value of zero.

In the context of a signal, full volume corresponds to the 127 value in an 8-but PCM audio file (or arguably -128). In the context of a speaker, those values should push the diaphragm no further than how far it can travel linearly without distortion. Obviously the user may want to turn down the volume from this full volume.

I hope you understand that even when using an audio editor that displays values in dB, the underlying values are integers (or floats) that absolutely have zero and "full volume" meanings, and conventionally map respectively to -∞ dB and 0 dB.

DonHopkins 2 days ago | parent | prev [-]

There such a thing as going to 11.

https://www.youtube.com/watch?v=uMSV4OteqBE

CamperBob2 2 days ago | parent | prev [-]

dB is always relative, even when it appears to be an absolute unit. The 0 dB marking at the top of the volume slider on pro audio gear (more likely +3 or +6 or something similar to leave some headroom) means "0 dB relative to the maximum rated power level." In pro gear this will be an absolute industry standard of some sort, likely one where the load impedance is also defined. 1 milliwatt into 600 ohms or something like that. The distinction between voltage and power is always going to confuse people, but that's not the dB's fault.

A major reason decibels are used is to make it easy to assess the overall gain or loss of an entire chain of processing stages: you simply add the numbers. The equipment's output can only go down from 0 dB, so the rest of the scale is negative.

As for sound pressure levels in dB, those are given relative to a 0-dB point that corresponded originally to the faintest sound people were generally considered capable of perceiving. These days "0 dB" refers to a specific amount of acoustic power, which I don't know off the top of my head, and that might or might not be near the threshold of perception for a given listener. But the reasoning still applies: amplification or attenuation of power levels is a simple matter of addition when expressed in dB. Arbitrarily defining a system's reference level to be 100 dB instead of 0 dB would be of no use to anyone.

drob518 2 days ago | parent [-]

Exactly. dB is just a way to apply a logarithmic scale on a quantity that would have orders of magnitude range if working with a linear scale. It allows an engineer to quickly add up all the amplification and attenuation through a series of amps and filters without having to do a lot of uglier math. It’s not really a physical unit. It’s a marker that says that we’re working in the domain of logarithmic quantities of some other units.

2 days ago | parent | prev | next [-]
[deleted]
IvyMike a day ago | parent | prev | next [-]

> People who assume that everyone is an idiot but themselves are rarely correct.

This is an off-by-one error.

xeonmc 2 days ago | parent | prev | next [-]

Interviewer: "So what's the fastest you've gone on your bike?"

Kid: "Thirty."

Interviewer" "Thirty what?"

Kid: "Umm..."

Kid: "Speed."

[0] https://www.youtube.com/watch?v=OYt1kqDNlMY

UncleMeat 2 days ago | parent | next [-]

"I was doing 70 down the highway" is absolutely the sort of thing people say. From context (this conversation takes place in the US, most highways have a speed limit somewhere around 60-70mph) people understand that you are talking about miles per hour.

viraptor 2 days ago | parent [-]

And yet, on the internet without the extra context, I can't tell if you're going slowly in km/h or the usual in mph. With dB that depends on whether you're taking to a person familiar with the context-specific conventions or not.

dotancohen 2 days ago | parent | prev | next [-]

KSP measures funds in some unitless value, it drives me nuts. Everything else is almost (but not quite) perfect.

viraptor 2 days ago | parent | next [-]

Just pretend it's a Jane Austen novel and you're earning 500. Pounds? Pieces of gold? Sheep? Who knows really ;)

BlueTemplar a day ago | parent | prev [-]

https://en.wikipedia.org/wiki/Currency_sign_(generic)

JoeDaDude 2 days ago | parent | prev [-]

Maybe you can say "6 dbm/s"

mystified5016 a day ago | parent | prev | next [-]

Exactly, the log(x) function is stupid and useless! It's the log of what? 6? Pi? Little-g? Same for logn(x). Who the hell is n?!

DonHopkins 2 days ago | parent | prev | next [-]

At least the Mel-frequency cepstrum is honest about being a perceptual scale anchored to human hearing, rather than posing as a universally-applicable physical unit.

https://en.wikipedia.org/wiki/Mel-frequency_cepstrum

>Mel-frequency cepstral coefficients (MFCCs) are coefficients that collectively make up an MFC. They are derived from a type of cepstral representation of the audio clip (a nonlinear "spectrum-of-a-spectrum"). The difference between the cepstrum and the mel-frequency cepstrum is that in the MFC, the frequency bands are equally spaced on the mel scale, which approximates the human auditory system's response more closely than the linearly-spaced frequency bands used in the normal spectrum. This frequency warping can allow for better representation of sound, for example, in audio compression that might potentially reduce the transmission bandwidth and the storage requirements of audio signals.

https://en.wikipedia.org/wiki/Psychoacoustics

>Psychoacoustics is the branch of psychophysics involving the scientific study of the perception of sound by the human auditory system. It is the branch of science studying the psychological responses associated with sound including noise, speech, and music. Psychoacoustics is an interdisciplinary field including psychology, acoustics, electronic engineering, physics, biology, physiology, and computer science.

DonHopkins 2 days ago | parent | prev | next [-]

Some people just hate certain numbers.

Many buildings don't have a 13th floor because superstitious people think it's unlucky.

Some people lose their shit at 8647 because paranoid delusional people think it's out to kill them.

a day ago | parent | prev [-]
[deleted]