How to convert an AAF to FCPXML for Final Cut Pro.

Why Final Cut can’t just open the AAF

AAF is the interchange format of the Avid world — Media Composer, Pro Tools, Nuendo and DaVinci Resolve all read and write it. Final Cut Pro never adopted it: there is no AAF import, no AAF export, and no plug-in from Apple that adds one.

What Final Cut does read is its own XML. Two flavours exist: .fcpxml, a single file, and .fcpxmld, a bundle that Final Cut 10.6 introduced and that can carry collected media inside the package. AAF Everything writes both, so the conversion is AAF in, FCPXML out — no NLE in between.

AAF to FCPXML, step by step

1. Export the AAF from wherever the cut lives

   In DaVinci Resolve: the Deliver page with the Pro Tools preset, or File → Export → AAF. In Avid Media Composer: File → Output → Export to File → AAF. In Pro Tools: File → Export → Selected Tracks as New AAF/OMF. Embedded or referenced media both work.

2. Drop the AAF into AAF Everything

   Drop the file into the window or click Choose. You can queue several timelines at once — they all convert to the same target in one batch.

3. Pick .fcpxml or .fcpxmld and the frame rate

   Under Output, choose .fcpxml for a single file or .fcpxmld for the bundle. The frame rate you set becomes the timeline’s timecode — audio placement is computed in samples and stays exact at any rate, including 23.976 and 29.97 DF.

4. Decide what happens to the media

   Link to original media references the files where they are. Collect next to output copies every referenced file into one folder you can hand on as a whole. MXF-wrapped audio — what Resolve and Avid usually deliver — transcodes to WAV automatically, because Final Cut does not read MXF audio from an XML reliably.

5. Convert, then import in Final Cut

   Hit Convert. In Final Cut Pro: File → Import → XML. Next to the output sits a plain-text report naming everything that travelled and everything a format could not carry.

What travels into Final Cut — and what does not

• Audio placement — sample-accurate, independent of the frame rate.
• Crossfades — as Final Cut’s own overlapping audio blend, at full length and without a level dip. (A dissolve transition in Final Cut blends the picture, not the sound — the overlap is the audio crossfade.)
• Fades and clip gain — kept.
• Volume automation — written as real Final Cut volume keyframes, not flattened to an average.
• Markers and the picture tracks — kept, including several video layers.
• Surround / multichannel — kept.

What Final Cut has no field for: pan and clip colours. FCPXML simply has nowhere to put them, so they are dropped and the report says so. If you need pan automation to survive, AAF is the richer target — see FCPXML to AAF for the way back.

FAQ

Is .fcpxmld better than .fcpxml?

It is the same timeline in a different wrapper. .fcpxmld is a bundle (a folder macOS shows as one file) introduced with Final Cut 10.6; collected media can travel inside it. On 10.5 and older, use .fcpxml.

Can Final Cut Pro import AAF with a plug-in?

Not from Apple. Third-party tools exist that translate AAF into something Final Cut reads — which is exactly what this conversion does, only without a round trip through another editor.

What happens to MXF audio?

It transcodes to WAV automatically, including every stream of a multi-stream MXF. You can switch that off if your workflow reads MXF natively, but for Final Cut we recommend leaving it on.

Does the picture come across?

Yes, the video tracks travel with the cut, including several layers. If the sound you need is inside the video files rather than on separate audio tracks, switch on Extract video audio and the converter pulls it out into new audio tracks.

Related