Every audio post project starts the same way. You open the AAF you received. And before a single creative decision gets made, you spend the next two hours translating someone else's mess into something you can actually work in.
This is AAF prep & if you've been doing this long enough, you've stopped counting the hours.
The professionals who shaped fPost described the same experience across different facilities, different cities, different workflows. A studio in London got 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. A music editor at a small post company, ended up with hundreds of clips that they have to listen to, read, and manually sort. Her estimate for prep on even short content: two to three hours.
That time is invisible to clients. They don't see it. It falls entirely on the engineer before the first real decision gets made.
fPost exists to automate that work. This article explains what the prep problem actually involves, where the time goes, and how fPost's approach to AAF automation changes it.
Why AAF Prep Takes So Long
The AAF format is technically capable - it carries audio, video, metadata, timecode, volume automation, track names, and references to external media. In principle, it's a clean handoff to Pro Tools. In practice, a technically valid AAF and a session ready for mixing are not the same thing.
Here is what actually needs to happen between "AAF imported" and "session ready":
- Import the AAF. Pro Tools loads one AAF at a time. For commercial work with 10–15 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's on it. This comes after sorting, not before.
- Resolve stereo/mono. Stereo files exported from Adobe Premiere arrive as split mono pairs - Audio 1 (mono) alongside Audio 1.L / Audio 1.R on separate tracks. Detecting which are true stereo versus dual-mono, then converting and rebuilding stereo pairs, is a manual process many producers hit every single day.
- Apply your facility template. This is the hardest step. Your template is not just a starting point - it's the operating system of your facility. Every routing path, folder structure, color code, and I/O assignment has meaning. Importing a flat list of tracks from the AAF and mapping it to your template requires judgment about content type, not just execution.
- Verify routing. Every path, every send, every bus assignment.
- Preserve a safety copy. Every professional interviewed for fPost's development had one consistent request: keep an untouched original alongside the organized version. The question "what did editorial actually send?" needs to be answerable.
Across the professionals who informed fPost - London, New York, Los Angeles, Washington D.C. - the time cost of this process was consistent: typically two to three hours per session, with complex projects approaching half a day.
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 - resulting in combinations like Audio 1 (mono) and Audio 1.L / Audio 1.R for the stereo portions on the same named track.
The result in 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.
This affects a significant portion of the industry. Some producers hjandle it on nearly every job.
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 mix blind because the routing is always the same.
When an AAF arrives with flat, generically named tracks, rebuilding that structure takes judgment. You can't automate "move this clip to the DX track" without first knowing the clip contains dialogue. That classification problem is exactly where AAF prep costs the most time - and where manual scripting and DIY automation fail. As one engineer described it: "The verification cost of checking an automated tool's work can equal or exceed the cost of doing it manually."
Any tool that doesn't understand your template isn't solving the problem.
The Multi-AAF Problem
Commercial audio post often means many AAFs arriving simultaneously - some producers regularly receive 10-15 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 lengths: 60s, 30s, 15s, 6s.
Pro Tools loads one AAF at a time. The core issue for commercial work isn't just sorting - it's alignment. Each spot has to land at a precise position on the timeline, not just sequentially. That's a fundamentally different operation.
What "Session Ready" Actually Means
A session that's 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 is preserved and accessible
- Timecode and metadata are validated
Getting from "AAF imported" to this 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 by Forte AI approaches the problem differently from session management tools that parse tracks. Instead of reading track names and clip positions from the AAF file, fPost uses AI-R — Forte's proprietary content detection technology — to classify audio at the signal level.
AI-R listens to what's actually in each clip and identifies it across three categories: dialogue, music, and SFX. This classification happens before any reorganization - which means fPost doesn't need reliable track names or metadata to sort correctly.
Once content is classified, fPost applies mix template matching: it reads the facility template already open in Pro Tools and maps incoming clips to the appropriate tracks based on what they actually contain. Not based on what they're named. The template you've already built - with your routing, your folder structure, your I/O - is what fPost uses to place content.
The workflow:
- Open your Pro Tools template session
- Point fPost at the AAF
- fPost analyzes content, applies classification, and reorganizes the session.
- A safety copy of the original is automatically preserved alongside the organized version
- Import session data - timeline, automations, timecode - is retained throughout
- Template matching happens directly in pro tools.
For stereo handling: fPost detects dual-mono pairs and create an interleaved stereo from them.
The result is a session that meets the bar described above - content sorted at clip level, template applied, stereo resolved, original preserved - in minutes instead of hours.
What Carries Over - and What Doesn't Change
fPost keeps what matters: timeline position, timecode, automations, and the structure of your existing Pro Tools session. Your 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 is handling the administrative layer - the translation work between picture editorial's structure and audio post's structure - so that when you open the session, you are already at the starting line.
An independent post mixer who has been following the industry shift for years, describes the context clearly: "Post is moving away from big facilities toward freelancers and home studios - those are the people who need software support the most." For engineers working without assistants - one of our interviewees hasn't been able to hire one in three years - fPost takes over the work that would have fallen to an assistant.
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, 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. It works fully offline - no dongles, no cloud processing, no media leaving your workstation.
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's designed 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's ready for creative work. That gap - sorting clips by content type, applying your facility template, fixing split stereo, resolving track naming - costs 2–3 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 your template session in Pro Tools, point fPost at the AAF, and fPost handles the rest: AI-R content detection classifies each clip, mix template matching maps classified clips to the appropriate tracks in your template, stereo pairs are detected and converted, import session data (timecode, automations, timeline) is retained, and a safety copy of the original is automatically preserved.
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 my existing facility template?
fPost reads the template you have open in Pro Tools and uses it as the target structure. It doesn't impose its own routing or folder structure - it maps incoming content to your existing setup. Your template tracks stay intact; content is placed inside them.
What are the system requirements?
fPost requires macOS 13 or later and Pro Tools 2024.3. The DAW language setting must be English. It runs fully offline with no internet connection required.
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. Mixing, editing, and all creative decisions remain entirely with the engineer.
Try fPost
fPost is currently in beta. Demos are available on request at forte-ai.com/demo. If you're spending hours on AAF prep before every session, that's the problem fPost is built to solve.
.png)
