Compression Myths!

Official support for: meldaproduction.com
RELATED
PRODUCTS

Post

Myth #1: Attack is the time it takes for a compressor to begin compressing once a signal crosses over the threshold

This may be my favorite audio myth of all time, because I think it’s the most pervasive. People who know a lot of things; people who’ve written books on the subject of recording and processing audio, have perpetuated this myth by writing about it, repeating it and passing it along as established fact so that you can read it passed off as fact in countless blogs and forums.
The only problem is that it’s completely, utterly incorrect.
in the pursuit of truth, justice, and all that is good in the world, I give you the correct definition of attack
And so, in the pursuit of truth, justice, and all that is good in the world, I give you the correct definition of attack:

Attack is the length of time it takes a compressor to apply roughly two-thirds of the targeted amount of gain reduction.
I say ‘roughly two-thirds’ because there is no agreed-upon, industry-accepted standard for what this spec actually is. Yes, you read that right: no two compressor designers will agree on exactly how to define, and therefore measure, attack. My definition above is within the ballpark of most thinking, so I’m running with it.
To understand this definition of attack better, you need to get some basics of compression established first. Let’s say your compressor is set with a threshold of -10dB and a ratio of 3:1. If you feed this compressor a signal at -11dB, nothing happens because the signal is lower than the -10dB threshold.
But if that signal jumps to -1dB things get interesting. Most notably, the instant the signal reaches -10dB the compressor begins attacking it. There is no delay whatsoever in this response, which belies the myth that attack is the time it takes a compressor to respond once a signal crosses threshold.



With a -1dB signal and a -10dB threshold, the signal is 9dB over threshold.  Our 3:1 ratio means that for every 3dB coming in over threshold, the comp wants to allow 1dB out the backside. Since our example has a signal 9dB over threshold, our hypothetical 3:1 comp wants to compress those incoming 9dB into 3dB at the output, which would require 6dB of gain reduction.
Given that attack is the time it takes a compressor to apply roughly 2/3 of the targeted gain reduction, the attack in this case indicates how fast the comp will apply the first 4dB of the target 6dB of reduction.
If you don’t follow the math of this illustration, don’t worry. For now it’s enough to know that the compressor starts applying gain reduction as soon as the signal crosses the threshold. Which means that attack is not a delay before action, nor is it even a measurement of time per se; instead, it is a rate, a measurement of the speed at which the process of gain reduction is occurring.




Read the whole article here:
https://www.attackmagazine.com/features ... mpression/
Last edited by jmg8 on Sat Nov 12, 2016 2:58 pm, edited 1 time in total.
Jason @ Melda Production

Post

It would be great to hear peoples opinion about this article (especially Vojtěch)
I'm sure I completely agree with all of it. It definitely challenged some of my existing believes of compression.
Jason @ Melda Production

Post

Thanks for sharing. Quite interesting. Also funny, that the hoster is "attackmagazine.com", hehe. :D Also thanks for the summary and explanation. In the end I mainly use my ears combined with the great Melda graphs, while using a compressor. But it's also nice to understand things technically better! :)
System: Win 10 64 bit / i9 9900K (8x 3.6 GHz) / 16 GB DDR4-3200 RAM / 1TB M.2 SSD + 2x 500 GB SSD / RME Babyface / Reaper

Tagirijus.de

Post

Hmm, I need to think about that.

To be impartial, the whole text should be in quotes, and credited to "Kush Audio guru Gregory Scott " - I thought that it was your own view at first.

Maybe this would be better in Effects or DSP and Plug-in Development; to get the views of other developers too.
DarkStar, ... Interesting, if true
Inspired by ...

Post

DarkStar wrote:Hmm, I need to think about that.

To be impartial, the whole text should be in quotes, and credited to "Kush Audio guru Gregory Scott " - I thought that it was your own view at first.

Maybe this would be better in Effects or DSP and Plug-in Development; to get the views of other developers too.
OK, I have edited now. To be clear I did not write any of this. I just found it interesting to share and find out if anyone agrees or disagrees with any of it.
Jason @ Melda Production

Post

...for me it's not so much about "agree/disagree," but more about finding myself as technician/"engineer" working in an environment of creators/"artists"...and I end up using a lot of "near miss metaphors" to get everyone on the same page :roll: ...try explaining to your mom the use of differential calculus concerning thermal gas flow temperature exchange to her while she's cooking dinner :dog: ...and you all know what I mean :lol: .../s~
mba m2 15" | 16gig.ram | 1tb ssd | macOS 26.1 Tahoe
logic 11.2.2  | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t

Post

I think there's no official rule about those "two/thirds"; we just have to get the main concept and use our ears - imo.

I believe you'll hardly find two compressors in which attack and release are implemented the same way, just because, as a matter of fact, there's no scientific standard rule on what they should do exactly to an audio signal.

That's it all for me...

- Mario

Post

Technical but very interesting read on compression/dynamics:

(web)
http://www.rane.com/note155.html

(pdf)
http://www.rane.com/pdf/ranenotes/Dynam ... essors.pdf
Last edited by mvillemaire on Sat Nov 12, 2016 5:13 pm, edited 1 time in total.

Post

Not on topic but about equalization:

(web)
http://www.rane.com/note115.html

(pdf)
http://www.rane.com/pdf/ranenotes/Expos ... hology.pdf

Someone can post it to the relevant topic/thread.

Post

So he basically pulled that 2/3s out of his ass and didn't even try to explain why it was in his ass in the first place.

Written like a true besser-wisser, bending myths into something they really aren't, not presenting any facts to back shit up... I call BS on this fellows mythbusting efforts.

Post

.jon wrote:So he basically pulled that 2/3s out of his ass and didn't even try to explain why it was in his ass in the first place.
The reason is probably a lengthy explanation of electronics that no one cares about on a user level.

Post

pone wrote:
.jon wrote:So he basically pulled that 2/3s out of his ass and didn't even try to explain why it was in his ass in the first place.
The reason is probably a lengthy explanation of electronics that no one cares about on a user level.
Unfortunately this guy lacks the credibility to present such claims without solid proof, and I won't be bothered to start testing.

Post

...im like totally board, dude :D ...so what does it sound like? that's the real/actual question :lol: ...that's why i came here :dog: ...I had enough of the maths in schoo :dog: :dog: :dog: l...im here for the chicks and the vibes :tu:...please, give me a break :D ..../s~
mba m2 15" | 16gig.ram | 1tb ssd | macOS 26.1 Tahoe
logic 11.2.2  | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t

Post

...I'm also like totally buildingmyselfanewlongboard dude :tu: It sounds great, with or without maths. I got no idea what you could possibly mean, but GL with the chicks mate :phones:

Post

A compressor is an envelope follower with side effects. Ideally, if you tell it to reduce 3 db within 11 ms, it should do exactly that. If it doesn't, these are the side effects - 'analog' imperfection due to material, implementation, etc. The 2/3rds part is bullshit. This guy is bullshit. I'm sick of 'audio gurus' building their reputation by selling fairy dust to the gullible. He gets his plugins coded for him in 3-rd world sweatshops, FFS!

Post Reply

Return to “MeldaProduction”