The Four-Phase Pipeline at a Glance
fPost owns the entry. Matchbox and EdiLoad own the reconform. fMusic owns the export. No tool in the chain replaces another. The case for using each one is that it absorbs the work the next phase depends on, so the next phase starts on a clean input.
Why This Is a Pipeline, Not a Comparison
The post production tools community has a habit of framing every tool conversation as "X versus Y." That framing fails for fPost, Matchbox, EdiLoad, and fMusic because the tools do not solve overlapping problems. A re-recording mixer who uses Matchbox for reconform still needs something to build the session in the first place. A facility running fPost on every incoming AAF still needs Matchbox or EdiLoad when picture editorial sends a new cut. A session that has been built and reconformed correctly still needs fMusic (or a manual export pipeline) to print stems and masters.
The right frame is "and." fPost AND Matchbox. fPost AND EdiLoad. fPost AND fMusic. The pipeline runs end to end, and every tool in the chain depends on the tools upstream and downstream of it. The case for using fPost is not that it replaces Matchbox; it is that a session fPost has built is a better input to Matchbox than a manually prepped session, and a session that started clean delivers cleaner stems through fMusic at the end.
Phase 1: Session Build (fPost)
The pipeline begins when picture editorial delivers an AAF: a single file containing the audio clips for the cut, with timeline positions, basic naming, and sequence-level metadata. The audio post team has to turn that AAF into a Pro Tools session that is workable for creative editing, with content sorted to facility-template tracks, routing in place, and stereo and mono issues resolved.
This step has historically been manual and takes two to three hours per session, often longer for complex projects. It is the unpaid tax of audio post production: invisible to clients, falling on assistants and freelance mixers, and repeated on every AAF delivery (initial lock, conform AAFs, ADR pickups, final delivery).
fPost automates this step. AI-R content analysis classifies each incoming clip as dialogue, SFX, or music. The session is mapped to the facility's Pro Tools template: tracks named and routed correctly, color coding applied, folder structure in place. Import Session Data is preserved, including timecode, automations, and the timeline structure the conform process depends on. The untouched original AAF is saved alongside the organized session as a safety copy.
The output of Phase 1 is a Pro Tools session a dialogue editor or re-recording mixer can open and start working in immediately. The structural restart between picture editorial and audio post is absorbed; the within-dialogue assessment that requires listening (boom vs. lav, take selection, performance choices) stays with the editor and mixer.
Phase 2: Mixer Work (Pro Tools)
Phase 2 is the creative work itself: dialogue edit, sound design, Foley, ADR, music edit, and the mix passes. This is where the dialogue editor sorts clips at the region level, the sound designer builds effects, the Foley artist records and edits, and the re-recording mixer balances the final mix against picture.
This phase is owned by Pro Tools and the session built in Phase 1, supported by every plugin and tool the facility uses for restoration, design, and mix. The structural decisions made in Phase 1 (which tracks exist, how they are routed, which color belongs to which content type) shape every minute of Phase 2 work. The full sequence sits inside the audio post production workflow, where each role's specific work fits into the broader picture-to-final-mix arc.
Nothing automates this phase, and nothing should try to. Creative editing is the work the human is paid to do. What the upstream tooling does is reduce the time spent on the structural restart so that more of the schedule lands on the creative layer.
Phase 3: Reconform (Matchbox and EdiLoad)
Picture lock rarely holds. The director sees the cut and asks for two scenes to be tightened. Legal flags a frame. The agency note arrives overnight and the spot needs three new versions. Each change generates a conform: a new picture cut and (usually) a new AAF, against which the existing audio session has to be reconciled.
Matchbox (from The Cargo Cult) is a Pro Tools-integrated conforming tool. It takes the old picture cut and the new picture cut, computes the delta, and applies that delta to the existing Pro Tools session. Clips slide, automation slides, and unchanged regions stay in place. Pro Tools 2025.6 introduced Matchbox 2 integration with a Smart Conform workflow that operates clip by clip, which reduces the cases where a single edit boundary shifts an entire region the wrong way.
EdiLoad (from Sounds In Sync) is a broader-scope tool covering EDL compare, reconform, WAV assembly, scene remap, and WAV relink. It is rented per project at many facilities, used heavily during the conform-intensive phase of a project, and returned when the conform pressure ends. Mixers who use EdiLoad rely on it specifically for the reconform mechanic and for the WAV management that comes with episodic delivery cycles.
Both tools operate on existing Pro Tools sessions. Neither builds the session from the AAF in the first place. A clean reconform requires a clean original session, which is the contract between Phase 1 and Phase 3: fPost's output is the input that Matchbox or EdiLoad reconforms against. The cleaner the build, the smoother the conform.
Phase 4: Stem and Master Export (fMusic and the Delivery Pipeline)
After the mix is locked, the session has to print stems (DX, MX, FX, M&E, plus any project-specific splits) and the final masters in the destinations' channel layouts. Each file has to be named to the platform convention, measured for loudness, and verified against the destination's delivery specification.
fMusic automates the stem and bounce export step in Pro Tools and Logic Pro. Mix prep, routing, and stem export run as a defined operation rather than a manual print pass per stem. For projects with multi-version, multi-format delivery (5.1, 7.1, Atmos, near-field 2.0), the time savings on print scale linearly with the number of variants.
The full delivery process (loudness measurement, file naming, M&E QC, BWF metadata population) covers loudness compliance per ATSC A/85 or EBU R 128, stem split requirements per platform, and the M&E discipline that lets international localization teams dub the project without remixing. None of this is fully automated; the platform-specific specs require human verification. fMusic handles the print mechanic; the QC and naming pass is the mixer's responsibility.
Where the Pipeline Hands Off Between Tools
The friction in any multi-tool pipeline is at the handoffs. fPost to Pro Tools is a handoff. Pro Tools to Matchbox or EdiLoad is a handoff. The mixed session to fMusic is a handoff. Each one carries the metadata and structural choices made upstream into the next phase, and a missed setting at one handoff produces a problem two phases later.
Three handoff disciplines decide whether the pipeline flows or breaks:
Metadata completeness at Phase 1. A session built from an AAF with full clip-level metadata (source timecode, channel labels, scene and take where available) is a session that reconforms cleanly in Phase 3. fPost Suite flags clips with incomplete or anomalous metadata at the build step rather than letting them surface during conform. The reconform tool downstream depends on the metadata it receives.
Stable timeline structure through Phase 2. Edits made during creative work should reference timecode positions, not relative positions. This is what allows Matchbox or EdiLoad to compute a clean delta when a new cut arrives. Sessions where editors have used time compression or position-relative gain automation produce conforms that drift in unpredictable ways.
Routing in place from the start. Stems print cleanly when the routing they depend on was set in the facility template at Phase 1 and held through Phase 2. fMusic prints what the routing tells it to print; an ad-hoc routing decision made during the mix can produce a stem that is missing a sub-bus or duplicating a feed.
The AAF complete guide covers what the AAF actually carries from picture editorial into Phase 1, which is the input the entire pipeline depends on.
Frequently Asked Questions
Is fPost a competitor to Matchbox or EdiLoad?
No. fPost builds the Pro Tools session from the AAF that arrives from picture editorial; Matchbox and EdiLoad reconform existing sessions when picture changes arrive. They cover different phases of the pipeline. A facility using Matchbox or EdiLoad for reconform still needs something to build the session in the first place, which is what fPost does.
Can I use fPost alongside Matchbox?
Yes. fPost's output is a Pro Tools session organized to the facility template with full clip metadata preserved. That session is the input Matchbox reconforms against when picture changes arrive. The two tools operate at different points in the lifecycle and complement each other directly.
Does EdiLoad replace fPost?
No. EdiLoad does EDL compare, reconform, WAV assembly, scene remap, and WAV relink. None of those are the AAF-to-Pro-Tools session build step. EdiLoad operates on sessions that already exist, which is the output of the build phase that fPost handles.
What does fMusic do that Pro Tools doesn't already do?
Pro Tools handles single-stem bounce manually. fMusic automates the multi-stem, multi-session bounce process: mix prep, routing, and stem export run as a defined operation rather than a manual print pass per stem. For projects with multi-version delivery (5.1, 7.1, Atmos, near-field), the time savings scale with the number of variants.
Where does the pipeline start, and where does it end?
It starts when picture editorial delivers the first AAF and ends when the final stems and masters ship to the destination platform. fPost owns the entry (Phase 1), Pro Tools and the mixer's tools own the creative work (Phase 2), Matchbox or EdiLoad owns reconform (Phase 3), and fMusic owns the export print (Phase 4).
fPost automates AAF import and session organization for Pro Tools, including AI content classification at the dialogue, SFX, or music level, template routing, stereo and mono correction, and Import Session Data preservation. It is the Phase 1 tool in the audio post pipeline, designed to work alongside Matchbox, EdiLoad, fMusic, and every other tool that owns a different phase. Demo at forte-ai.com/demo.
.png)
