This article walks through what AAF prep involves, where the time leaks, and how fPost (Forte AI's automation product for audio post professionals) closes the gap between a technically valid AAF and a session that is ready for the mix. If you are reading this because the prep layer is eating your week, the short answer is: the work itself does not have to be done by hand.
Where AAF Prep Fits in the Audio Post Production Workflow
Most workflow guides describe audio post as a sequence of creative phases: spotting, session setup, dialogue editing, Foley, ADR, sound effects, sound design, music, mix and master, finalize. Those phases are well covered elsewhere. The piece they tend to skip over is the gating step that sits in front of the first creative decision: the prep that determines whether the session is ready to be worked on at all.
The phases from 1 to 7 are where the creative work happens. Phase 0 is where the time leaks. Inside Phase 0, AAF prep is the specific case where picture editorial hands off an AAF and the audio post team has to translate it into something workable.
Why AAF Prep Takes So Long
The AAF format itself is technically capable. It carries audio, video references, metadata, timecode, volume automation, track names, and external media references. Avid's official OMF / AAF Import and Export documentation is the canonical reference on what the format is supposed to carry. In principle it is a clean handoff to Pro Tools. In practice, a technically valid AAF and a session that is ready for mixing are not the same thing.
Here is what has to happen between AAF imported and session ready:
- Import the AAF. Pro Tools loads one AAF at a time. For commercial work with ten to fifteen deliverables arriving minutes before the session, that alone is a bottleneck.
- Assess what arrived. Listen through, read clip names, understand what the picture editor was thinking. This is not always obvious. Editorial structure is organized around cut decisions, not audio function.
- Sort content at clip level. This is where most of the time goes. Tracks are not the unit of organization. Clips are. Dialogue lives on SFX tracks. Music beds are scattered. The picture editor had no reason to organize by audio type.
- Identify content type per clip. Dialogue, SFX, MX, BG. None of this is labeled. A clip called Audio 1 could be anything.
- Rename tracks. You can only rename a track once you understand what is on it. This comes after sorting, not before.
- Resolve stereo and mono. Stereo files exported from Adobe Premiere arrive as split mono pairs, with patterns like Audio 1 (mono) alongside Audio 1.L and Audio 1.R on separate tracks. This behavior is documented in Vassar College's Premiere AAF export guide and is the single most common source of stereo cleanup work in audio post.
- Apply the facility template. This is the hardest step. The template is not just a starting point. It is the operating system of the facility. Every routing path, folder structure, color code, and I/O assignment has meaning. Importing a flat list of tracks and mapping it into that template requires judgment about content type, not just execution.
- Verify routing. Every path, every send, every bus assignment.
- Preserve a safety copy of the original. The question "what did editorial actually send?" needs to be answerable later.
Across the engineers Forte AI consulted during product discovery, in London, New York, Los Angeles, and Washington D.C., the time cost was consistent: two to three hours per session, approaching half a day on complex projects. The Pro Tools Expert panel of audio post professionals discussing AAFs from video editors covers the same ground from the industry side: the format works, the handoff is consistent in its inconsistency, and the cost lands on whoever opens the session next.
The Problems That Compound It
The Premiere Problem
Adobe Premiere has a specific AAF export behavior that creates disproportionate prep work. When Premiere exports stereo content, it splits it into mono pairs. The result is a combination like Audio 1 (mono) and Audio 1.L / Audio 1.R for the stereo portions on the same named track.
The result inside Pro Tools is a checkerboard of mono and split-stereo clips that are nearly impossible to sort by track name alone. You have to detect which pairs belong together, determine whether they represent true stereo or dual-mono, then convert and rebuild each one manually before you can route anything correctly. Engineers working with Premiere-sourced AAFs hit this on most jobs.
The Template Problem
Facility templates are not preferences. They are infrastructure. A template defines how dialogue, SFX, music, ADR, Foley, BG, and PFX flow through a session: which folder tracks contain which content, which busses carry each signal, what the I/O looks like, how stems are routed. An engineer who knows the template can move quickly because the routing is always the same.
When an AAF arrives with flat, generically named tracks, rebuilding that structure takes judgment. You cannot automate "move this clip to the DX track" without first knowing the clip contains dialogue. That classification problem is where AAF prep costs the most time, and where manual scripting and DIY automation tend to fail.
The bar for AAF automation is not "mostly right." It is right. The cost of verifying and correcting an automated tool's mistake on a complex session can match or exceed the cost of doing the work by hand. Trust is the central problem. Any tool that does not understand the facility template, and that does not preserve a Carbon copy backup of the original, is not solving the prep problem.
The Multi-AAF Problem
Commercial audio post often means many AAFs arriving simultaneously. A producer in commercial work can receive ten to fifteen deliverables ten minutes before the session starts. Each has its own QuickTime reference, its own timecode convention (two-pop, slate, first frame of action, often mixed within the same batch), and its own deliverable length: 60s, 30s, 15s, 6s.
Pro Tools loads one AAF at a time. The core issue for commercial work is not just sorting. It is alignment. Each spot has to land at a precise position on the timeline, not just sequentially. That is a fundamentally different operation, and it is what makes commercial AAF intake a near-impossible thing to keep clean by hand.
Who Absorbs the Cost: Roles in the AAF Prep Loop
The time cost does not land evenly. Different roles in the audio post chain absorb it differently, and the prep work most often falls on whoever is closest to the front of the chain with the least leverage to push back.
In larger facilities the prep cascades down. For freelance re-recording mixers and dialogue editors operating without an assistant, there is no one to delegate to. That asymmetry is part of why the cost stays invisible: the people doing the prep are often the same people doing the creative work, and they absorb it without flagging it as a separate line item.
What Session Ready Actually Means
A session that is ready for creative work is not just technically playable. The bar is higher.
- Content is sorted at the clip and region level, not just by track
- Track names reflect content type and function, not editorial history
- Routing matches the facility template: folders, colors, I/O, sends
- Stereo and mono are correctly resolved throughout
- A safety copy of the original AAF is preserved and accessible
- Timecode and metadata are validated
Getting from AAF imported to that state is the prep problem. It is not a minor nuisance. It is a consistent, invisible tax on every project that falls entirely on the engineer before creative work begins.
How fPost Automates AAF Prep
fPost approaches the problem differently from tools that parse tracks. Instead of reading track names and clip positions from the AAF, fPost classifies audio at the signal level.
AI breakdown listens to what is actually in each clip and identifies it as DX, MX, or SFX. Classification happens before any reorganization, which means fPost does not need reliable track names or metadata to sort correctly.
Once content is classified, Mix template matching reads the facility template already open in Pro Tools and maps incoming clips to the appropriate tracks based on the audio they contain, not based on what they were named. The template you have already built, with your routing, your folder structure, and your I/O, is what fPost uses to place content.
The workflow:
- Open the Pro Tools template session.
- Point fPost at the AAF.
- fPost analyzes content, applies classification, and reorganizes the session.
- Mono to stereo pair detection and conversion handles the Premiere dual-mono case.
- A Carbon copy backup AAF is preserved alongside the reorganized version.
- Retain import session data keeps the timeline, automations, and timecode intact.
The output meets the session-ready bar above (content sorted at clip level, template applied, stereo resolved, original preserved) in minutes instead of hours.
fPost Capability Map
Each capability listed below corresponds verbatim to a feature listed on the fPost product page. They map one-to-one against the manual workflow steps above.
Manual AAF Prep vs fPost-Automated Prep
The steps below are universal in the sense that every AAF needs them. The way you apply them is a choice.
The point is not that automation replaces the editor. It replaces the work the editor should never have been doing in the first place. The creative and editorial decisions stay with the people whose expertise shapes the deliverable.
What Carries Over and What Does Not Change
fPost keeps what matters: timeline position, timecode, automations, and the structure of the existing Pro Tools session. The template tracks remain intact. Content is placed inside them.
It does not make creative decisions. fPost is not deciding how a scene should be mixed. It handles the administrative layer (the translation work between picture editorial's structure and audio post's structure) so that when the engineer opens the session, they are already at the starting line.
Who fPost Is Built For
The discovery process that shaped fPost involved mixers and editors across a broad range of contexts. The consistent thread was not facility size, it was the gap between when an AAF arrives and when creative work can begin.
The engineers who need fPost most are:
- Freelance re-recording mixers and dialogue editors working without assistants, where the full prep burden falls on the person who should be mixing.
- Independent post facilities with small teams handling high-volume work, where prep time compounds across multiple sessions per day.
- Commercial facilities with high-turnover deliverables, multiple AAFs per session, tight delivery windows, and standardized templates across rooms.
- In-house production teams where a single audio person handles everything from intake to delivery and conforming costs grow with each new cut.
fPost runs on macOS 13 and above. Pro Tools 2024.3 is required. The DAW language setting must be English. It works completely offline. No dongles, no cloud processing, no media leaving the workstation.
Pricing
fPost is generally available and self-serve. The free AAF Checker tier covers metadata forensics on incoming AAFs and is the fastest way to see what fPost surfaces on a file you actually received.
Full breakdown on the fPost pricing page.
Frequently Asked Questions
What is fPost and who is it for?
fPost is software for audio post professionals that automates AAF import prep and PTX session organization in Pro Tools. It is built for re-recording mixers, dialogue editors, and audio post facilities who need to get from raw AAF to workable session without spending hours on manual sorting, template matching, and stereo repair.
What problem does fPost solve?
The gap between a technically valid AAF and a session that is ready for creative work. That gap (sorting clips by content type, applying the facility template, fixing split stereo, resolving track naming) costs two to three hours per session on average, sometimes more. fPost automates that translation layer.
How does fPost work with AAFs in Pro Tools, step by step?
Open the template session in Pro Tools, point fPost at the AAF (or at multiple AAFs through Batch Import), and fPost handles the rest. AI breakdown classifies each clip into DX, MX, or SFX. Mix template matching maps classified clips into the appropriate tracks in the template. Mono pairs are detected and converted to stereo. Import session data (timecode, automations, timeline) is retained. A Carbon copy backup AAF is preserved automatically.
Does fPost organize by track or by clip?
By clip. This is the core distinction. AAF content is rarely organized by audio type at the track level: a dialogue clip can arrive on an SFX track. fPost reads the audio itself to determine content type, then places each clip in the correct location regardless of what track it arrived on or what it was named.
How does fPost handle the facility template?
fPost reads the template open in Pro Tools and uses it as the target structure. It does not impose its own routing or folder structure. It maps incoming content to the existing setup. Template tracks stay intact; content is placed inside them.
What is the Carbon copy backup AAF?
The original AAF is preserved alongside the reorganized session. Any decision fPost made can be reviewed, reversed, or rerun against the untouched source. This was the single most consistent ask across customer discovery.
What does Metadata forensics catch?
Video rate mismatches, TC format inconsistencies, sample rate problems, media status, and clip metadata completeness. The point is to surface the issues that would otherwise be discovered mid-mix.
What does fPost cost?
Studio is €399 per year or €149 per quarter. Suite is coming soon at €599 per year or €199 per quarter. Enterprise pricing is custom. The AAF Checker tier is free forever.
What are the system requirements?
macOS 13 or later. Pro Tools 2024.3. DAW language set to English. Works fully offline.
What does fPost not do?
fPost does not make creative decisions. It handles the administrative prep layer: content classification, template mapping, stereo repair, safety copying, batch intake, metadata forensics. Mixing, editing, and all creative decisions remain entirely with the engineer.
Stop Doing AAF Prep By Hand
If you are running an audio post facility, or working as a freelance dialogue editor or re-recording mixer, AAF prep is the layer most worth automating. The fPost product page walks through how AI breakdown, Mix template matching, Batch Import, and Metadata forensics handle the prep layer. Pricing sits on the fPost pricing page. The macOS download is one click away. To see fPost run on a session that looks like the sessions you receive in practice, request a demo. The team is still learning from people in the industry, and every conversation makes the product sharper.
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.
Authoritative sources cited in this article
- Avid OMF and AAF Import / Export documentation (PDF): the canonical Avid reference on the AAF format and how it is meant to interoperate with Pro Tools.
- Vassar College: Premiere Pro exporting AAF and OMF for Pro Tools: documentation of Premiere's AAF export behavior including the split-mono pattern referenced above.
- Pro Tools Expert: AAFs and OMFs from video editors, expert panel: industry panel on the AAF handoff problem from the audio post side.
- Avid Knowledge Base: difference between OMF and AAF formats: authoritative answer on the format distinction for engineers receiving mixed handoffs.
Related reading on forte-ai.com
- AAF guide for audio post production: the long-form companion on the AAF format itself.
- The problem with AAF: why the handoff format is part of the time cost.
- Premiere Pro AAF export to Pro Tools: on the dual-mono export pattern referenced above.
- Pro Tools-friendly AAF from Adobe Premiere: exporting AAFs that arrive cleaner.
- How to import AAF into Pro Tools: step-by-step: the manual import path.
- AAF workflow in Pro Tools: from import to mix-ready session: the end-to-end view.
- The hidden cost of Pro Tools PTX session prep in audio post production: the PTX-side companion when the session is already inside Pro Tools.
