Choose for the information that must survive
An edit-list handoff must answer two questions: which source range is used, and where does it appear in the sequence? Tracks, effects, audio routing and media identities add more requirements. The right format is the one the receiving application can interpret while retaining the information this particular job needs.
Conversion is useful when formats differ, but adds another translation step. If the receiving editor already reads the original interchange correctly, importing it directly may retain more detail than reducing it to a simpler format first.
Practical format comparison
| Format | Typical role | In this toolbox |
|---|---|---|
| CMX EDL | Readable source/record cut list | Cleanup, timing and reel operations; limited audio representation. |
| FCP7 XML | Structured video/audio timeline exchange | Supported hard cuts, track positions, gaps and basic audio. |
| FCPXML | Final Cut Pro timeline interchange | Basic primary-storyline video cuts and gaps; audio mapping blocks export. |
| AAF | Structured composition and media references | Supported cuts/filler and frame-aligned mono audio; offline output. |
These limits describe EDL Toolbox, not everything the formats or native editing applications can represent. An advanced AAF or FCPXML may be valid while exceeding the subset supported here.
Example: two picture tracks and dialogue
Imagine an interview on V1, inserts on V3 and dialogue on A1. One flattened EDL cannot faithfully describe the full layered picture. XML → EDL therefore produces separate video lists with a track map, preserving the original positions. It does not decide which upper track is visible or bake a composite.
FCP7 XML can retain supported video and audio tracks in one sequence. An offline AAF can also represent supported cuts, but unsupported multichannel mapping or subframe audio must be addressed. Keep all required tracks selected and review the findings before choosing a format merely because its filename is accepted.
Interchange is not a rendered movie
EDL contains edit instructions, not picture or sound. Editing XML usually describes media references and sequence structure. AAF can carry richer structures and may contain embedded media, but this toolbox does not extract or embed media. Its AAF writer creates offline references for relinking.
Changing an XML filename to .mp4 or an EDL to .aaf is not conversion. Rendering creates media; interchange translation creates another description of the edit. A native Premiere project, Resolve project or Avid bin is also different from an exported interchange file.
Check the handoff in the receiving editor
- Agree on sequence start, exact frame rate and DF/NDF convention.
- Keep a reference movie with visible sequence timecode and the original export.
- Check first and last frames, gaps, every track and audio sync.
- Inspect transitions, speed effects, nests and unsupported findings before simplifying the source.
- Test relinking to representative media before processing the full sequence.
A successful download proves an output was generated, not that every receiving application will interpret it identically. Use the format reference and the conversion-specific guide for the current limits.