Editorial Data Shouldn’t Need Manual Translation Every Time It Changes Hands

Modern productions cross several editorial applications and pipeline formats. One team sends an EDL. Another needs OpenTimelineIO. A third export arrives as FCPXML. Then somebody calculates timecode offsets by hand and introduces an error nobody catches for two days.

Why Three Formats Exist

CMX3600 EDL is the oldest and most widely accepted. It descends from tape-based linear editing, and its limitations reflect that: short reel names, minimal support for effects, and essentially no concept of nested structure. Its virtue is that everything reads it.

FCPXML carries far more of what an edit contains, including effects and structural detail, but it is tied to a specific application and its schema changes between versions.

OpenTimelineIO was created to solve exactly this: an interchange format designed to carry editorial intent between applications without each pair of tools needing its own bespoke translation.

In practice a production uses all three, because the client, the editor and the VFX vendor each standardised at different times.

Conversion Is Lossy in Directions People Forget

Converting toward a richer format is safe. Converting toward a simpler one discards information, and the discarded parts are not always obvious.

Flatten a nested sequence into an EDL and the nesting is gone. Retimes may survive as a speed value or may not survive at all. Effects typically vanish, leaving only the cut points.

This matters because the resulting file still looks correct. A VFX coordinator reading an EDL cannot see what was dropped on the way in.

Timecode Is Where Silent Errors Live

Timecode arithmetic looks trivial and is not, largely because of drop-frame.

At 29.97 frames per second, non-drop timecode counts frames accurately but drifts from wall-clock time. Drop-frame timecode skips certain frame numbers to stay aligned with real time — it drops numbers, never actual frames. Mixing the two, or assuming a sequence is one when it is the other, produces offsets that are small enough to survive review and large enough to matter.

Handle length compounds it. A shot delivered with the wrong handles is not visibly wrong until it reaches conform.

A Small Vendor Receives a New Cut

The client sends an updated editorial export. The supervisor needs to understand what changed before updating the tracker.

Rather than rebuilding the data by hand, the cut can be inspected and converted into whatever the next stage needs. That makes the tool a translation layer around editorial rather than another system to maintain — which is the right shape for a job that happens weekly and takes ten minutes when it goes well.

Local-First Matters Here

Editorial data is among the most confidential material on a production. An unreleased film’s cut structure reveals a great deal, and studios have specific contractual requirements about where such data may be processed.

A browser tool that works locally avoids uploading anything to a server, which is what makes it usable on shows where uploading would breach a security agreement.