lesson
Updated 6 days ago · 1 view
Imagine spending an hour perfecting subtle vocal fader rides, pressing play to listen back, wiggling one knob, and watching your entire automation track get flattened instantly.
In any digital audio workstation (DAW), automation is the recorded movement of parameters—such as volume faders, pan pots, or plugin parameters—plotted across the project timeline.
To prevent accidental overwrites and capture expressive performances, DAWs use dedicated operational modes that dictate how incoming control data interacts with existing curves.
How does each automation mode behave when your hand touches, moves, and releases a fader?
The Four Automation Modes
DAWs organize automation into four primary operational states: Read, Write, Touch, and Latch.
Each mode responds differently to user input during playback, balancing safety against destructive recording.
📊Interactive diagram
Why is Write mode considered high-risk, and why is Read mode your mix's essential safety switch?
Read and Write Modes
Read mode is the default playback state that plays back existing automation curves while ignoring any hardware or software fader movements made during playback.
Write mode is purely destructive: it begins overwriting parameter data the millisecond you hit play, erasing all prior curves across the entire pass whether you touch the fader or not.
In the mid-1970s, console designers like Allison Research introduced motorized VCA faders to automate analog mixing consoles, but digital DAWs revolutionized this by introducing non-destructive punch-in modes.