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 is something that only makes sense once you have done this work for a while. From outside the industry, importing a file sounds like the end of a task. From inside, it is the start of one. The session that just loaded is organized around the picture editor's decisions. Before any creative work begins, you need to translate it into a structure that reflects how audio post actually works.
This guide covers the full AAF workflow in Pro Tools, from the conversation you should have with picture editorial before the AAF ever gets exported, through import, through post-import organization, all the way to a session that is properly templated, verified, and ready for the work ahead. And because the workflow does not end when the first cut is approved, it also covers what happens when the new cut arrives mid-project.
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.
The questions worth asking, and getting actual answers to, before the handoff:
What NLE was used and which version? This matters more than it probably should. Premiere's AAF behavior changed meaningfully across versions, and whether the editor was on Premiere 2023 or Premiere 2024 will affect what arrives.
Are stereo files being delivered as split mono pairs or as interleaved stereo? This is the most consequential question for anyone regularly receiving Premiere-originated material. If you know split mono is coming, you can prepare for it. If it surprises you mid-session, it costs time you did not budget.
Are handles included? Handles are the extra audio before and after each edited clip. Dialogue editors need them to work. If the editor exports AAF with no handles, or with handles shorter than a second, there is nothing to work with at the edit points. Two seconds minimum, ten seconds ideally, is the professional standard. Ask for it explicitly.
What timecode convention is being used? On commercial work especially, you can receive 10-15 AAFs in a batch with different timecode references: two-pop, slate, first frame of action, all mixed together. One of our interviewee described this exact scenario, receiving that many deliverables ten minutes before the session starts, each with its own QuickTime reference. Knowing upfront which convention to expect, and confirming it is consistent across deliverables, prevents alignment problems that are genuinely painful to diagnose after import.
Is there an EDL available alongside the AAF? An EDL (Edit Decision List) is a separate file that carries metadata about the edit. When AAF metadata is corrupted or missing, which happens more often than it should, the EDL becomes the fallback for reconstructing what picture editorial intended. It is worth asking for it even if you hope not to need it.
These conversations take five minutes. The problems they prevent can take an hour to untangle on the back end.
What the AAF Actually 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. AAF preserved those things.
What AAF also carries, unfortunately, is the fingerprint of whichever NLE generated it.
The format is open source 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.
Avid Media Composer produces the most consistently reliable AAF exports. The format was developed alongside Media Composer, and it shows. If you are receiving from a Media Composer editor, the most important thing to verify is that handles are present (they are not included by default and must be explicitly requested) and that the export consolidates clips to avoid gaps in the media. Media Composer AAFs tend to behave predictably in Pro Tools, which is part of why high-end episodic and feature work still defaults to this workflow.
Adobe Premiere is where things get complicated. Premiere offers two export modes: "Embed Audio" and "Copy Complete Audio Files." The Copy Complete Audio Files option is what you want, as it copies all audio into the AAF and avoids relinking issues. However, if the editor has used nested clips, merged clips, or multi-camera sequences, those often do not resolve cleanly in the export. The bigger issue is stereo. Premiere routinely splits stereo content into mono pairs on export, creating a split-stereo situation that requires detection and correction before routing is possible. Confirming which version of both Premiere and Pro Tools was used helps narrow down known compatibility issues, as some have been present in specific version combinations.
DaVinci Resolve produces the least consistent AAF exports of the major NLEs right now. Common problems include missing audio, broken clip references, and metadata that does not survive the transfer. The most reliable workaround when Resolve-originated AAFs are causing persistent sync problems is to export an XML from Resolve, convert it using a compatible bridge tool, and route from there rather than relying on the native AAF.
Final Cut Pro X does not export AAF natively. The standard workflow is to export an FCP X XML and convert it using X2Pro from Marquis Broadcast, which generates a Pro Tools-compatible AAF. X2Pro has a good reputation for preserving audio roles and metadata from FCP X projects.
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 real 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 actually is, 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.
One of our interviewee hs been doing this work for years, described his typical incoming session: "I get a ridiculous number of dialogue tracks, many of them seemingly duplicated, with a mix of useful material and other material with no logic, pieces of dialogue buried on sound effects tracks." That is not a worst-case scenario. That is Tuesday.
Another interviewee at a large post studio, explained what "correctly organized" actually means at his level: "Nobody understands the way dialogue editing really works. I need booms separated and, most importantly, grouped by scene, because the boom perspective changes with the frame. Lavaliers are more stable and can stay actor-linked." Getting to that level of precision from a generic AAF import requires clip-level classification of every piece of production sound, which is exactly why AAF prep takes the time it does.
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 your 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 you know each clip's content type, you can 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.
As one professional in the Forte AI discovery process put it: "The goal is not to import tracks into Pro Tools. The goal is to get content onto my tracks in your template." That is the frame that clarifies what successful import actually means.
A supervising sound professional named this as the central requirement for any facility trying to standardize across multiple rooms and rotating staff: "Assistant editors work in shifts across multiple teams, so prep output must 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 reproducible 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.
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 producer who handles Microsoft and Seattle Seahawks content regularly, described this as a daily reality: "I spend time splitting, fixing, and re-interleaving audio before I can even begin mixing." That is time coming from every session, on content that runs on a tight production schedule, for a client who does not know or care how it is organized in Pro Tools.
Routing Verification Before Work Begins
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. As one source noted during the Forte AI research process: "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. Real 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.
When a new cut arrives, import the new AAF into a separate duplicate of the current working session first. Compare it against what you have. Identify what changed, where the changes land on the timeline, and what from your existing work needs to be conformed to match the new picture. Only after that assessment should changes be incorporated into the working session.
Keeping the original imported AAF tracks in the session, muted and on dedicated reference tracks with clear naming, gives you a comparison anchor throughout this process. Distinguishing working versions from archived versions in track naming is not overhead. It is the thing that makes revision rounds manageable rather than chaotic.
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 genuinely complex and requires real expertise to do correctly. Automation that saves meaningful time needs 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 actually is, 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 your existing template automatically.
fPost approaches this using content detection that analyzes the audio itself rather than relying on track names or metadata. It classifies each clip as dialogue, music, or SFX — the three categories AI-R currently detects — then applies that classification against your open Pro Tools template. The Premiere dual-mono problem is handled automatically during the import process. A safety copy is preserved without any manual step.
Some producers described what they are looking for in this space: "Today, a lot of time is still burned on first-assistant tasks, cleaning up incoming assets, fixing stereo pairs, rebuilding templates so mixers can start immediately." That is a description of the workflow in this article. The automation that addresses it needs to be reliable enough that the time saved is not erased by the time spent verifying the output.
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 or meaningless, 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 split 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. It costs nothing and has a real value when something needs to be traced back to the source.
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 your existing work need to be conformed to match the new picture. Only after that assessment should you incorporate changes into the working session. Sessions that were organized consistently from the start handle revisions significantly better than those assembled under pressure with inconsistent structure.
If your facility is looking at ways to reduce prep time on incoming AAFs, fPost automates the clip-level classification and template alignment steps described in this article. More at forte-ai.com/fpost.
.png)
