What it does
Validation checks event ranges, whole-frame timing, equal source and record durations, reel names and timecode limits. Import checks syntax and DF labels. Export writes consistent event spacing, TITLE, FCM and a frame-rate comment, with no empty lines between entries.
When and why to use it
A list that looks readable may still contain an invalid frame number or an out-point before its in-point. Checking those conditions early helps isolate problems before the list reaches a scanner, grading system or another editing application.
A practical example
An event contains frame 25 in a 25 fps timecode. Valid frame labels run from 00 to 24, so the import is rejected with an explanation. A long reel name is reported for review because strict CMX readers may expect at most eight characters.
How to use it
- Confirm the imported frame rate and timecode mode.
- Open the validation report and review its findings.
- Correct timing or names with the relevant tools, then export the normalized EDL.
What to check before a handoff
Formatting repair does not infer missing edits, choose how to resolve overlaps or prove that the list matches picture. Unsupported XML or AAF structures are reported separately and block conversion. A successful report is not a substitute for a target-application conform 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.