What this CMX 3600 audit checks
The parser reads TITLE and FCM headers, standard event rows, common clip-name and source-file comments, and M2 motion-effect lines. It validates four timecode fields against the selected rate, checks cut and transition fields, calculates exclusive source and record durations, follows each track's record order, and distinguishes intentional duration-matched transition overlaps from unexplained gaps or overlaps. Unknown lines remain visible rather than disappearing silently.
Rate, FCM, and timecode counting
FCM: DROP FRAME or FCM: NON-DROP FRAME controls label counting; it does not identify 24, 25, 29.97, or another actual rate. Select the rate used when the EDL was exported. The audit accepts colon or semicolon frame separators because real exporters vary, then validates labels under the FCM/rate combination. For drop-frame rates, skipped minute-boundary labels are rejected.
Timeline continuity and transitions
Rows are compared only with the preceding valid row on the same track. A cut should normally begin at the prior record Out. A dissolve or wipe may begin earlier; when that overlap exactly matches the declared transition duration, it is labelled as an explained transition overlap. Program span uses valid video or combined rows when present, while the event record-time total sums every valid row and can therefore double-count simultaneous audio and video.
Conform boundary
A clean report does not guarantee that an EDL will conform correctly. CMX 3600 is deliberately limited and exporters use extensions. This tool cannot verify media existence, reel-to-file mapping, source frame rate, handles, field dominance, mixed-rate interpretation, audio samples, effects, color metadata, speed-ramp semantics, or application-specific import behavior. Compare against the locked reference picture and test the actual target application.
Frequently asked questions
Why must I choose a frame rate?
The classic FCM declaration says drop or non-drop, not the numeric rate. The same-looking timecode fields have different frame counts at 24, 25, or 30 fps, so the auditor does not guess.
Does it support Premiere, Resolve, and Avid variations?
It accepts variable-width numeric event numbers, reel names up to the whitespace boundary, common track tokens, standard cuts/dissolves/wipes, comments, and M2 lines. Vendor-only lines are reported as unknown instead of being treated as standard. Import behavior must still be checked in the destination system.
Does it repair or rewrite my EDL?
No. Automated normalization can remove extension data or change ambiguous intent. The page produces a read-only report and formula-safe CSV so corrections can be made in the source edit or a reviewed text copy.
Why can event record time exceed program span?
Event time sums all valid rows, including simultaneous audio and video tracks and transition overlaps. Program span measures the earliest to latest record boundary among video or combined events. They answer different questions.
Format references
Adobe documents CMX 3600 as its EDL export format and notes that EDLs work best for simple timelines with limited video and audio tracks. Blackmagic Design describes CMX 3600 as a basic interchange format carrying clip arrangement, names, transitions, and linear speed settings. See Adobe's current EDL export guide and the DaVinci Resolve reference manual.
Calculate SMPTE timecode · Plan video bitrate and storage · Browse video tools