Skip to main content
!
!QAZ2wsx#EDC
Participant
January 4, 2019
Question

Dynamics Processing - Level Detector & Gain Processor: Why 2 Attacks & 2 Releases?

  • January 4, 2019
  • 1 reply
  • 1237 views

Context - I have been an audio engineer since the mid-90s.  I learned on Analog gear.  I got into DAW recording in 1997.  I have extensive knowledge of how compressors and noise gates and expanders work, so I am not looking for an explanation of compressors.  However, I am having a difficult time understanding the user interface of the Dynamics Processing plug-in.

I feel like I grasp the main graph on the "Dynamics Tab," but I'm having a hard time understanding the Settings tab.

Under the settings tab you have the Level Detector section and below it, the Gain Processor section.  Level Detector has an Input Gain slider (this makes sense).  The Gain Processor has an Output Gain slider (this makes sense) as well, and both have attack and release settings.

MAIN QUESTION: I understand what attack and release settings are for on any other compressor/gate/expander, but why are there two sets of these settings under this tab?  I notice there is no "hold" setting.  Can someone help me wrap my old brain around this weird looking compressor?

I've got to admit, I'm not a big fan of this plug-in because I feel it over-complicates the traditional and fairly sublime interface of regular compressors, but I've got an open mind.  I just want to understand how it works because right now, I'm having a hard time getting it to do what I want.

I know the new version of Audition has new processors, but that will not help me.  My job takes a couple of years to adopt new updates sadly.  I want to understand this plug-in specifically.

This topic has been closed for replies.

1 reply

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community Expert
Community Expert
January 4, 2019

Okay - true confessions time; we've always had some difficulty with this. It's a hangover plugin from CEP (Audition's predecessor from Syntrillium) and back then we got confused by it, even with a bit of help from the guy who designed it! What I can tell you though is how it's supposed to work, why it doesn't appear to have a threshold control (it doesn't need one - it's graphical), and perhaps explain why this makes it so confusing:

On the Settings tab, you have a Level Detector, and a Gain Processor. The Level Detector is the part of the plugin that analyses the incoming signal, and lets you boost it if it's weak. This is a Bad Idea - you are much better off leaving this at 0dB and normalizing your signal before applying it - you'll have a much better idea of where you are then. The Attack and Release times here only relate to how your incoming signal is analysed. The Gain Processor lets you determine what the attack and release characteristics of the processed signal will be, and its output gain control effectively controls the amount of 'influence' the driving signal has on the output. Yes, all these attack and release controls appear to conflict with each other, and the output level tab is far from intuitive. As far as the other controls on that tab are concerned, the lookahead time should be obvious (helps you catch transients better) and the Band Limiting and Noise Gating likewise.

To get some sort of idea of how much these Attack/Release settings don't really matter so much, leave the tab open and flick through the presets - and you'll notice that nothing really changes that dramatically unless it's for something excessive. Basically, unless you have good reason to alter them, leave the settings pretty much where they end up on average - attack times low, release times around 2-300ms.

What will change though between the presets is the graphical display, and that's how you set the basic system up. What's really clever about it is that you aren't simply limited to a single threshold - you can set up multiple break points and have all sorts of curves, depending entirely on what you want to achieve. Within the limitations of it being a single-channel processor, pretty much anything is on the cards if you can set it up in six segments - which is why it's still here, and still popular. Even more so now that it has a gain reduction meter!

You will notice that you can also spline the curves, and that the amounts of compression and the appropriate threshold levels are displayed for each segment. You can also set the makeup gain from this panel. Once you've got something you like, save it as a preset, or you may never find it again!

Bottom line - perseverance pays off with this thing!

    !
    !QAZ2wsx#EDCAuthor
    Participant
    January 4, 2019

    DUUUUDE!  First, thanks so much for such a detailed explanation.  I have been trying to find and answer to this for a long time.  I gave up on the thing the first few times I tried it a couple years ago mainly because I could not understand what the point of the complicated interface was for what was in the end, a somewhat sonically lackluster - tho usable - compressor.  But your explanation makes it as crystal clear as I think it can be from a technical standpoint.

    Playing with the actual controls on different types of audio material, it's hard to understand why two sets of controls are useful (instead of just confusing) for the normal sorts of things people use dynamics for.  In other words, why not just hide one set (probably the Level Detector) of controls and just have that setting as something usable and constant built into the code, and just leave the second set for tweaking?  Why allow the user this extra control?  I can tell they interact with each other in some way.  Once I start dialing in some extreme settings on both, it becomes obvious both are having an audible effect on the audio.  I'd love to pick the designer's brain about this.  Can you think of a practical situation where this could be helpful?  I will definitely be playing around with it tomorrow.

    For work though, my instinct is just to just set and then ignore the attack and release controls to something standard-ish (0ms attack, 100ms release) on the Level Detector and just tweak the Gain Processorwhich, like you said don't really matter a ton if they're being used within practical limits and not trying to do something extreme for compression.  They matter more for noise gates in my experience.  The effect of the gating can have much more obvious results (sometimes very negative) when set poorly, especially for human voices with all of the lingering word fall-offs like on S's and such.

    I have more respect for this plugin now, although I still probably will never use it because I have some better sounding ones anyway, but a guy I work with who is new to compression likes it and I also like the graphical representation of what's happening.  I just wanted to make sure I wasn't too quick to write it off due to my ignorance about its design.

    Thanks again for you answer.  It was extremely helpful. =)

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices