"No CMX-style EDL events were found" when converting an EDL
“No CMX-style EDL events were found.”
What is actually wrong
The converter reads CMX3600: numbered event lines with a reel, a track, a transition, and four timecodes. It found none. Either the file is not an EDL (an XML or AAF given the .edl extension), it is a different EDL dialect, or the text encoding hides the digits from the parser (Windows Notepad saving as UTF-16 is the classic case).
Fix it here: EDL to CSV
Drop the file. It is detected and converted in your browser; nothing is uploaded. Free to start, no signup.
Convert a file now
Conversions …
Drop EDL, SRT, VTT, .prtranscript, or transcript files
Any caption, transcript or timeline file: CutConvert picks the converter and shows what survives · up to 100 KB per file
The fix, step by step
Open the file in a text editor
A real CMX EDL starts with TITLE: and has lines like "001 A001C003 V C 01:00:10:00 01:00:14:12 00:00:00:00 00:00:04:12". If you see <xml or unreadable bytes, it is not an EDL.
Re-export as CMX3600
Premiere: File > Export > EDL, CMX3600 format. Resolve: right-click the timeline > Export > Timeline, EDL. Avid: List Tool, CMX3600.
Convert the EDL
Drop the file here. Every event becomes a CSV row with reel, track, transition, source in/out, record in/out and the clip name from the comment lines.
What an event line is
CMX3600 is a fixed-column text format from the days of linear tape editing. After a TITLE: line and an optional FCM: line (which tells you drop or non-drop frame), every edit is one event:
001 A001C003 V C 01:00:10:00 01:00:14:12 00:00:00:00 00:00:04:12
* FROM CLIP NAME: A001_C003_0512AB.movEvent number, reel, track (V, A, A2, AA), transition (C for cut, D for dissolve with a length, W for wipe), then source in, source out, record in, record out. The comment lines that follow carry the clip name and, from some applications, the source file path. The converter reads all of it and writes one row per event.
Why there may be no events
The file is not an EDL. Premiere’s export dialog sits next to "Final Cut Pro XML" and "AAF". An XML file starts with <?xml. An AAF is binary. Either one saved as .edl produces this message. Look at the first line.
It is a different dialect. Sony 9100, GVG and the older CMX 340 formats have different column layouts. Most applications default to CMX3600, and it is the one to choose; the others are rare enough that no modern importer expects them.
The encoding hides the text. An EDL opened and saved in Windows Notepad can come out as UTF-16, where every character is followed by a zero byte. A parser expecting ASCII sees no event lines. Re-save as UTF-8 or ANSI, or export again from the NLE.
Long clip names broke the columns. Some tools write reel names longer than the eight characters CMX allows, which pushes the timecodes out of position. The converter tolerates this, but an EDL with reel names containing spaces can still misalign. Premiere’s "Use source file name" option is the usual cause; turn it off and rely on the FROM CLIP NAME comment instead.
An empty timeline. A sequence with only nested sequences, or with tracks disabled in the export dialog, produces a header and nothing else.
Frame rate and the CSV
The EDL carries timecode, not milliseconds. The converter writes the timecodes as they are and, when you choose a frame rate on the page, also adds duration columns computed at that rate. Get the rate wrong and the durations are wrong; the timecodes themselves are untouched.
The EDL never leaves your browser.
FAQ
- Which EDL format should I export?
- CMX3600. It is the default in Premiere, Resolve and Avid, and the one every EDL reader expects.
- Can the converter read an EDL with transitions?
- Yes. Dissolves and wipes are written with their type and length, and a dissolve’s two source events are kept in order.
- Why are my clip names missing in the CSV?
- The names come from the FROM CLIP NAME comment lines. If the export omitted comments, or the file was cleaned of lines starting with *, there are no names to read.