You spend forty minutes riding dialogue against a scene. Every move is a judgement call about where the ear should sit, and none of it could have been guessed by a machine. Then a new cut arrives, three seconds come out of the middle of the reel, and the question is no longer how you wrote the automation but whether any of it still lines up.
Most guides to Pro Tools automation stop at the first half of that. They teach the modes, which is the part you learn once, and skip the part that costs hours every week on a project with moving picture.
What an Automation Mode Actually Controls
The modes do not decide what your automation says. They decide when Pro Tools is allowed to write it, and what happens at the moment you let go of a control.
That distinction is the whole thing. Every mistake with automation is a mismatch between what you intended to write and the window in which Pro Tools was recording, so the mode is less a setting than a statement about how much of the timeline you are prepared to overwrite on this pass.
Modes are set per track, from the automation mode selector in the Mix or Edit window, and the parameters each mode is allowed to touch are enabled separately in Window > Automation. A track in Write mode with every parameter enabled behaves very differently from one with only volume enabled, which is the source of a large share of accidental overwrites.
| Mode | What it writes | Reach for it when |
|---|---|---|
| Off | Nothing. Existing automation is ignored on playback as well as on write. | You want to audition a static balance without the written moves interfering |
| Read | Nothing. Plays back what is already written and ignores the fader. | The pass is finished and you want it protected from accidental moves |
| Write | Every enabled parameter, from the moment the transport rolls, whether or not you touch anything. | You are laying down a first pass and there is nothing underneath worth keeping |
| Touch | Only while you are holding the control. On release it stops and returns to the underlying pass. | You are fixing individual moments inside automation you otherwise want intact |
| Latch | From first touch until the transport stops. Release does not end the write, it holds the last value. | You are automating switches and controls with no natural return position |
| Touch/Latch | The fader behaves as Touch, every other enabled parameter behaves as Latch. | You want fader rides to fall back but plug-in moves to hold |
| Trim | A relative offset applied over the existing pass rather than a replacement for it. See below. | The shape of your moves is right and only the overall level is wrong |
The failure that sends people looking for this article is nearly always Write mode. It starts overwriting the instant the transport rolls, without waiting for you to touch a control, so a pass that was meant to fix one line erases a scene's worth of work behind it. If you are unsure which mode a track is in, that is itself the argument for Read: it is the only mode that makes the session safe to play.
Trim: The Mode Most Guides Skip
Trim is the one worth understanding properly, and it is routinely left out. Production Expert's automation guide runs to roughly 2,200 words without covering it in the body.
The others replace. Trim offsets. Rather than writing a new absolute value over what is there, Trim applies a relative change across the existing automation, so the moves you already made keep their shape and the whole contour slides up or down together. Sound on Sound describes the result as adjusting the overall level of a track without disturbing the basic shape of the moves you already made.
That is the exact situation nobody has a good manual answer for. You have ridden a dialogue track through a scene, every move is right relative to every other move, and then the scene needs to sit two decibels lower against a new music cue. Rewriting it in Touch means reproducing forty small judgements you already made correctly. Trim means one pass that moves all of them together.
The corollary is worth stating plainly: if you find yourself about to redo a pass because the level is wrong rather than because the moves are wrong, you want Trim.
Where Automation Passes Get Destroyed
Here is the part the mode tutorials do not reach, and it is where the hours go on any project where picture is still moving.
Automation is written against timeline positions. It is not attached to the clip underneath it in the way engineers intuitively assume, which means anything that changes where events sit on the timeline puts your automation and your audio out of register with each other. A new cut that removes three seconds from the middle of a reel shifts every subsequent event, and the automation you wrote against the old positions stays exactly where it was.
The situations that cause it are ordinary:
- Picture changes after you have started mixing. The most common case, and the reason reconform exists as a discipline rather than a task. The mechanics of handling it are covered in our guide to conforming audio after picture lock.
- A fresh AAF arrives for a scene you have already worked. Importing it brings the editor's structure back in alongside work you have done since.
- The session gets rebuilt to a template. Reorganising tracks and routing after automation exists risks separating passes from the signal path they were written for.
- Automation parameters were enabled that you did not intend to write. Less dramatic and more frequent: a plug-in bypass or send level captured during a volume pass, discovered three days later.
None of these are exotic and none of them are a mistake by the person doing them. They are the normal shape of a project where the cut is not final, which is most projects. What separates a room that absorbs a picture change in an afternoon from one that loses two days is almost entirely whether the session was built so that a rebuild is survivable, and that is decided at prep time, before any automation exists.
Where AI Takes Over, and Where It Should Not
The honest boundary runs straight through the middle of this topic.
The automation itself is not a candidate for automation. A dialogue ride is a sequence of judgements about intelligibility, emotional weight, and how a line sits against a music cue that has its own arc. No current tool has an opinion worth having about any of that, and a tool that claimed to would be a reason for suspicion rather than interest.
What surrounds the automation is a different matter. Getting incoming audio classified, named, routed to the correct buses, and aligned to the facility template is mechanical work with a correct answer, and it is where the two to three hours before a mix actually go. fPost runs that stage on an incoming AAF: its AI-R content detection classifies audio as dialogue, music, or SFX, places clips against the template, and keeps timecode, automation, and import session data intact through the process, so the session you start automating is already the session you would have built by hand.
On the music side the same split applies to mix prep and stem delivery rather than to picture: fMusic classifies incoming stems by instrument and handles the export end, which is the administrative bracket around the mixing itself rather than any part of the mixing.
The wider question of what is genuinely AI inside Pro Tools today, as opposed to what is marketed that way, is mapped in detail in our article on whether there is AI in Pro Tools. The short version is that the native surface is smaller than most engineers assume, and nearly everything useful sits in third-party plugins and companion applications.
Protecting a Pass Before You Need To
Three habits cost nothing at the time and repay themselves on the first picture change.
Put finished tracks into Read as soon as a pass is done. It is the cheapest insurance in the application, and it removes the entire category of accidents where a stray fader touch during a playback overwrites completed work.
Be deliberate about which parameters are write-enabled in Window > Automation rather than leaving everything armed. Most accidental overwrites are not the wrong mode, they are the right mode applied to more parameters than intended.
Prep the session properly before automating rather than after. Routing, naming, and template alignment fixed at import cost minutes; the same changes made after two days of automation exist mean deciding, per track, whether the pass can come with you. The prep sequence is covered in our walkthrough of automating AAF prep in Pro Tools, and the keyboard-level speedups that shorten the same stage are in our guide to Pro Tools shortcuts for mix prep and bounce.
Frequently Asked Questions
What is the difference between Touch and Latch in Pro Tools?
Both begin writing when you touch an enabled control. The difference is what happens when you let go. Touch stops writing and the parameter returns to the underlying automation, so it is suited to fixing individual moments. Latch keeps writing until the transport stops, holding the value you left it at, which suits switches and controls that have no natural resting position.
Why did Write mode erase my automation?
Because that is its documented behaviour. Write overwrites every write-enabled parameter from the moment the transport rolls, whether or not you touch a control, so playing back a section in Write mode replaces the automation underneath it. Use it for a first pass over empty automation, and return tracks to Read as soon as a pass is worth keeping.
What does Trim mode do differently?
Trim applies a relative offset to existing automation instead of replacing it. The moves you already wrote keep their shape and the whole section moves up or down together, which is what you want when the balance is wrong but the rides are right.
Does automation survive a picture change?
Not on its own. Automation is written against timeline positions, so when a new cut shifts events the automation stays where it was and no longer aligns with the audio. Handling that is the reconform stage, and how much work it turns into depends heavily on how the session was organised before the automation existed.
Can any tool write mix automation for me?
Not usefully, and it is worth being sceptical of anything that claims to. Fader rides are creative judgements about how a moment should sound. What tools can take over is the preparation around them: classifying incoming audio, routing it, naming it, aligning it to a template, and handling stem delivery at the other end.
Where do I set which parameters get automated?
In Window > Automation. Enabling only the parameters you intend to write is the single most effective way to avoid capturing plug-in or send moves during a volume pass.
fPost prepares an incoming AAF so the session is template-aligned before any automation exists, which is what makes a later picture change survivable. Details at forte-ai.com/fpost.
