Start with an interchange export
An Avid bin or native project is different from an AAF or EDL export. For a handoff, agree which sequence, picture tracks and audio tracks the recipient needs. Keep the native project, a reference movie and the original interchange export together so a conversion can always be checked against the intended cut.
AAF is useful for structured sequence exchange; EDL is useful for a more limited event list. A conversion should solve a specific compatibility problem. If Resolve or Premiere can read the original AAF correctly, use that route before reducing the edit to a simpler representation.
Inspect an AAF before converting it
EDL Toolbox reads supported AAF structures locally in the browser. Choose the intended composition if more than one is present. Check its sequence start, source timecodes, track numbers and import findings. A recognized subset in the event table does not mean the entire AAF is exportable.
AAF → EDL creates separate lists for selected video tracks, with supported audio retained and a track map for a multitrack bundle. AAF → XML writes a supported FCP7 XML sequence. Neither operation extracts embedded media, translates every Avid effect or carries all native media identities.
Example: an insert track keeps its position
An AAF contains picture on V1 and inserts on V3, leaving V2 empty. Selecting V1 and V3 for EDL output produces two lists. An insert at Record In 01:03:10:00 remains at that position. The gap before it is part of the sequence, not empty space to remove automatically.
For XML output, V3 remains in the third track position. Check the reference movie to determine how the layers are meant to combine; separate lists do not describe every composite or effect.
Audio needs its own verification
Simple frame-aligned mono audio cuts are within the supported AAF subset. Multichannel source mappings, linked clip groups, effects, fades and edits between video frames can require information the converter does not preserve. Findings on selected tracks block export.
Excluding an affected audio track is appropriate only when the agreed handoff does not need it. It is not a repair of that track. For a full sound-post turnover, retain the native application’s audio export and the receiving department’s requirements.
Converting EDL or XML back to AAF
The toolbox can create an offline AAF from supported EDL or editing XML cuts. An EDL does not contain full source lengths, original codecs or media-management identities. Generated references therefore cannot promise automatic relinking to existing Avid-managed media.
Test a small representative sequence before adopting this route for a production. Check source ranges, timeline start, every selected track and media association in the destination. If the required relink metadata or effects are missing, return to the originating application instead of treating a successful file import as a complete conform.