Edit Decision Workbench
Plan a non-destructive single-video-track edit from multiple source reels. Enter available source ranges and each cut’s source and record addresses. The workbench computes record out-points, makes gaps explicit, checks overlap, and exports a cut-only CMX 3600 EDL, native OpenTimelineIO .otio, and editable project JSON. Only this documented one-track subset can be imported.
Key features
- Author up to 80 ordered cut decisions against 40 named source reels
- Use exact integer-frame arithmetic at 24, 25 or 30 fps non-drop timecode
- Calculate source and record out-points from half-open frame spans
- Show intentional record gaps as numbered BL black-video events
- Reject overlapping record edits, out-of-range source cuts and missing reel references
- Export and reopen constrained CMX 3600 EDL, native OpenTimelineIO .otio, and editable project JSON
How to use
- Choose 24, 25 or 30 fps non-drop and enter an ASCII project title and first record address.
- List each source reel, clip name and available source in/out addresses.
- Add cuts in order with source in/out and desired record in. Leave room between record in-points for black gaps.
- Inspect the exact frame timeline and resolve any overlap, missing source or day-boundary error.
- Download EDL, .otio, or project JSON. Select the matching fps before EDL import; .otio carries its own integer rate.
Use cases
- Hand off a basic cut list from two camera reels to another editor
- Document a sequence with intentional black between shots
- Check source handles and record overlaps before conforming media
- Save an editable JSON draft and exchange a one-track OTIO or restricted legacy EDL
Frequently asked questions
Does this tool edit or render my videos?
No. It builds edit decisions and exchange text. It does not inspect media, verify reel-to-file relinking, change frames, mix audio or render a final video.
Which EDL features are supported?
Only a single video track with straight cuts and BL black gaps at 24, 25 or 30 fps non-drop. Dissolves, audio channels, speed changes, nested timelines, drop-frame, mixed source rates and arbitrary vendor extensions are rejected or unavailable.
Are in/out addresses inclusive?
No. Source out and record out are the first frames after the edit. A source in of 00:00:01:00 and out of 00:00:02:00 at 24 fps spans exactly 24 frames.
What happens when record addresses overlap or leave a gap?
An overlap blocks output. A positive gap becomes an explicit BL event. Reorder can create an overlap until you adjust record-in addresses or use Ripple record addresses, which closes all gaps.
Can I import an existing EDL?
The importer accepts the strict cut-only layout emitted here, not arbitrary CMX variants. EDL has no reliable embedded frame-rate declaration, so select its 24/25/30 fps mode first. Importing EDL reconstructs source bounds from the used cuts; project JSON preserves the full catalog.
Will an EDL import into every editor?
No. CMX 3600 has application-specific style variations and reel-linking rules. Check reel IDs, frame rate, source media timecodes and import settings in the target editor. Use this file as an editorial plan, not a verified conform.
What OpenTimelineIO files can I exchange?
Native .otio JSON uses Timeline.1, one Video Track.1, Clip.2 (legacy Clip.1 on import), Gap.1, MissingReference.1, and integer 24/25/30 fps time ranges. It carries no actual media URL. Other tracks, transitions, effects, audio, linked media URLs, fractional or mixed frame rates, and unsupported metadata are rejected rather than silently flattened.
Privacy
Clip names, addresses and project files remain in this browser page. Nothing is uploaded, stored or sent to analytics; downloads are generated locally.
Comments & questions