Professional edit-list tools
for modern postproduction

Convert

Convert XML video and audio tracks to an AAF sequence

Create one offline AAF from selected XML video and supported audio tracks, retaining source ranges, record positions and sequence timecode.

Open XML → AAFAll guides

What it does

XML → AAF writes a real binary AAF in your browser. Selected video and supported mono audio tracks from FCP7 XML become one AAF composition; supported basic FCPXML primary-storyline cuts can also be converted. Source-media-relative in/out points, reel and clip names, available media paths, track numbers, gaps and the declared timeline duration are retained. Empty positions before V3 remain empty positions rather than renumbering V3 to V1.

When and why to use it

Use this when you receive an editing XML but the next editorial or conform step expects an AAF sequence. It creates an offline video handoff that can be relinked to the original media in the receiving application. The conversion does not render or upload footage.

A practical example

An XML has cuts on V1 and V3, starts at 01:00:00:00 and leaves a one-second gap before its first clip. Select both tracks to create one AAF with V1, an empty V2 and V3. A source in-point of 250 frames remains relative to that media file’s start timecode.

Choose a conversion for your input

The menu groups conversions by the open file’s format: EDL, XML or AAF. Only conversions from that format are enabled. FCP7 XML and FCPXML both use the XML group, with their individual support limits still checked at export. Gray options explain which input to open; guide pages remain available for every direction. Choosing an output or downloading a conversion does not replace the working document. Open the exported file to start working in its new format.

How to use it

  1. Open FCP7 XML or supported FCPXML, or choose the multitrack XML sample from the + menu. Then select XML → AAF under Convert · from XML.
  2. Select the video and audio tracks and name the output AAF. Review any missing-timing or unsupported-format findings.
  3. Choose Preview AAF to open the shared review and inspect its export plan. Approve & export generates the binary locally; a conversion error leaves pending edits unapproved.
  4. Download the AAF, import it into the receiving application, relink media and compare the sequence with reference picture.

What to check before a handoff

This initial writer supports hard cuts and filler at one supported rate, with matching source/sequence DF modes and progressive square-pixel video references. Frame-aligned mono audio hard cuts are supported. Multichannel source mapping, linked clip groups, fades, audio effects, subframe edits, transitions, speed effects, grading and nested edits block AAF export. FCPXML audio mapping is not yet supported; audio detection blocks conversion unless explicitly excluded. FCP7 XML must declare sequence and source timecodes. FCPXML omitted starts follow its zero-start defaults. Missing media durations use the declared source out-point and produce a warning. AAF contains generic offline video descriptors with XML dimensions when available, otherwise 1920 × 1080; it does not reproduce original codecs, embedded media, native project metadata or existing Avid media identities. Manual relinking may be necessary. Up to 64 video track positions and 5,000 cuts. Full-frame 59.94/60 timecode and receiving-NLE compatibility need testing on a representative project. Synthetic binary and WebAssembly tests do not replace that receiving-application check.

Reference & format notes

These guides describe the current EDL Toolbox behavior. For XML format details, see Apple’s FCP7 XML reference and FCPXML documentation. Test the exported list against representative media in your receiving application.