Automation

What Automation Actually Is

Automation is a series of instructions: at this moment, set this parameter to this value. At this later moment, set it to that value. Logic draws a line between those points and smoothly transitions from one to the other. The result is a parameter that changes over time without you touching anything during playback.

If you have ever used the Fade tool on the edge of an audio region, you have already seen the concept. Automation extends that idea to everything — not just volume, not just at the edges of regions, but any parameter at any point in the timeline.

Showing Automation

Press A and every track in the Tracks area grows a translucent overlay. This is the automation lane — the space where automation data lives. By default, you are looking at the Volume parameter, but you can change it to anything.

The dropdown menu on each track’s automation lane lets you pick which parameter you are viewing: Volume, Pan, Mute, any send level, or any parameter from any plugin loaded on that track. If you have a Channel EQ on the track and you want to automate the frequency of Band 3, it is in there.

Automation Modes

Every track has an automation mode selector — a small dropdown in the track header that reads Read by default. This controls what happens during playback and recording.

Read

Read is the default. Logic plays back whatever automation is written on the track. If you grab a fader while in Read mode, it snaps back to the automated position as soon as you let go. Read mode protects your work — it will not let you accidentally overwrite automation by bumping a fader.

Touch

Touch is the mode you will use most. During playback, Logic follows existing automation. The moment you grab a parameter — a fader, a knob, a send level — Logic starts recording your movements as new automation. When you let go, the parameter returns to wherever the pre-existing automation says it should be.

Think of it like a conversation: the existing automation is talking, and Touch mode lets you interrupt. When you stop talking, the original voice picks back up.

This is the safe way to write automation. You can punch in on a specific section, ride a fader through a chorus, and everything before and after stays untouched.

Latch

Latch works like Touch with one difference: when you let go, the parameter does not return to the previous automation. It stays at whatever value you left it at and holds that value forward, overwriting any existing automation from that point on.

Use Latch when you are establishing a new level for the rest of the song — for example, when you want the bass to sit 2dB louder from the second chorus onward. Touch would snap back to the old level when you release the fader. Latch holds the new level.

Write

Write overwrites all existing automation from the moment playback starts. It does not care what was there before. In practice, you will rarely use Write mode. Touch and Latch cover almost every situation, and Write is too easy to accidentally destroy good work with.

Choosing a Mode

Start with Touch. When you understand why it behaves the way it does, Latch will make sense as the natural complement. Write is there if you need it, but it is the sledgehammer in a toolbox full of scalpels.

Writing Automation with the Mouse

You do not need a control surface or a fader to write automation. The pencil and pointer tools work directly in the automation lane.

With automation view open (A), click anywhere on the automation line to create a

To move a node, drag it. To delete one, select it and press Delete. To select multiple nodes, rubber-band select across them or Shift-click.

Drawing Freehand

Switch to the Pencil tool and draw directly on the automation lane. This creates a dense series of nodes following your mouse path — useful for organic, hand-drawn movements like a filter sweep or a gradual volume ride.

Straight Lines and Ramps

The Pointer tool is better for precise work. Click to create a starting node, click further along the timeline to create an ending node, and Logic connects them with a straight line. This gives you clean fades and predictable ramps.

Curves

After creating two nodes connected by a straight line, hold Option and drag the line segment between them. It bends into a curve — concave or convex depending on which direction you drag.

Writing Automation with Faders

The other way to write automation is to move the actual controls — faders, knobs, pan pots — while the transport is playing in Touch or Latch mode.

1. Set the track’s automation mode to Touch
2. Press Play
3. Grab the fader (in the Inspector, the Mixer, or on a control surface) and move it
4. Logic records your movements as automation data
5. Let go — the fader returns to wherever the previous automation says it should be

This is how you “ride” a vocal — play the song and push the fader up for quiet words, pull it back for loud ones. It is physical and intuitive, and the result often sounds more musical than automation drawn with a mouse.

If you are using a hardware controller (a knob, a fader, a MIDI controller mapped to a parameter), the same principle applies. Set the mode, hit play, move the physical control. Logic captures it.

