Video summary

How to Prevent Losing Plug-In Automation In Pro Tools: Baseline Automation Explained

Main summary

Key takeaways

Technology

Baseline Automation / Plugin Automation in Pro Tools

The video explains Baseline Automation in Avid Pro Tools as a critical safety mechanism. When you write automation for a plugin (e.g., an EQ), you need to ensure you don’t accidentally leave “missing” parameters—because Pro Tools may then snap those parameters back to defaults or wipe out earlier EQ moves.

Key issue

When you create or record automation in Pro Tools, it only applies to the plugin parameters that are included in the plugin’s Plugin Automation Enable list. If you automate only some parameters (or none), Pro Tools may revert the others to default behavior as you move between sections/scenes.

Core technique / Why it matters

In a template, you may insert a plugin (example: FabFilter Pro-Q 3; also mentions Pro-Q4 in a different/future context).

You must confirm the plugin’s automation settings include the parameters you want to control. If a parameter isn’t included:

  • Your “baseline” settings may not persist through the session.
  • Later automation written for only a subset of parameters can effectively erase what you thought was an earlier EQ move when you return/preview.

Tutorial / Step-by-step concepts shown

1) Template setup + baseline EQ

  • The presenter works on a template for background tracks (described as bgs/cbgs/bg groups).
  • He uses a default 7-band EQ preset with slight low/high rolloff.
  • The goal is to create a baseline automation pass so the plugin automation is “preset” across the timeline.

2) Enable the correct plugin parameters

  • The video points to the plugin’s “Plugin Automation Enable” section.
  • You may need to select all automatable parameters and add them so they are actually included in automation writing.

3) Demo behavior when parameters are correctly included

  • After writing baseline automation across a selection, later EQ automation is written for a specific region.
  • When playback passes that region, the EQ snaps back to the baseline/default—as intended.

4) Demo behavior when parameters are not included

  • He removes baseline automation (or demonstrates the outcome when automatable parameters weren’t selected properly).
  • After writing automation for a small section, returning later makes the earlier EQ change disappear, because the plugin parameters weren’t included for automation.

5) Fixing a “mess”

  • If automation was written incorrectly:
    • Return to the default state.
    • Re-write baseline automation to the intended section(s).

6) When to write baseline (timing strategy)

  • He recommends setting baseline early in the session, leaving time headroom before the “hour” so editors/imports don’t cause timing issues.
  • Example: he starts baseline around 00:58, then writes baseline across the session length.

7) Handling previously created automation

  • If baseline was written for the whole thing, it may already exist.
  • He describes re-highlighting the whole timeline and re-setting baseline to clear incorrect automation.

Practical takeaway / Checklist

  • Ensure the plugin Automation Enable list includes all parameters you want automated before writing baseline.
  • Create baseline automation for key plugin chains (e.g., EQ used for backgrounds/Foley/dialogue/music).
  • Start baseline early enough to avoid editor import/timeline offset problems.
  • If you switch plugin versions (e.g., Pro-Q2 → Pro-Q3), you may lose parameter selections—so re-check the plugin automation enable configuration.

Main speaker / Source

  • Joel D. Galan — sound re-recording mixer and industry coach

Original video