Editorial workflow guide
How to Detect Scene Cuts and Generate an EDL from a Reference Video
Turn a flattened reference movie into a reviewed CMX3600 cut list for conform, comparison, source matching, or finishing.
Reference video → CutDetect review → CMX3600 EDL
When all you have is a flattened reference
A flattened reference contains the finished sequence but none of the original edit decisions or source clip names. Detecting its scene changes creates a cut list that can act as a map for conform, comparison, version review, or source matching; reconnecting those events to source media requires a separate source-matching workflow.
This is especially useful when a client sends only a review export, when an online editor needs to notch a flattened sequence, or when a finishing team must compare a new delivery against an earlier version. The goal is not to recover every original source relationship; it is to recover the timing and order of the visible cuts.
Use a constant-frame-rate reference with known frame rate and source timecode. Clean hard cuts are the easiest transitions to detect reliably.
How CutDetect speeds up the workflow
CutDetect handles the first detection pass and keeps transition review, manual correction, and EDL export together in one local Mac application. It removes much of the repetitive cut-finding work while leaving editorial decisions with the operator.

Before you begin
- Confirm the reference frame rate and whether its timecode is drop-frame or non-drop-frame.
- Use the highest-quality reference available; heavy compression can soften or distort edit boundaries.
- Decide whether dissolves and fades need manual edit points in the final cut list.
Step-by-step workflow
1. Open the reference in CutDetect
Load the reference and check the first frame, embedded timecode, duration, and playback behavior. If the movie has variable frame rate, transcode it before creating frame-accurate editorial data. The timebase you establish here must match the application that will receive the EDL.
2. Run automatic scene-cut detection
Use CutDetect to analyze the reference for sudden visual changes. Begin with a balanced detection threshold rather than trying to capture every possible transition in one pass. A slightly conservative result is usually faster to refine than a timeline filled with flash-frame false positives.
3. Review the detected-cut timeline
Move through the result with Previous Cut and Next Cut navigation. Pause on dense montage sections, whip pans, camera flashes, and low-contrast edits. Use frame stepping to establish the first frame of the incoming shot rather than relying only on playback.
4. Correct the cut list
Use Add Cut when a true transition was missed and Remove Cut when a flash, strobe, or abrupt exposure change was identified as an edit. Review the opening and closing sections separately because fades and slates may require manual decisions.
5. Export the CMX3600 EDL
Export the reviewed events from CutDetect using the reference movie’s timecode basis. Give the file a descriptive name that includes the reference version and frame rate, then reopen it before handoff to confirm the file is valid.
6. Verify the EDL downstream
Import the EDL into the NLE, conform application, or source-matching workflow. Confirm that its event range covers the intended duration, then compare the first event, final event, and several cuts distributed across the running time. If events gradually drift, stop and resolve the frame-rate interpretation before continuing.
CutDetectScene-cut detection, review, and CMX3600 EDL export for Mac.