Track Automation vs. Region Automation

This is a distinction that trips people up, but it matters once you start moving regions around.

Track Automation

Track automation is the default — the kind you have been reading about so far. It is anchored to the timeline: “at bar 17, set the volume to -6dB.” Move the region that lives at bar 17 to bar 33, and the automation stays at bar 17. The automation and the audio are independent.

This is the right choice for mix moves that are tied to song structure — a filter opening into the chorus, a volume ride through a section, a pan move at a specific moment. These are decisions about where in the song something should happen.

Region Automation

Region automation lives inside the region itself. Move the region, the automation moves with it. Copy the region, the automation copies with it. Delete the region, the automation is gone.

To switch to region automation, click the automation mode dropdown on the track and choose Region instead of Track (or look for the toggle in the automation lane header).

Region automation is the right choice when the automation is part of the musical idea — a filter wobble on a synth riff, a volume swell on a pad, a panning effect that is integral to the sound. If you would want that automation to follow the region when you rearrange the song, it belongs in the region.

When Track and Region Automation Collide

If you have both track and region automation on the same parameter, region automation takes priority within the region’s boundaries. Outside the region, track automation applies. This can create unexpected jumps if you are not aware of it — another reason to be deliberate about which type you are using.

Editing Automation

Selecting and Moving Nodes

Click a node to select it. Shift-click to add nodes to the selection. Rubber-band select to grab a range. Once selected, drag the nodes — horizontally to shift timing, vertically to change value, or both.

Snapping

Automation nodes snap to the grid like everything else in Logic. Hold Control to temporarily override snapping for fine adjustments. This is useful when you want a fade to start slightly before the downbeat rather than exactly on it.

Copy and Paste

Select a range of automation nodes and use Copy (⌘ + C) / Paste (⌘ + V). The pasted automation lands at the playhead position. This is a fast way to replicate a volume ride or filter sweep across multiple sections.

Paste at Original Position (⌥ + ⌘ + V) puts the copied automation back at the exact timeline location it came from — useful when you are copying automation between tracks rather than between sections.

Deleting Automation

Select nodes and press Delete to remove them. To wipe an entire track’s automation for a parameter: click in the automation lane, select all with ⌘ + A, then Delete.

You can also delete automation through the Mix menu: Mix > Delete Automation offers options to delete visible automation, all automation on selected tracks, or all automation in the project. Use these with care.

Trim Automation

Trim is a modifier to Touch and Latch modes. Instead of writing absolute values (“set volume to -8dB”), Trim writes relative offsets (“move whatever is there up by 2dB”).

Say you have spent twenty minutes riding a vocal — every breath, every dynamic shift, carefully automated. Then you realize the whole vocal is 1.5dB too quiet. Without Trim, you would have to redraw the entire ride. With Trim, you grab the fader, push it up 1.5dB, and every node in your existing automation shifts up by that amount. The shape of your ride is preserved.

To enable Trim, look for the Trim checkbox in the track header when automation is visible, or access it through the automation mode dropdown. It is available as a modifier to both Touch and Latch.

The Automation Folder

When you are automating multiple parameters on the same track — volume and a filter cutoff and a send level — switching the dropdown back and forth gets tedious. The automation folder solves this.

Click the disclosure triangle to the left of the automation parameter dropdown (or the + button to add lanes). Each automated parameter gets its own lane stacked vertically below the track. You can see and edit volume, pan, and three plugin parameters simultaneously.

This is where things get surgical. You can line up a volume dip with a filter sweep and a send increase, seeing all three on screen at once.

Copying Automation Between Tracks

Select automation nodes on one track, copy them (⌘ + C), select the destination track, and paste (⌘ + V). The automation lands at the playhead position on the new track. If both tracks have the same parameter (Volume, Pan, etc.), the automation maps directly. For plugin-specific parameters, the destination track needs the same plugin loaded.

This is useful when you have multiple background vocal tracks that need the same volume ride, or parallel instrument tracks that should share a filter sweep.

