← Part of: the AAF Everything guide
Final Cut ⇄ Media Composer

Final Cut Pro to Avid Media Composer — and back.

AAF is Avid’s own format. Final Cut writes FCPXML and nothing else — the conversion sits between them, in both directions.

Short answer: In Final Cut Pro, open Window ▸ Extensions ▸ AAF Everything and send the timeline straight to AAF. Or export File → Export XML from Final Cut Pro and convert it to .aaf; an Avid AAF coming the other way converts to .fcpxml or the .fcpxmld bundle.

The reference implementation

AAF came out of the Avid world, and Media Composer reads and writes it as a native interchange format. Final Cut Pro writes FCPXML and has no AAF import or export, so the conversion sits between them in both directions.

Avid expects OP-Atom MXF and particular descriptor details, which is why MXF-wrapped media is best left untouched on this route — Media Composer reads it natively.

Final Cut to Media Composer, step by step

The direct way: in Final Cut Pro open Window ▸ Extensions ▸ AAF Everything, choose AAF and export. The workflow extension writes the AAF from the current timeline. It is the same conversion as the app, without exporting XML by hand. The steps below take the route through the app.
  1. Export the XML from Final Cut Pro

    File → Export XML. A single .fcpxml or the .fcpxmld bundle — drop either one in.

  2. Convert to .aaf

    Drop the file in and pick .aaf. If your Avid workflow wants channels split, the Separate combined channels option writes one mono file per channel while the tracks stay stereo.

  3. Collect the media

    Collect next to output gives one movable folder. MXF audio can stay untouched (reference as-is) — Avid reads MXF natively, so the originals can stay as they are.

  4. Coming back: an Avid AAF into Final Cut

    File → Output → Export to File → AAF in Media Composer, then convert to .fcpxml or the .fcpxmld bundle. Leave the MXF transcode on for this leg — Final Cut does not read MXF audio from an XML reliably. See AAF back into Final Cut.

Speed changes and video dissolves: audio speed changes are rendered only when Separate combined channels is on. Without it, the AAF points to your original recordings and the report lists every retimed clip with its position, so you can rebuild the speed in Media Composer. With it on, the audio of constant speed changes is rendered at the speed Final Cut plays it; speed ramps never are. A video cross dissolve is not carried, and picture after it can slip by the length of the dissolve: render or consolidate it in Final Cut before you export.

What travels — and what does not

Pan comes along as track pan when every clip on a track has the same value in Final Cut. Where the values differ, nothing is averaged and the report names the track. On the way back into Final Cut, no pan is written. Track and clip colours ride in a private AAF comment that only this converter reads back. Exact track names give way to Final Cut roles on the return leg, and empty tracks are not representable in FCPXML.

FAQ

Should MXF audio be transcoded for Avid?

No. Media Composer reads MXF natively, so reference as-is leaves your originals alone.

What about markers?

They are written into the AAF as named markers.

Can I go Avid to Premiere instead?

Yes — an Avid AAF converts to Premiere XML as well. Premiere cannot read third-party AAFs reliably, which is exactly why that route exists.

Try it on your own timeline first.

The demo is the complete app with unlimited conversions — each output covers the first 120 seconds with the full track layout. If your file converts the way you need, buy a license.

Download the free demo Buy — $79