nolanlabs

Blog · Delivery

OTIO, FCPXML, EDL or AAF: what survives the trip

· Updated · 5 min read

A red suitcase in the middle of a long, straight, narrow footbridge over a salt flat at dusk.

Short answer

Use FCPXML out of Final Cut, AAF into Avid or Pro Tools, FCP 7 XML or AAF from Premiere to Resolve, and an EDL when you need one track of cuts anyone can read. OTIO works well with Resolve; check Premiere's support on your version. None carry the full look, so test 30 seconds first.

On this page
  1. What each format carries
  2. Which should I use between which apps?
  3. Why can’t Premiere read FCPXML?
  4. Is OTIO ready to replace the others?
  5. How do you test a hand-off?
  6. What nolanlabs reads and writes

Pick the format the receiving app reads best, not the one with the longest feature list. All four describe an edit and point at media.

What each format carries

The EDL, FCPXML and AAF columns below come from the import chart in the DaVinci Resolve 21 manual (July 2026, chapter 22). So they say what reaches Resolve, which is a fair proxy and not a law: another app can read less. Resolve’s chart doesn’t cover OTIO, so that column uses Adobe’s and Blackmagic’s own descriptions.

OTIO FCPXML EDL (CMX 3600) AAF
Whose Academy Software Foundation Apple Decades old; CMX 3600 is the common form Open; AMWA publishes the specs
Media inside No. .otioz bundles it No No Audio can be embedded
Video tracks Many Many One per file Many
Dissolves Depends on the app Yes Yes Yes
Other transitions Depends on the app Ten types Become cross dissolves Nine types
Audio transitions Depends on the app No No Yes
Constant speed Yes Yes Yes Yes
Speed ramps Depends on the app Yes No Yes
Freeze frames Depends on the app No No Yes
Position, scale, rotation Depends on the app Yes No Through 3D Warp
Opacity Depends on the app Yes No Through 3D Warp or Superimpose
Grade Depends on the app As primaries No No
Titles Depends on the app Yes No No
Nested sequences Depends on the app Yes No No
Mixed frame rates Depends on the app Yes No Yes

The chart lists FCP 7 XML separately, and it matches FCPXML except that it brings no color.

Freeze frames and titles split FCPXML from AAF, which is a good reason to read the chart rather than assume the newer format wins.

Which should I use between which apps?

Start from what the receiver documents. As of November 2026:

From To Use Watch for
Final Cut Resolve FCPXML The only path that brings color, as primaries, and it doesn’t go back
Premiere Resolve FCP 7 XML or AAF Resolve asks for XML from a recent Premiere
Premiere Media Composer AAF Doesn’t relink by itself. Use Batch Import, and Adobe’s “Use tape sources” option
Premiere Pro Tools AAF Turn on Breakout to Mono. Separate Audio keeps more metadata
Media Composer Resolve AAF Effects Resolve can’t read go back in the AAF only if you don’t re-edit
Final Cut Premiere Convert first Premiere can’t read it, below
Premiere Final Cut FCP 7 XML, then a converter Adobe says only a few effects transfer, and audio levels may not transfer accurately
Anything Anything old, or a pull list EDL One EDL per video track, and turn on 32-character names in Premiere if clip names run long
Resolve Resolve, or an OTIO app OTIO .otio needs their copy of the media; .otioz is the whole set, and large

Resolve doubles as a translator. Its manual describes importing one format and exporting another, such as an EDL out as FCPXML or a Media Composer AAF out as an XML for Premiere. Effects can fall off at each step, so count it as a real trip.

Why can’t Premiere read FCPXML?

Because “Final Cut XML” names two formats. Premiere’s import list has “FCP XML”, and its export writes XML for Final Cut Pro 7. Modern Final Cut writes FCPXML, which Adobe calls “a .fcpxml file format that Premiere cannot directly import,” and its help sends you through the third-party XtoCC.

FCPXML also has versions. In Apple’s guide, Final Cut exports the current version or one of two earlier ones, and 1.10 or later writes a .fcpxmld bundle. If a third-party tool refuses the file, try an older version before anything else. Apple’s reference is also plain that FCPXML describes certain aspects of a project and doesn’t replace a library.

Is OTIO ready to replace the others?

For the cut, often. For a whole hand-off, not yet. OTIO’s README calls it an interchange format for editorial cut information and says it isn’t a media container. Resolve imports and exports it, and its manual says it travels between programs with more compatibility than AAF or XML.

Premiere is the one to test. Adobe’s community post, titled as released but describing the beta, lists names, the cut, source in and out, durations, start timecode, frame rate, tracks, constant speed and sequence markers, with clip markers kept on a Premiere round trip. Transitions and effects aren’t on that list. Adobe’s developer guide says Premiere Pro 25.6.0 or later supports OTIO, yet its export format list, updated in August 2026, doesn’t name it. Open your menu and see. The community wiki lists Media Composer as export only, in preview.

One trap if a script or tool does your conversion: OTIO’s other formats go through separate adapters, and each has its own limits. The AAF adapter reads constant speed but doesn’t write it. The FCPXML adapter lists no transitions or speed. The CMX 3600 adapter has one video track and constant speed only. Those are the adapters’ limits, not the formats’. An app’s own export may keep more.

How do you test a hand-off?

Before the real one, send 30 seconds containing one of everything you need: a dissolve, a constant speed change, a ramp, a title, a repositioned clip, a marker, and a clip at another frame rate. Then:

  1. Relink first. Every format here points at files, so a wrong path looks like a wrong edit.
  2. Compare start timecode and duration against the sequence you sent.
  3. Lay a rendered reference on the top track with a Difference blend and play it. A correct conform goes close to black. Anything else is a cut or a move that didn’t survive.
  4. Write down what’s missing, and rebuild it on one side only.

For speed changes in a pull, write the percentage in a note as well, and send the curve for ramps. An EDL can’t hold a ramp. Graphics with transparency go as their own files, so export the alpha before you hand off. Once the conform matches, run your delivery checks on the other side too.

What nolanlabs reads and writes

nolanlabs, the editor we make, reads and writes all four, and clips point at the original files with their own timecode. Each carries a different amount: OTIO and FCPXML keep cuts, tracks, sound, transforms, titles and markers; an EDL takes V1 or one chosen track with its sound; AAF is tracks, cuts and dissolves, for Avid and Pro Tools. Grades, masks, effects, compound clips and multicam come back exactly from an OTIO or FCPXML file nolanlabs wrote, but another app sees only what the format can show. Motion clips travel only in OTIO, and image sequence references in an OTIO file aren’t read. The details are on the hand-off page.

Blog

Keep reading.

Every piece

Written by the people who make nolanlabs, a video editor that edits with you.

Download for Mac Download for Windows Download

Free to start, on Mac and Windows.