What to Automate: Practical Starting Points

Volume

The most common automation target. Vocal rides — leveling out a performance word by word, phrase by phrase. Section contrast — dropping the bass 2dB in the verse so it hits harder in the chorus. Fading out an effect tail before the next section.

Send Levels

Automate the send to a reverb bus: dry verse, wet chorus. Automate a delay send to catch one word and pull it back down immediately — the “delay throw.” This is one of the most powerful automation targets because it lets you change the spatial quality of a sound across sections without touching the channel itself.

Filter Cutoff

An AutoFilter opening over eight bars is a classic build. A low-pass filter closing down before a drop creates tension. Filter automation is one of the fastest ways to make a static section feel like it is going somewhere.

Plugin Bypass

You can automate the bypass state of any plugin — on or off at specific points. A distortion that kicks in only for the bridge. A chorus effect that activates on the second verse. This is cleaner than automating a dry/wet knob because it removes the plugin from the signal path entirely when bypassed.

Top-Down Automation

A workflow concept, not a Logic feature. Start with the big moves before the small ones.

1. Section-level contrast first. Use volume automation to make the chorus louder than the verse, the bridge quieter than either. Get the large-scale dynamics of the song working.
2. Track-level rides second. Ride the vocal through each section. Bring the lead guitar up in the solo. Push the snare in the final chorus.
3. Effect automation third. Filter sweeps, delay throws, reverb changes, panning moves. These are the details that make a mix feel alive, but they only work if the foundation is solid.

Working top-down means you are not automating filter sweeps on a track whose volume balance is still wrong. Get the architecture right first.

Common Pitfalls

Moving Regions with Track Automation

If you rearrange your song — move the chorus from bar 33 to bar 25 — any track automation stays at bar 33. Your volume ride for the chorus is now playing over the wrong section. This is the single most common automation headache.

Solutions: use region automation for moves that are tied to the musical content, or select the automation along with the regions when you rearrange (click in the automation lane and include the nodes in your selection before moving).

Forgetting You Are in Touch or Latch

You set a track to Touch mode to write some automation, you finish, and you forget to switch back to Read. Next time you play the session and accidentally bump a fader, you have overwritten your automation. Get in the habit of switching tracks back to Read when you are done writing.

Automation on Muted Tracks

Automation continues to write on muted tracks if the mode is set to Touch or Latch. Muting a track does not pause automation recording.

The Order of Operations

Where automation sits in Logic’s signal flow:

Clip Gain → Plugins (in order) → Automation (volume/pan) → Fader → Output

Clip gain happens before your plugins see the signal. Plugin processing happens next. Volume and pan automation come after the plugins. The fader is the final stage before output. This means automating volume does not change how hard your compressor is working — it is post-plugin. If you need to change the level going into a plugin, automate the Gain plugin or use clip gain, not the track fader.

Key Commands from This Chapter

What to Practice

• Open a project with at least a few tracks. Press A to toggle automation view. On one track, switch the parameter dropdown from Volume to Pan, then to a plugin parameter. Get comfortable navigating what is available.
• Set a track to Touch mode and hit play. Grab the volume fader and ride it through a section — push it up for quiet parts, pull it back for loud ones. Stop playback and look at what Logic wrote. Switch back to Read and play it back.
• Draw automation with the mouse: click to create two nodes on a volume lane, then Option-drag the line between them to bend it into a curve. Listen to the difference between a straight-line fade and a curved one.
• Try region automation: create a short repeating pattern — a triangle or sawtooth shape — on a filter cutoff parameter inside a region. Copy the region out for 16 bars. You have just built a rhythmic effect with no plugins.
• Automate a send level to create a delay throw: find a word or hit you want to echo, draw the send level up for that moment and immediately back down. Play it back and listen to the single echo ringing out. This one technique shows up in almost every professional mix.
• Practice the rearrangement trap: write some track automation, then move the region to a different bar. Notice that the automation did not follow. Undo, switch to region automation, and try again. Understanding this distinction now will save you real frustration later.