fPost has had one job since day one: take the AAF that arrives from picture editorial and hand back a Pro Tools session that is ready to mix. The Studio tier does that for one AAF, one session, and three content categories. fPost Suite, the new tier built for busy rooms and small facilities, is what happens when the same engine is pointed at the way post teams actually receive work: several AAFs per turnover, sessions that need to be split across editors, and rooms that need to know more about a clip than which of three buckets it landed in.
Here is what Suite adds, in the order it appears in a real turnover.
Import multiple AAFs into one session
The Studio workflow starts with one AAF. Suite's import screen accepts several at once: select the files, and each one appears in an ordered list you can rearrange manually or by timecode, with the frame rate of every AAF displayed alongside. When the AAFs arrive at different frame rates, which happens the moment two reels or two episodes come from different editorial setups, fPost flags the mismatch and aligns the imports automatically instead of leaving you to discover it on the timeline.
Two import modes decide what the combined session looks like:
- Preserved. Each AAF keeps its own block of tracks. Reel one lands as its own group, reel two below it, every source intact and separately addressable. This is the mode for turnovers where the reels stay distinct through the mix.
- Consolidated. Clips from all AAFs are packed into the fewest shared tracks possible. This is the mode for rooms that want one lean session rather than parallel track blocks.
Before anything is built, the processing step shows each AAF's sample rate and bit depth, flags anything that needs attention, and notes details a mixer would want to catch early, like an AAF whose timecode starts at zero when the industry convention is a one-hour start. What an AAF carries in general, and why the import is only the first half of the prep, is covered in our AAF guide for audio post.
Subcategories: beyond dialogue, music, and effects
fPost Studio classifies every clip into three macro categories, dialogue, music, and sound effects, using AI-R, the on-device engine that reads what a clip actually contains rather than trusting the track name the editor left on it. Suite keeps the same engine and goes a level deeper.
Dialogue breaks out into subcategories such as sync dialogue, studio speech, crowd walla, non-verbal vocalizations, and singing or vocal performance, each with its own selectable color so the session stays readable at a glance and matches the way your room works. Music distinguishes instrumental, music with vocals, electronic and synthesized material, and music stems or partial mixes. Sound effects split into ambience, hard effects, designed effects, whooshes, impacts, risers, drones, and UI beeps and tones. Every subcategory can be mapped to its own template track, and stereo interleaved handling can be enabled per category.
For a sound editor, that difference is not cosmetic. A session where crowd walla is already separated from sync dialogue, and risers from ambience, is a session where the edit starts at the edit rather than at another sorting pass.
Per-clip metadata, on demand
Suite adds a clip inspector: double-click any clip and fPost shows the original AAF name, the original track name from editorial, the channel format, mono or stereo, stated plainly rather than guessed from the file, and the category and subcategory AI-R assigned. When a clip lands somewhere unexpected, the inspector is the audit trail: you can see what arrived, what it was called upstream, and why it was placed where it was. It is the metadata forensics fPost already runs during import, surfaced per clip instead of buried in a log.
One AAF in, as many sessions as the room needs
The last Suite addition changes what comes out the other end. Studio builds one organized session. Suite's PTX Splitter offers the shapes post teams actually work in: build everything into one new session, import into the current session, start from your template, or split by category, which produces separate Pro Tools sessions with all the dialogue in one, all the music in the second, and all the effects in the third. The category split is not locked to three sessions either: categories can be grouped, so a room can keep, say, music and effects together in one session and send dialogue to its own.
That last option is the one dialogue editors and facilities asked for, because it maps to how scripted work is actually divided: the dialogue editor, the music editor, and the effects editor each open a session containing only their material, already named, colored, and routed to the template. The room's template mapping works the same way it does in Studio: fPost duplicates the template tracks as needed, moves every clip into place, checks that every file link resolves, and leaves the original AAF and media untouched, so a re-run is always safe.
Studio and Suite, side by side
| fPost Studio | fPost Suite | |
|---|---|---|
| AAF import and session prep | Yes | Yes |
| PTX session reorganization | Yes | Yes |
| Template matching and naming | Yes | Yes |
| Content recognition | Macro categories: dialogue, music, effects | Subcategories within each |
| AAFs per import | One | Multiple, preserved or consolidated |
| Split one AAF across sessions | No | Yes, including by category |
| Clip metadata | Session level | Per clip, on demand |
| Support | Standard, 48h | Priority, 24h |
| Offline | Add-on available | Included |
| Price | EUR 399/year, 1 seat | EUR 599/year, 1 seat |
Both tiers run entirely on-device: nothing is uploaded, classification happens locally, and the app needs a connection only at sign-in, which is what makes it usable in rooms handling embargoed material under NDA. Both require Pro Tools 2024.3 or later on macOS 13 or later, and both start with a 7-day free trial with no credit card. Facilities that need floating licenses, a license server, and an SLA sit above Suite in the Enterprise tier.
Suite is available from Monday, July 27, 2026. As a launch offer, until September 15, 2026 it sells at the Studio price of EUR 399 a year instead of EUR 599.
Where Suite fits
If you are an independent editor mixing one turnover at a time, Studio already covers the job, and the step-by-step of that workflow is in our guide to automating AAF prep with fPost. Suite earns its place the day the work stops arriving as one AAF: multi-reel features, episodic series where reels and versions stack up, and rooms where the session has to leave the import split across the people who will work on it. The tier decision on the Avid side, which Pro Tools can open the handoff at all, is a separate question, and it is covered in our Pro Tools tier comparison for audio post.
Frequently Asked Questions
What does fPost Suite add over Studio?
Four things: importing multiple AAFs into one session with preserved or consolidated track modes, the PTX Splitter for dividing one AAF across separate Pro Tools sessions by category or grouped categories, per-clip metadata inspection, and subcategory recognition beyond the three macro categories. Suite also includes offline use and 24-hour priority support.
Can fPost import multiple AAFs into one Pro Tools session?
With Suite, yes. Select several AAFs, order them manually or by timecode, and choose preserved mode, where each AAF keeps its own track block, or consolidated mode, where clips are packed into the fewest shared tracks. Frame rate mismatches between AAFs are detected and aligned during import.
Can fPost split an AAF into separate dialogue, music, and effects sessions?
Yes, with Suite. The PTX Splitter can build one session with everything, import into the current session, start from a template, or create separate sessions by category, so each editor opens only their material, already organized to the template. Categories can also be grouped on the way out, for example music and effects in one session and dialogue in another.
What are subcategories in fPost Suite?
Studio classifies clips as dialogue, music, or sound effects. Suite classifies within those: sync dialogue, studio speech, crowd walla, and vocal performances within dialogue; instrumental, vocal, electronic, and stem material within music; ambience, hard effects, designed effects, whooshes, impacts, risers, drones, and UI sounds within effects. Classification runs on-device with AI-R, based on the audio content rather than track names.
What does fPost Suite cost and what does it require?
Suite is EUR 599 a year for one seat, with offline use included and priority support. It is available from July 27, 2026, and until September 15, 2026 it sells at the Studio price of EUR 399 a year as a launch offer. It requires Pro Tools 2024.3 or later and macOS 13 or later, runs on Apple Silicon and Intel, and starts with a 7-day free trial with no credit card.
