Fairlight · Automation · Resolve 21

Automation Workflow in DaVinci Resolve Fairlight

This page documents the automation interface visible in the captured Resolve 21 build: the Fairlight → Automation menu, Active Range, Write To, punch/range operations and the separate Clip Gain Line workflow. It deliberately avoids carrying old Latch/Preview UI assumptions into a layout where those controls are not visible.

Fairlight automation · workflow map

Think in scope → operation → result

Resolve 21
Active Range
Write To · Fill · Glide
conceptual map — not a UI screenshot
01
Define scope
Use edit context or Active Range to decide where mix-data operations should act.
02
Choose operation
Write To, Fill Range, Glide Range and punch commands define how data is changed.
03
Keep layers separate
Track/mix automation and Clip Gain solve different levels of the mix.

2. Active Range

Define where the automation operation is allowed to act

The captured submenu exposes Active In, Active Out and Enable. On the timeline, the chosen range is visible as a purple span with boundary handles, making the scope of the operation readable before you write anything.

3. Write To

The current menu makes write targets explicit: Start, End or All

Rather than assuming a hidden automation toolbar, this page follows the controls visible in Resolve 21. Write To is a concrete menu operation, and its submenu gives three targets that can be combined with a defined active range or current edit context.

Start

A visible write target at the start side of the operation/range.

End

A visible write target at the end side of the operation/range.

All

The broad write target shown alongside Start and End in the same submenu.

4. Mix-data operations

The same menu also exposes tools for filling, gliding, joining and moving automation data

Fill Range

A dedicated range operation visible directly in the menu.

Glide Range

A separate glide operation for a range, shown immediately below Fill Range.

Join Mix

The captured menu includes Join Mix as part of the automation/mix-data toolset.

Copy · Paste · Erase · Mix List

These commands make it clear that automation is editable mix data, not only a one-time live movement.

5. Concept map

Use diagrams for the mix logic, screenshots for the exact Resolve controls

Automation is broader than one menu command, but the interface can vary between layouts and hardware configurations. This conceptual panel keeps the signal/mix idea readable without pretending to be a screenshot of controls that are not visible in the captured build.

Conceptual layer

Explains what kind of mix information can change over time and how it fits into the session.

Verified UI layer

The surrounding screenshots document the exact Automation, Active Range and Write To menus visible in Resolve 21.

Automation scope

Automation is broader than volume alone

Track fader
Level moves
Pan
Position changes
EQ / Dynamics
Tone and dynamics moves
Plug-ins
Effect parameter changes
Bus / Main
Group and final-bus automation

6. Do not confuse it with Clip Gain

Keyframes on the Clip Gain Line are useful — but they are clip-level editing, not track automation

The captured timeline shows several keyframes directly on one audio clip. This is a good workflow for local level shaping inside that clip, but it belongs to the clip itself. The Fairlight Automation menu operates on mix automation data and ranges, so the two workflows should be explained separately.

Clip Gain Line

Local correction tied to a specific clip and visible as points on the clip line.

Fairlight Automation

Mix-data workflow exposed through Automation commands, active ranges, write operations and the mix list.

7. Practical sequence

A safe Resolve 21 automation workflow from the interface we can actually verify

1. Open Automation

Use Fairlight → Automation and inspect the current read/edit state before changing mix data.

2. Define scope

If the operation should affect a limited section, set Active In/Out and enable Active Range.

3. Choose the operation

Use Write To, Fill Range, Glide Range or the other visible mix-data commands according to the task.

4. Keep clip gain separate

For a local volume fix inside one clip, use the Clip Gain Line rather than treating every small correction as track automation.

Resolve 21 · interface verification

This revision intentionally uses only the automation controls visible in the captured Resolve 21 screenshots. No separate Touch/Latch/Preview toolbar is documented because it is not visible in the captured interface.

Encyclopedia route

Automation now matches the captured Resolve 21 workflow

Use Cache & Bounce for committing processed clips, this page for mix-data operations, and Mastering for loudness and final delivery checks.