How to Mix Audio: Automation for Beginners

Main ideas / lessons

• Automation is fundamental to mixing: It lets you “perform the moves” of a mix over time—changing levels and plugin parameters as playback progresses.
• Everything you want to change can be automated: not just faders/loudness, but EQ, compression, reverb, sound design tools, and dialogue processing, etc.
• Understanding automation modes is key: different DAWs share similar core automation concepts, but the exact behavior depends on the selected mode.
• The speaker’s practical workflow: they mainly rely on Touch (and Trim) automation, plus a Pro Tools feature (Preview) to adjust before committing.

Automation modes covered (with behavior)

1) Read (default in many DAWs)

• What it does: Plays back using existing automation data.
• Writes anything? No.
• User input impact: Generally ignores control changes unless no automation exists already.
• Best for: Normal playback where you don’t intend to write/overwrite automation.

2) Write (opposite of Read)

• What it does: Continuously records automation.
• Writes anything? Yes—every enabled track/plugin parameter/control the user manipulates during playback.
• Why it can be destructive: Adjusting EQ bands or moving faders will hard-write those changes into the session.
• Best for: Intentional automation recording when you truly want to write all active parameters.

3) Touch

• Core behavior:
  • While playback is running, any parameter you move writes automation.
  • Only the touched parameters change; untouched parameters remain unchanged.
• When you release the control:
  • The parameter returns to its previous automated value immediately after you stop touching it.
• Best for: Fine-tuning between existing mix moves without permanently disrupting the automation.

4) Latch

• Core behavior:
  • Starts playback by following existing automation normally.
• When you begin moving a parameter:
  • Automation begins writing.
• When you stop touching the control:
  • It keeps writing and stays at the value where you stopped, rather than returning.
• Pros: Useful when you want changes to “stick” after you stop adjusting.
• Risks: If enabled accidentally, it may overwrite material you wanted to keep.

5) Touch Latch (Pro Tools-specific)

• Combination concept:
  • The fader/level automation behaves like Touch (returns after you stop adjusting).
  • Other plugin/process parameters behave like Latch (stay written after you stop).
• Speaker’s usage: Rarely used, but acknowledged as useful in certain situations.

6) Trim

• What it does: Acts as a secondary layer on top of existing automation.
• Purpose:
  • Modify an already-good mix move by small adjustments (e.g., +0.5 dB, +2 dB, or pulling down slightly).
• How it functions:
  • Works across any automatable parameter for plugins/tracks/layers—not rewriting from scratch, but offsetting/adjusting what already exists.
• Best for: Fixing small problematic sections (a dip or jump) while leaving the rest of the automation performance intact.

Workflow / method the speaker uses (step-style)

• Primary approach:
  • Mix using Touch + Trim automation “pretty much all the time.”
• Use Pro Tools “Preview” to control when automation gets committed:
  1. Put Pro Tools into Preview mode.
  2. For each dialogue/sound effect (when mixing elements individually):
     • Adjust parameters/processing while hearing results.
     • Do fine-tuning before committing.
  3. Then commit automation only to the moments where it’s needed.
• Benefits claimed:
  • Less CPU/processing load since plugins/changes only affect the specific sections where they’re required.
  • More organized session because automation is tailored to specific audio pieces instead of changing entire tracks/plugins broadly.

Speakers / sources featured

• Speaker: Alex Nickerbacher (also referenced via the website alexnickerbacher.com and social handle @axk).
• Source/DAW mentioned: Avid Pro Tools (used as the example DAW where modes like “touch latch” and “preview” are discussed).