⚡ Quick summary. Getting from a raw AAF import to a session that is genuinely ready for mixing involves a lot more than clicking import. The full workflow covers: a five-minute conversation with picture editorial that prevents most import problems before the export happens, the NLE-specific export behaviors that change what arrives (Avid, Premiere, DaVinci Resolve, Final Cut Pro X), the import settings that have downstream consequences, the clip-level organization work that takes the time, template alignment, stereo and mono cleanup, routing verification, the safety copy of the original session, and the revision workflow when the new cut arrives mid-project. fPost automates the clip-level classification and template alignment steps and is generally available on macOS 13+ with Pro Tools 2024.3+.
The AAF arrives. You import it. Pro Tools loads the tracks, the clips land, playback works. And that moment, right there, is where most of the work begins.
The gap between a technically valid AAF import and a session that is ready for a dialogue editor or re-recording mixer takes two to three hours on a typical project and approaches half a day on complex ones. That number is consistent across the customer discovery Forte AI has run with dialogue editors, assistants, re-recording mixers, and facility owners in London, New York, Los Angeles, and Washington D.C.
This guide covers the full AAF workflow in Pro Tools as professional audio post engineers run it: the conversation you should have with picture editorial before the AAF is exported, through import, through post-import organization, all the way to a session that is correctly templated, verified, and ready for the work ahead. It also covers what happens when the new cut arrives mid-project, which is where workflow discipline either holds up or breaks down. For the automation-specific companion (clip-level classification with AI breakdown, Mix template matching against the open Pro Tools template, Mono to stereo pair detection and conversion), see how to automate AAF prep in Pro Tools with fPost.
The Conversation to Have Before the AAF Is Exported
The single most effective thing you can do to reduce AAF prep time is to align with picture editorial before the export happens. Most of the problems that surface during import are preventable, but only if they are addressed at the source. Five minutes of conversation prevents an hour of cleanup.
| Question to ask picture editorial | Why it matters |
|---|---|
| What NLE and which version was used? | AAF behavior changes across versions, especially for Premiere. Knowing the source narrows down expected issues before they surface. |
| Are stereo files delivered as split mono pairs or as interleaved stereo? | Premiere-originated material often arrives as split mono. Knowing this upfront lets you prepare; finding it mid-session costs unbudgeted time. |
| Are handles included, and how long? | Dialogue editors need handles to work the edit points. Two seconds minimum, ten seconds ideally. Handles must be explicitly requested on most NLE exports. |
| What timecode convention is being used? | Commercial work can mix two-pop, slate, and first frame of action across the same batch of deliverables. Confirming consistency upfront prevents alignment problems that are painful to diagnose after import. |
| Is an EDL available alongside the AAF? | When AAF metadata is corrupted or missing, the Edit Decision List is the fallback for reconstructing what picture editorial intended. Worth asking for even if you hope not to need it. |
What an AAF Is, and Why That Matters
An AAF is the Advanced Authoring Format, an open-standard container file designed specifically for moving projects between applications in post production. It carries audio clips, video reference, timecode, volume automation, track names, and references to external media files. It was built as the successor to OMF, which lost volume automation and track names during export and import cycles. Avid's OMF / AAF Import and Export documentation is the canonical reference on what the format is designed to carry, and the Avid Knowledge Base article on the difference between OMF and AAF covers the technical distinctions for engineers working with mixed handoff formats.
What AAF also carries, unfortunately, is the fingerprint of whichever NLE generated it. The format is open standard and widely supported, but supported does not mean implemented identically. The way Avid Media Composer generates an AAF is different from how Adobe Premiere does it, which is different from how DaVinci Resolve does it, which is different from Final Cut Pro X (which does not have a native AAF export at all). Understanding which NLE you are receiving from, and what to expect from that NLE's output, changes how you approach the import.
| NLE | AAF behavior to expect | What to verify before import |
|---|---|---|
| Avid Media Composer | Most consistently reliable. Format was developed alongside Media Composer. | Handles are not included by default and must be explicitly requested. Confirm the export consolidates clips to avoid media gaps. |
| Adobe Premiere | Routinely splits stereo into mono pairs on export, creating split-stereo content that needs detection and correction. Nested clips, merged clips, and multi-camera sequences often do not resolve cleanly. | Use Copy Complete Audio Files (not Embed Audio). Note which Premiere version was used. Expect dual-mono on stereo content. |
| DaVinci Resolve | Least consistent AAF exports of the major NLEs. Common problems include missing audio, broken clip references, and metadata that does not survive the transfer. | If sync problems persist, export an XML from Resolve and convert it using a compatible bridge tool rather than relying on the native AAF. |
| Final Cut Pro X | No native AAF export. Standard workflow is to export an FCP X XML and convert it using X2Pro from Marquis Broadcast. | Confirm the XML to AAF bridge tool is configured to preserve audio roles and metadata from FCP X projects. |
The Pro Tools Expert panel on AAFs and OMFs from video editors is one of the most useful industry references on these handoff realities from the audio post side.
Importing the AAF into Pro Tools: The Steps That Actually Matter
Once you have the file and you know what to expect from it, the import process itself is where a few decisions have downstream consequences worth getting right the first time.
Open the correct session first. Import the AAF into your facility template session, not into a blank Pro Tools session. Starting with a blank session means rebuilding your routing and folder structure after the fact, which is slower and more error-prone than importing into a structure that is already in place. Your template is the target. Import to it.
Set Audio Media Options to Copy from Source Media. This copies all audio files into the session's Audio Files folder, making the session self-contained. Leaving this set to Link to Source Media creates a dependency on wherever the original media files live. At any facility where files move around, that is a risk.
Confirm the import options before clicking through. Pro Tools' import window gives you control over which elements come in. Check that you are getting the correct audio sample rate, that the import is not about to overwrite existing tracks in your template, and that the handle length is what was agreed on.
Verify playback before doing anything else. Once the session loads, scrub through the timeline. All clips should play back correctly, timecode should be where you expect it, and the handles should be audible. This takes a few minutes and catches problems before you have spent an hour organizing a session with corrupt media.
What Happens After Import: The Organization Work
Here is the part that takes the time.
A freshly imported AAF session is organized around the picture editor's workflow. Tracks are named for their role in picture editing, if they are named at all. Audio elements are scattered based on how the edit evolved, not based on audio function. Dialogue lands on SFX tracks because the editor dropped production sound wherever there was room. Music sits in unexpected places. Generic track names like Audio 1, Audio 2, Audio 3 give you nothing useful.
Before any routing or creative work is possible, the session needs to be sorted at the clip level. This distinction matters. Sorting at the track level means moving whole tracks around. That is not enough, because content types are scattered within individual tracks. You need to assess each clip or region, identify what it contains, and move it to the correct position in your template's structure. That requires listening. Scripts that parse track names fall apart here because the names are not reliable. You have to hear what is on each clip and make a judgment.
A dialogue editor at a small London post facility described a typical incoming session as a high count of dialogue tracks, many seemingly duplicated, with a mix of useful material and other content with no clear logic, including pieces of dialogue buried inside sound effects tracks. That is not a worst-case scenario. That is Tuesday.
A supervising sound editor at a large post studio described what correctly organized means at the high end of the work: booms separated, and most importantly grouped by scene because the boom perspective changes with the frame; lavaliers more stable and able to stay actor-linked. Getting to that level of precision from a generic AAF import requires clip-level classification of every piece of production sound. That work is mechanical but expert.
Template Alignment: This Is the Hard Part
Sorting clips by content type is necessary but not sufficient. Everything also needs to land in the correct position within the facility's routing template.
A Pro Tools template for audio post is not a cosmetic preference. It defines the entire signal flow of the session. Folder tracks contain related content and route to stem buses. Color coding identifies content type at a glance. Bus assignments connect everything to the print master. I/O assignments match the physical patch bay. The template is the operating system of the facility, and it took a lot of work to build.
When an AAF arrives with flat, generically named tracks, the clip-sorting work described above is what connects incoming content to that template. Once each clip's content type is known, you move it to the appropriate folder, assign the correct routing, and apply naming and color conventions. The template tracks stay intact. Content is placed inside them.
A framing that came up consistently in customer discovery: the goal is not to import tracks into Pro Tools. The goal is to get content onto the engineer's tracks in their template. That is the frame that clarifies what successful import means.
For facilities standardizing across multiple rooms and rotating staff, the requirement is reproducible output. Assistant editors work in shifts across multiple teams, so prep output has to be indistinguishable across shifts. The path to adoption is shared facility presets and documented standards, not bespoke per-person workflows. The standard is not about any individual engineer's preference. It is about output that anyone who opens the session can understand immediately.
Stereo and Mono: Fix This Before Anything Else
Stereo cleanup is not the most interesting part of AAF prep, but it is the part that causes the most routing problems if it is left until later.
The issue is that stereo and mono files need to land on the correct track types in Pro Tools. A stereo file on a mono track does not play correctly. A mono file on a stereo track wastes a track and can cause confusion in the mix. And the specific Premiere dual-mono problem, where what looks like stereo is actually two identical mono channels masquerading as a stereo pair, is invisible until you start listening. This export behavior is documented in Vassar College's Premiere AAF and OMF export guide and is the single most common source of stereo cleanup work in audio post.
The right time to address this is immediately after import, before you start building routing. Audit all stereo content first. Identify genuine stereo files, split-stereo pairs that need to be re-interleaved, and dual-mono situations where the two channels carry identical audio. Handle each case correctly, then proceed with template alignment. Finding a mono-on-stereo-track problem after hours of routing work means undoing things you just did.
A commercial producer working on high-turnover content for a major sports and tech client described this as a daily reality: time spent splitting, fixing, and re-interleaving audio before mixing can begin. That time is coming out of every session, on content that runs on a tight production schedule, for clients who do not know or care how it is organized in Pro Tools.
Routing Verification and the Safety Copy
Once content is placed in the template and stereo is resolved, verify routing before the session leaves the prep stage.
This means tracing every signal path: dialogue tracks to dialogue bus, dialogue bus to print master, SFX tracks to SFX bus, and so on through every stem and bus in the session. It means checking sends. It means confirming that I/O assignments match the room's physical configuration. And it means verifying that the routing was not accidentally altered during the clip-moving process, which can happen.
A routing error found during prep takes minutes to fix. The same error found during a mix session, when the re-recording mixer is waiting or the client is in the room, is a different kind of problem.
Before anything: preserve a safety copy of the original imported session. Every professional who contributed to fPost's development mentioned this independently. The question "what did editorial actually send?" should always be answerable, and the answer should not require reconstructing history. If you always overwrite the original reality, you remove a useful anchor for verification and debugging. The safety copy costs nothing to keep and occasionally saves significant time.
When the New Cut Arrives: Managing AAF Revisions
The workflow above describes what happens when the first cut lands. Production does not stop there. Edit changes arrive mid-project. Sequences get restructured. New ADR gets recorded. SFX placements shift.
Managing revisions in an already-organized session is one of the most technically demanding parts of audio post workflow, and the sessions that hold up best under revision pressure are the ones that were organized correctly from the start.
| Step | What to do | Why |
|---|---|---|
| Import the new AAF into a duplicate | Open the new AAF in a separate duplicate of the current working session, not the working session itself | Protects current work from accidental overwrite during comparison |
| Compare against current | Identify what changed, where the changes land on the timeline, and what existing work needs to be conformed | Establishes scope before any restructuring begins |
| Keep the original imported AAF tracks | Retain them in the session, muted and clearly named as reference | Gives a comparison anchor throughout the conform process |
| Distinguish versions in naming | Working versions versus archived versions get separate naming conventions | The thing that makes revision rounds manageable rather than chaotic |
| Only then incorporate changes | Apply the conform decisions to the working session after the comparison is done | Prevents partial-conform states that lose track of what was changed where |
Sessions that were assembled under deadline pressure with inconsistent naming and ad hoc structure tend to accumulate compounding problems with each revision. The ones that were set up correctly from the beginning take new cuts in stride.
Where Automation Fits Into This
The AAF workflow described above is complex and requires expertise to do correctly. Automation that saves meaningful time has to handle the hard parts, not just the mechanical ones.
The hard parts are content classification at the clip level and template alignment. Those are the steps that require judgment about what audio content contains, not just where it sits. Tools that automate track renaming or session formatting help at the margins. The significant time savings come from a tool that can classify clips by audio content type and place them into the correct positions in the existing template automatically.
fPost approaches this using content detection that analyzes the audio itself rather than relying on track names or metadata.
| fPost capability | What it does | What it handles in the workflow above |
|---|---|---|
| Analyze and reorganize any AAF/PTX | Reads the AAF and applies classification and template against the open Pro Tools session | The post-import organization and template alignment steps |
| AI breakdown → DX / MX / SFX classification | Classifies each clip at the signal level into dialogue, music, or sound effects | The clip-level sorting work that takes the most manual time |
| Mix template matching | Maps classified content into the facility template already open in Pro Tools | The template alignment step, with the template kept as source of truth |
| Mono → stereo pair detection & conversion | Detects dual-mono pairs and converts to interleaved stereo | The Premiere dual-mono case, before routing begins |
| Carbon copy backup AAF | Preserves the original AAF alongside the reorganized session | The safety copy requirement that every professional flagged |
| Batch Import | Loads multiple AAFs in one operation | The 10-to-15-deliverables-minutes-before-the-session commercial case |
| Metadata forensics | Surfaces video rate, TC format, sample rate, and clip metadata completeness | The corrupt-AAF discovery problem, surfaced before the session reaches anyone |
| Retain import session data | Keeps timeline position, automations, and timecode intact through reorganization | The downstream automation and timecode integrity |
| Works completely offline | Runs locally, no internet, no dongles, media never leaves the workstation | Facilities with air-gapped or compliance-sensitive workflows |
fPost is generally available on macOS 13 and above with Pro Tools 2024.3. Studio is €399 per year (€149 per quarter). Suite is coming soon. Enterprise pricing is custom. The AAF Checker tier is free forever. Full breakdown on the fPost pricing page.
Frequently Asked Questions
What is an AAF and why does it need prep work in Pro Tools?
An AAF (Advanced Authoring Format) is the standard file for moving a project from a picture editing application to Pro Tools. It carries audio clips, video reference, timecode, and metadata. It needs prep work because it is organized around the picture editor's workflow, not around audio post workflow. Content types are scattered, track names may be generic, nothing is mapped to a facility routing template, and stereo / mono handling may need correction. Getting from an imported AAF to a session that is ready for a mixer requires sorting, organizing, and template-aligning the session after import.
How do I import an AAF into Pro Tools correctly?
Open your facility template session first, not a blank session. Then import the AAF using File > Import > Session Data. Set Audio Media Options to Copy from Source Media so all audio is copied into the session's Audio Files folder. Verify sample rates before confirming. Once the session loads, scrub through the timeline to confirm all clips play back correctly and handles are present before starting any organization work.
What is the difference between an AAF from Premiere versus Media Composer?
Media Composer produces the most reliable AAF exports because the format was designed alongside it. Premiere's exports are more variable, particularly around stereo handling, where Premiere often splits stereo content into mono pairs that need to be detected and re-interleaved in Pro Tools. Premiere's export behavior also changes across versions, so knowing which version was used helps anticipate known issues. DaVinci Resolve produces the least consistent exports of the major NLEs.
What should I check with picture editorial before the AAF is exported?
The most important things to establish upfront are: whether handles are included and how long they are, whether stereo files are being delivered as interleaved or split mono, which NLE and which version was used, what timecode convention applies, and whether an EDL is available alongside the AAF. These conversations prevent the majority of common import problems.
How long should AAF prep take?
For a straightforward project from a clean source, prep can be done in 30 to 60 minutes. For complex sessions or Premiere-originated material with split stereo, scattered content, and no reliable metadata, two to three hours is typical. For dense variety content, shows with large track counts, or AAFs where metadata has been lost entirely, it can approach a full day. The variables are the quality of the incoming file, the complexity of the content, and how closely it matches the template it needs to land in.
What is a safety copy and why do I need one?
A safety copy is an untouched version of the session as it arrived from picture editorial, preserved alongside the organized working version. It serves as a reference point when questions arise about what was in the original, when conforming to a new cut, and when something in the organized version does not match expectations. Every professional should keep one. fPost preserves a Carbon copy backup AAF automatically.
When a new cut arrives mid-project, what is the correct approach?
Import the new AAF into a duplicate of the current working session, not directly into the session you are working in. Compare the new cut against the current state to understand what changed. Identify which elements of existing work need to be conformed to match the new picture. Only after that assessment should changes be incorporated into the working session. Sessions that were organized consistently from the start handle revisions significantly better than those assembled under pressure with inconsistent structure.
Where does fPost fit into this workflow?
fPost automates the clip-level classification and template alignment steps, plus dual-mono detection and the safety copy of the original AAF. The pre-export conversation, the verification step after import, and the conform decisions on revisions remain with the engineer. fPost handles the mechanical translation between picture editorial's structure and audio post's structure.
Stop Losing Hours to AAF Prep
The pre-export conversation, the NLE-specific import settings, and the revision discipline stay with the engineer. The clip-level classification and template alignment are where the manual hours land, and where automation saves the most time. The fPost product page walks through how AI breakdown, Mix template matching, Batch Import, and Metadata forensics handle that layer. Pricing sits on the fPost pricing page. To see fPost run on a session that looks like the sessions you receive in practice, request a demo.
About the author: Loris Comba is Co-founder and CEO of Forte AI, an audio automation entrepreneur focused on eliminating repetitive operational tasks in professional audio production. Forte AI builds fPost (audio post production automation) and fMusic (mix prep and stem export automation) for Pro Tools and Logic Pro.
