OTIO-Sequencer Bridge

Module: Design · Category: Cinematic · Tool ID: OTIOSequencerBridge

Three-tab bridge between OpenTimelineIO (OTIO) — the industry-standard editorial timeline format — and UE Level Sequencer. Sequences scans LevelSequence assets with stats. OTIO Export/Import exports sequences to OTIO JSON or imports/parses OTIO files. Shot Breakdown analyzes camera cuts with a marketing render checklist.

Bridge open on Sequences tab with project sequences listed, summary stats per sequence visible.

When to use it

• Editorial round-trip: exporting UE sequences to Premiere/DaVinci/Avid via OTIO, then importing the editorial cut back
• Marketing render planning: shot breakdown with checklist (audio? long enough? camera assigned?)
• Cinematic auditing: getting a stat overview of all LevelSequence assets

What it isn’t for

• Don’t expect this to render via OTIO. It bridges editorial data, not pixel-level renders.
• Don’t expect this to author shots. That lives in Sequencer.

Opening the tool

1. Open the EQLabs Hub and search for OTIO or Sequencer Bridge (or browse to Design → Cinematic).
2. Click the tool card.
3. Use the tab bar: Sequences, OTIO Export/Import, Shot Breakdown.

Tab 1: Sequences

Scan LevelSequence assets with stats.

Section	What it does	Default
Scan Path	Folder to scan	/Game
Scan Sequences	Walks every ULevelSequence
Sequences list	Per-sequence row: name, duration (seconds), duration (frames), frame rate, track count, sub-sequence count, camera-cut count, bound actors

Single-click a sequence to select it (drives the Shot Breakdown tab).

Tab 2: OTIO Export/Import

Round-trip with editorial software.

Section	What it does
Export File Path	Output OTIO JSON path
Export OTIO	Exports the selected sequence to OTIO JSON
Import File Path	Input OTIO JSON path
Browse Import File	Pick an OTIO file
Import OTIO	Parses the file and lists the clips
Imported Clips list	Per-clip row: track name, clip name, kind (Video/Audio), start/end frames, matched UE asset path

The exporter writes a standards-conforming OTIO JSON. The importer parses OTIO JSON and tries to match each clip to a UE LevelSequence asset by name.

Imported OTIO file with 8 clips listed, "Matched Asset" column showing successful resolution to LevelSequence assets.

Tab 3: Shot Breakdown

Camera-cut analysis with marketing render checklist.

Section	What it does
Analyze Shots	Walks the selected sequence’s camera cuts
Shots list	Per-shot row: shot name, start/end frames, duration, camera name, focal length, issues
Marketing checklist	Per-shot checks: has audio, length >= minimum, camera assigned, total shot count adequate
Export CSV	Saves the breakdown

Workflow

Round-trip with editorial

1. Set Scan Path, click Scan Sequences.
2. Select a sequence.
3. Switch to OTIO Export/Import tab.
4. Click Export OTIO — JSON file written.
5. Hand to editorial; they edit; receive the result.
6. Click Browse Import File, pick the result, click Import OTIO.
7. Compare imported clips against current LevelSequence.

Marketing pre-render

1. Select a sequence on the Sequences tab.
2. Switch to Shot Breakdown.
3. Click Analyze Shots.
4. Walk the issues column for each shot.
5. Export CSV for the producer.

Settings reference

Field	What it does	Default
Scan Path	Folder for sequences scan	/Game
Export / Import file paths	OTIO JSON paths	(empty)

Settings file: [Project]/Saved/EQLabs/Settings/OTIOSequencerBridge.json

Output

• OTIO JSON file. Via Export OTIO.
• Imported clip list in-panel. Via Import OTIO (read-only display).
• CSV export. Shot Breakdown.
• No edits to LevelSequence assets. Read-only.

Tips and gotchas

• OTIO clip-to-asset matching is name-based. If your editorial software renames clips, matching breaks.
• Frame rates must align. Export OTIO at the project’s master frame rate to avoid drift.
• Marketing checklist is heuristic. Flags low-shot-count or missing audio; doesn’t guarantee shippable.

Related tools

• Sequencer Shot Validator — for asset-side LevelSequence validation
• Camera Sequencer Enhancement — author shots that consume this OTIO data