Skip to content

Final Cut Pro → Pro Tools

Final Cut Pro to Pro Tools

Pro Tools has read AAF for twenty years and does not read FCPXML. fcp2aaf writes the AAF: your roles become tracks, your clips land where they fell, and the audio is cut from your own recordings with handles.

macOS 14 or later · Apple Silicon

Final Cut Pro exports FCPXML. Pro Tools imports AAF. Neither one speaks the other's language, and Final Cut has no AAF export to bridge the gap.

fcp2aaf reads the FCPXML, conforms the audio, and writes an AAF that Pro Tools opens with File ▸ Import ▸ Session Data. The mixer gets a session, not a stack of files to place by hand.

Three steps, all on your Mac

In Final Cut Pro, select the project and choose File ▸ Export XML. Drop that file on fcp2aaf. Choose fades, handles, timecode and which tracks travel, then convert.

You get the AAF, its audio, and a report of what travelled and what did not. Nothing is uploaded — the conversion runs on your own machine, reading your own disk.

Every role becomes a Pro Tools track

Final Cut has roles and lanes; Pro Tools needs one clip at a time on a track. fcp2aaf resolves them: overlaps within a role spill onto extra tracks, roles stay contiguous, and two clips joined by a crossfade stay together. A stereo pair opens as two slots, A1.L over A1.R.

You see the session drawn before it exists — every track, every clip where it will fall — and you set the order, the names and which tracks stay behind. You can click any clip and hear it first.

Fades Pro Tools turns into real clip fades

By default fcp2aaf writes fades as dissolves, which is the one form Pro Tools imports as a draggable clip fade. A curved handle — easeIn, easeInOut — arrives as a straight fade, because that is what Pro Tools accepts as a real fade, and the report counts how many had a shape so the curve is one dialog away.

You can also write fades as volume automation, or not at all, or as native AAF properties that Pro Tools ignores. Split edits, J-cuts and L-cuts arrive laid exactly where the sound played.

Markers land in Memory Locations

Final Cut's markers arrive as locators. The three kinds each have their own switch, so a mixer can take the notes and leave the chapter marks. The kind is written into the marker's own name — [TODO], [DONE], [CHAPTER] — because Pro Tools reads one marker ruler and nothing else about a marker's kind.

Source timecode, so Spot to Original works

The timecode the recorder stamped travels inside the AAF, whether the audio is embedded or beside it, and every channel of a recording points at the same origin. That is what Pro Tools matches on to spot a clip back to where it was recorded and to pull in the other microphones of a take.

What an AAF cannot carry into Pro Tools

Some of these are worth knowing before you go looking for a switch. Each was established by writing an AAF and opening it in Pro Tools — they are limits of the format as Pro Tools implements it, not things fcp2aaf leaves out.

  • Track and clip colour. An AAF carries none; Pro Tools colours each track on import. Its own AAF exports carry none either.
  • The shape of a curved fade. It arrives straight, which is what Pro Tools accepts as a draggable fade. The report counts them.
  • Pan on a track grouped in stereo. Pro Tools does not read it there. One channel per track — the default — keeps pan.
  • A muted clip. AAF has no mute a session reads back, so silenced material arrives with its clip gain at −∞: whole, inaudible, one gesture from being heard.
  • Final Cut's audio effects. An EQ or a compressor added in Final Cut is a Final Cut plugin. The audio arrives as recorded, at its clip gain.

What the mixer opens

A session, not a bin
Roles resolved into tracks, every clip placed to the sample, crossfades and split edits intact.
The sound work in place
Clip gain, volume automation, pan, fades as draggable clip fades, and markers as Memory Locations.
Media with room to work
Conformed from your originals with the handles you set, embedded or referenced, at the session rate.

Questions about Pro Tools

Can Final Cut Pro export AAF for Pro Tools?

No. Final Cut exports FCPXML only. fcp2aaf reads the FCPXML and writes the AAF that Pro Tools imports as Session Data.

Which version of Pro Tools?

Any version that imports AAF, which is every version for the last two decades. The default output is standard AAF, so nothing here depends on a recent build.

Embedded or referenced media for Pro Tools?

Either. An embedded AAF is one file to hand over. A referenced delivery is a folder with the AAF and its WAVs, lighter to write, and it can carry 32-bit float. Both import the same way.

Do multitrack field recorders and multicam come across?

Yes. A multitrack rush opens as a block of tracks, one microphone each, named after the subrole. Multicam and sync clips deliver every angle you switched on for audio, not just the active one.

What is the Audio Channel Combiner?

An optional setting that groups a clip's channels into a stereo track. It is not in the AAF standard and it costs correct pan reading in Pro Tools, so it is off by default. One channel per track is the standard, portable output.

Not using Pro Tools?

The same AAF opens in these too. Each page covers what to expect.

Ready to hand the cut over to the mix?

Up to 5 minutes is free, for everybody, with every feature switched on. No card, no account, and nothing to cancel.