Reply to thread

Message: [QUOTE="Queen, post: 90480, member: 27"] FRCTL Audio's AURA shows the exact dB drop its clarity control applies to the tail while you play, and that number is the first thing worth reading. Most people set it once, hear the vocal jump forward, and never touch the timing controls sitting right next to it. That is where the actual work is. Depth is blunt. Timing is what makes the whole thing sound like nothing is happening at all. Get the depth right with the wrong attack and you will still hear the tail smear across the front of every line. Attack and release do different jobs here, and neither has a default that survives a whole record. A rap verse at 84 BPM and a ballad at 68 need different behavior from the same plugin, even with identical depth. [HEADING=2]Attack decides whether your consonants survive[/HEADING] Attack sets how fast the tail gets out of the way once the source arrives. Fast means the drop is in place before the first syllable is fully out. Slow means the front of the word fights a tail still sitting at full level. For a lead vocal, start fast. Consonants carry most of the meaning in a line, and they are the first thing a long tail buries, so you want the tail already down by the time the T or the S lands. Slower attack still has a use. On a snare or a plucked guitar, letting the first few milliseconds through before the duck engages keeps the transient sounding like itself and stops the reverb from pumping in a way anyone notices. [HEADING=2]Release time between phrases is where mixes fall apart[/HEADING] Release controls [B]how fast the tail comes back once you stop singing[/B], and it is the setting people get wrong most often. Too fast and the room swells inside every gap, which reads as an effect switching on and off. Too slow and the reverb never really returns, so you are paying for a room nobody hears. Tie it to the song rather than to a number you liked last week. At 120 BPM, an eighth note runs 250 milliseconds and a sixteenth runs 125, and a release somewhere in that window tends to feel like part of the arrangement instead of an accident. Then listen to the gaps on purpose. Solo nothing. Play the full mix and pay attention only to the quarter second after each phrase ends, because that is the only stretch where the reverb is doing anything you can actually judge. Busy sections change the math. AURA has an absorb control that shortens decay when a passage gets dense and a swell control that lengthens it in the gaps, so the timing you dial on a sparse verse will not behave the same way once the chorus stacks up. [HEADING=2]The low end needs its own timing[/HEADING] AURA has a duck lows control that pulls the bottom of the tail down harder than the top, and in the paid version it runs on its own attack and release. That separation matters more than it sounds. Low frequencies ring longer and mask more. A tail perfectly timed at 3 kHz can still be sitting on top of the vocal at 200 Hz, and pushing the main depth further only thins the room out everywhere else to fix a problem living in one octave. Two other controls change what your timing has to cope with. Tune clears the tail between the notes you are actually playing, and drain sets how aggressively old notes get pushed out of the tail, so both cut down the buildup the duck is fighting before it ever starts fighting. You get less of this on the free tier. Duck lows, predelay, and the gate all sit behind the paid version, which is worth knowing before you judge the whole approach on [B][URL='https://goldmidi.com/community/threads/frctl-audio-built-aura-reverb-to-keep-vocals-clear.75877/']the four knobs in AURA Lite[/URL][/B]. Watch the gain reduction readout across a full verse rather than a single line. If the duck moves hard on the loud phrases and barely at all on the quiet ones, your timing is tuned to the singer's peaks, and it will come apart the moment they pull back and sing something soft. [/QUOTE]

Name