Automation

Automation is the DAW's record of "this parameter was here, then it moved here, then it ended up there." Volume rides on a vocal. Filter sweeps on a synth. Send levels rising into a chorus.

A static mix locks every fader and knob in one position. An automated mix moves them deliberately, second by second, to keep the listener engaged across three minutes.

What to Automate

Almost anything can be automated. Some moves come up so often they're worth defaulting to:

Volume. The single most common automation. Vocal lines often have 30+ small volume tweaks across a song to keep every word audible without compressing the life out of the performance.

Mute / unmute. Cutting an instrument out for a single bar before a chorus, or muting a hi-hat for a half-bar lead-in.

Send level. Reverb send rising into a chorus, then pulling back. Delay throws on the last word of a line.

Filter cutoff. A low-pass slowly opening across a build-up. The most-used automation in EDM after volume.

Pan. A guitar moving from left to centre across an intro. Subtle pan automation adds movement that feels human rather than fixed.

EQ bypass / band gain. Different EQ settings for different sections (verse vs chorus).

Plugin parameters. Reverb size, delay feedback, distortion drive — anything that can dial in becomes more interesting if it changes deliberately during the song.

Automation Modes

Most DAWs offer:

• Read — plays back existing automation, ignores new movements.
• Write — records every fader movement; overwrites existing automation.
• Touch / Latch — only writes when you actually move a control; reverts to existing data when you let go (Touch) or stays at the last value (Latch).
• Trim — adds a relative offset on top of existing automation, useful for nudging an entire pass without redrawing everything.

For most mixing work, Touch is the safest default. You can grab any control, move it, and let go without disturbing automation you've already written.

Automation vs Modulation

Two related concepts that are often confused:

• Automation is recorded by you. Plays the same every time.
• Modulation is generated by an LFO, envelope, or other source. Repeats based on its own rate, not the song timeline.

Use automation for moves tied to musical sections. Use modulation for ongoing patterns (a wobble bass LFO, a tempo-synced filter sweep). The two can also coexist — automate the rate of an LFO, for example, so the modulation gets faster across a build.

Automation Lanes

Most DAWs let you display automation on a separate visual lane below the audio waveform. Useful for seeing curves, drawing precise breakpoints, and editing without obscuring the audio.

In Logic, hitting A toggles automation view. In Ableton, A does the same. In Pro Tools, the show/hide menu controls which automation lanes are visible. Knowing your DAW's shortcut here saves hours.

When Automation Goes Wrong

The flat-mix problem. No automation = no movement. The mix sits at one level for three minutes; the listener loses interest.

The over-rode problem. Every fader twitches every bar. Movement for its own sake. The mix sounds nervous.

The forgotten-pass problem. Automation written in Touch mode that you forgot is still there, fighting newer moves. Always check existing automation before writing new passes.

The bypass-without-removing problem. Disabling automation read mode without deleting the data leaves landmines for future you. Either commit and remove or fully disable.

Practical Workflow

1. Get a static balance first. Set every fader at a sensible level before automating anything.
2. Write big moves before small ones. Fader rides on the full chorus before adjusting individual word volumes.
3. Use track grouping. If you automate the lead vocal volume, the doubles often need the same shape. Group them and write one pass.
4. Print when stable. Render automated tracks to audio when you're confident. Saves CPU and prevents accidental disruption of complex passes.

Common Mistakes

Automating instead of mixing. Automation polishes; it doesn't replace getting the static mix right. A vocal that needs constant volume rides probably needs better compression instead.

Forgetting to enable read mode after writing. You wrote a beautiful pass, then forgot to switch back. Now the mix plays static.

Skipping the bypass test. Listen with all automation disabled to remind yourself what the static balance sounds like. If "static" sounds nearly as good as "automated," you're working in the wrong direction.

Further Reading

• Sound on Sound — Mixing With Automation