What Dialogue Edit Prep Is and What It Is Not
Dialogue edit prep is the work of building the organizational structure that makes creative editing efficient. It covers: setting the track layout, establishing routing to the dialogue bus and delivery stems, organizing incoming clips by content type and microphone source, applying color coding at the clip level, setting up room tone tracks, and configuring the session structure so picture changes can be absorbed without restarting.
It is distinct from AAF prep, which is the prior step of getting a raw AAF import organized to the point where a dialogue editor can begin. AAF prep addresses the session immediately after arrival from picture editorial: sorting content that arrived without organization, resolving stereo and mono issues, and aligning with the facility template. The full audio post production workflow covers where AAF prep ends and dialogue edit prep begins.
Dialogue edit prep is what follows in a session that has already been organized: the specific track structure, routing, and clip-level work a dialogue editor completes before touching a single edit point.
The Track Layout for Dialogue Editing
The standard dialogue editing layout in Pro Tools separates production dialogue from every other content type, and separates production dialogue by microphone source. A well-organized dialogue session has distinct track areas for each of the following.
Production boom dialogue. The primary microphone on most production recordings. Boom tracks carry the acoustic perspective of the shot: a wide shot sounds different from a close-up. The dialogue editor uses these differences to match the acoustic character of adjacent shots when editing.
Lavalier dialogue. The actor-linked alternative. Lavs maintain a consistent acoustic character across camera positions. When the boom has problems, whether handling noise, a difficult room, or an interference issue, the lav is the fallback. Having lav tracks immediately below the corresponding boom tracks in the session layout is what makes that switch fast during the edit.
Backup and additional production recordings. Insurance radio mics, plant mics, or additional boom positions used on multi-character scenes. These tracks exist in the layout even when used infrequently, because finding them during the edit is faster than creating them.
ADR tracks. Separate from production dialogue. Automated dialogue replacement is recorded in a controlled studio environment and should never sit on the same tracks as production sound. ADR tracks in the facility template typically have their own routing: a dedicated sub-group or separate stem assignment that keeps re-recorded and production dialogue independently controllable through the final mix.
Editing workspace tracks. Empty tracks reserved for the cutting process. Temporary destinations for clip copies, in-progress edit comparisons, or alternate takes under consideration. These tracks do not carry content that delivers; they carry the working material the editor needs visible during the session.
The track layout is not arbitrary, and it is not the dialogue editor's personal preference. It is the facility's standard, encoded in the Pro Tools session template that loads at the start of every project. The convention that makes a facility template valuable is that it does not change: the session on Monday has the same track names in the same positions as the session on Friday, which is what makes multiple editors or rotating shifts capable of working on the same project without rebuilding structure.
Track Naming and Color Coding Conventions
Track names follow function, and function does not change across projects. Common naming patterns in professional post facilities:
- Boom tracks: DX Boom 1, DX Boom 2 for a two-character scene; Boom A, Boom B for simpler structure
- Lav tracks: DX Lav 1, DX Lav 2; or Lav-A, Lav-B keyed to the corresponding boom track
- Backup: DX Backup or the recording device designation (e.g., Plant, Radio)
- ADR: ADR 1, ADR 2 in their own track area, with the routing that distinguishes them from production
- Room tone: RT 1, RT 2 below the production dialogue group
Color coding reinforces track function at a glance. The specific colors vary by facility, but the logic is consistent: one color per track type, applied in the template so every session starts with it already in place. When an editor clips a section of lav audio into a boom track for a repair, the clip color changes to match the destination track automatically through Pro Tools clip-inherits-track-color behavior.
The color system's purpose is speed. During a dense dialogue edit, the editor knows whether they are looking at a lav clip or a boom clip from the waveform display without reading names or listening. That recognition reduces friction on every decision in the session.
Routing: Bus Structure for Dialogue Editing
Routing in a dialogue editing session serves two functions: monitoring during the edit, and stem delivery at project completion.
For monitoring, production dialogue typically routes to a dialogue sub-bus that feeds the main session output. The sub-bus allows the editor to balance the overall dialogue output without adjusting individual track faders, and it provides the listening reference during the edit. The ADR sub-bus runs parallel to it, typically at the same level but independently controlled.
For delivery, stem routing is set in the facility template before the project opens. Dialogue stem, ADR stem, and room tone each deliver as separate outputs. This routing is already in place in the template. What the editor does during the project is fill the tracks; the signal chain from those tracks to the delivery outputs does not change project to project.
The Pro Tools session template article covers how a facility standard template encodes all of this: track layout, routing, color coding, and I/O assignments as a single file that loads at project start.
Clip-Level Organization: The Work That Track Layout Cannot Do
Track layout creates the scaffold. Clip-level organization is the work of filling it correctly.
An AAF from picture editorial places clips on the tracks the picture editor created. A shot that used both boom and lav may have both clips on adjacent tracks with similar names, or the editor may have used the lav as a cut-in on the primary dialogue track with no indicator that a second recording exists. The dialogue editor needs to know, for every clip in the session, what microphone recorded it and whether an alternative recording of the same moment is available.
That assessment requires working at the region level. For every section of the session, the dialogue editor should:
- Move boom clips to the boom track area and lav clips to the lav track area, preserving sync
- Identify backup recordings and place them directly below the primary on their designated track
- Note sections where no clean alternative exists if the primary recording is problematic
- Mark known problem sections before the edit begins, so every issue is flagged without listening through the session from scratch
Region grouping in Pro Tools links clips from the same production recording so they stay in sync through edits. A boom and lav recording of the same moment, when grouped, move together when either is trimmed or repositioned. Ungrouped, a cut in the boom requires a manual matching cut in the lav. On a session with dozens of scenes and multiple takes per scene, ungrouped clips become a source of sync errors.
Color marking at the clip level adds status information beyond track type. A verified clean clip gets one marker state; a clip with a known problem gets another. The system varies by editor, but the principle is that the clip should communicate its status visually so the editor does not have to listen to the same problem twice to remember what it was.
Room Tone and Noise Floor Setup
Every dialogue editing session requires room tone: a clean recording of the acoustic environment at each production location, without dialogue, sound effects, or music. Room tone fills the gaps that editing creates, smooths transitions between takes with slightly different noise floors, and maintains consistent ambience across a scene.
Setting up room tone in the session before the edit begins involves three steps.
Locating room tone recordings. Production sound recordists capture room tone on set, typically at the beginning or end of each setup. These recordings arrive in the AAF among the production audio, often labeled by the recordist with scene and location identifiers. They need to be found in the incoming material and moved to the dedicated room tone tracks in the session layout.
Populating dedicated room tone tracks. Room tone tracks sit below the production dialogue group in the standard layout. They are not editing tracks. They carry room tone clips only, routed through the dialogue bus but with a distinct track color that distinguishes them from production audio. In a session with multiple locations, each location's room tone lives on its own pair of room tone tracks, or at minimum is clearly labeled so the editor knows which room tone to use in which scene.
Looping room tone for sustained sections. Pro Tools region looping allows a short room tone recording to cover long sections of silence without the audible seams of manually placed copies. Setting this up early, when the room tone clips are first placed in the session, means the editor never cuts silence sections without room tone in place underneath.
Room tone tracks are part of the facility template. When the template loads and the AAF content is mapped to the correct tracks, the room tone track area already exists with correct routing. The dialogue editor locates the room tone recordings in the incoming material and places them. That is faster than creating the infrastructure from scratch each project.
Setting Up for Picture Changes
On narrative and episodic work, a new cut arriving mid-project is not an exception. The dialogue editor should assume it will happen and build the session to absorb it.
Conforming readiness is the property of a session that can accept a picture change without losing the creative editing work already completed. It requires:
Preserving the session's timeline structure. The Pro Tools PTX session prep guide covers the specific session attributes that need to be maintained. Edits applied to primary dialogue tracks should stay referenced to timecode positions, not to relative track positions, so incoming picture changes can be applied against a stable reference.
Using Clip Gain for minor level adjustments rather than track automation. Clip-level gain edits travel with the clip through a conform. Track automation applied to a track that is partially replaced during a picture change may no longer correspond to the correct moments after the change lands.
Maintaining a pre-edit safety copy. A saved version of the session at the point after AAF prep and before dialogue editing began is the baseline for any conform operation. It shows the session in its organized state before creative edits, and it provides a clean reference for what was at each timeline position before the new cut changed anything.
This pre-edit copy is separate from the safety copy of the original AAF, which is preserved during the import process itself as a record of what picture editorial actually sent.
How fPost Sets Up the Starting Line
The dialogue edit prep described in this guide begins after the session has been organized. How quickly the editor reaches that starting point depends on what the session looks like when they open it.
An unorganized AAF import, content scattered across generic tracks with nothing mapped to the facility template and stereo or mono issues unresolved, adds hours before the structural prep in this guide can even begin. The clips are on wrong tracks. The routing is absent. The color coding does not reflect content type. The editor cannot start placing room tone because the room tone recordings are not separated from the production audio yet.
fPost handles this step before the dialogue editor opens the session. When an AAF comes in from picture editorial, fPost analyzes the audio content of each incoming clip, classifying it as dialogue, music, or SFX. The session is then mapped to the facility's Pro Tools template: tracks named and routed correctly, color coding applied, and folder structure in place. Import Session Data is preserved, including timecode, automations, and the timeline structure the dialogue editor needs for conforming.
The session the dialogue editor opens is one where dialogue clips are on dialogue tracks, the facility routing is in place, and the work described in this guide starts immediately rather than after a restructuring phase that costs the same hours the template was designed to save.
Frequently Asked Questions
What is the difference between AAF prep and dialogue edit prep?
AAF prep is the work of getting the raw import organized: moving content from a flat, unstructured AAF into the correct track areas, correcting stereo and mono handling, and aligning with the facility template. Dialogue edit prep is what follows in the organized session: the specific track layout, clip-level sorting, room tone setup, and conforming structure a dialogue editor builds before the first creative edit. Both steps are part of the full post production workflow, but they have different inputs and outputs.
How many tracks does a typical dialogue editing session have?
It depends on the project and the facility template. A narrative television episode might have 12 active dialogue tracks: 4 boom, 4 lav, 2 ADR, 2 room tone, plus editing workspace. A multi-character episodic with multiple simultaneous scenes might have 24 or more. The facility template defines the base structure; the editor adds tracks as the project requires.
Why is clip-level organization more important than track-level organization?
Because audio content in an AAF from picture editorial is distributed at the clip level, not organized by the track level. A single picture editor track may carry boom dialogue, lav dialogue, room tone, and production effects in different clips across the timeline. Track names tell the dialogue editor nothing reliable about what any specific clip contains. The assessment and reorganization happen clip by clip, regardless of what the track is labeled.
What happens to dialogue editing work when a new picture cut arrives?
A new cut changes edit points in the picture, replacing some sections of the timeline and leaving others intact. Conforming the audio session to a new cut applies those changes to the existing session using a conforming tool or an EDL comparison. Sessions built with conforming readiness in mind, timeline positions intact and clip-level gains rather than track automation for minor adjustments, absorb new cuts with less rework than sessions where those structural decisions were not made.
Where does room tone come from in a dialogue editing session?
Room tone is recorded on set by the production sound recordist, typically at the start or end of each setup when the actors and crew are present but quiet. It captures the acoustic character of the location at the time of shooting and arrives in the AAF among the production audio. The dialogue editor locates these recordings, moves them to the dedicated room tone tracks in the session, and uses them to fill gaps and smooth transitions throughout the edit.
Can fPost help with dialogue session setup?
fPost handles the step before the dialogue editor begins: importing the AAF, classifying incoming audio as dialogue, music, or SFX, and mapping the session to the facility's Pro Tools template. The dialogue editor receives a session where the tracks are correctly organized and routed, and the prep work described in this guide starts from that organized state rather than from an unstructured import.
If your team is spending hours organizing incoming AAFs before dialogue editing can begin, fPost handles the import, content classification, and template mapping automatically. More at forte-ai.com/fpost.
