What this OTIO auditor checks
The bounded JSON parser expects a native OpenTimelineIO Timeline with its canonical tracks Stack. It inventories top-level tracks, nested compositions, clips, gaps, transitions, effects, markers, metadata keys, serialized schema identities, rational times, source and available ranges, active media-reference keys, and known media-reference families. Exact findings explain invalid rates and durations, missing relationships, unsupported schema versions, source ranges outside declared media availability, and selected-folder path mismatches.
Media portability with explicit evidence
External references are classified as relative, absolute, remote, unsafe parent-relative, or unsupported studio-specific URLs. A selected folder lets the tool distinguish an exact relative-path match from a case-only match, a basename candidate, ambiguity, or absence. With no selection, local existence remains unverified. Remote URLs are never fetched, absolute paths remain nonportable even if a similarly named file is selected, and recognized query secrets or URL credentials are redacted.
How the timeline comparison works
Tracks and child objects receive deterministic identities from their nested parent, OTIO type, name, and same-name occurrence. This keeps named clips comparable across ordinary insertions and reports additions, removals, and field-level timing, media, enabled-state, effect, marker, and metadata changes separately. Repeated unnamed objects or renames can appear as removal plus addition; that is disclosed instead of guessed.
Validation and timing boundary
This tool does not execute the OpenTimelineIO library and is not an official conformance test. It does not load AAF, FCP XML, EDL, OTIOZ, OTIOD, or plugin adapters; resolve studio media linkers or custom schemas; reproduce every OTIO range, transform, transition, stack, or effect operation; decode media; render a sequence; verify codecs, frames, or remote availability; rewrite timelines; or guarantee interchange with an editor. Use the current OTIO library and every target application for critical delivery validation.
Frequently asked questions
Why is the displayed timeline span called an estimate?
The browser computes sequential track positions from supported source and available ranges while treating transitions as overlays. Nested stacks, time effects, and application-specific metadata can change evaluated timing, so the official library remains authoritative.
Does selecting a folder upload the media?
No. The browser receives a local file list for path comparison. The auditor does not read media bytes or send names, paths, or timeline content to ToolQuill.
Can this compare an OTIO export with an EDL or XML?
No. Both inputs must be native OTIO JSON. Convert other formats using a trusted, version-matched OpenTimelineIO adapter first, then compare the resulting OTIO files.
Primary references
The OpenTimelineIO documentation describes the interchange model. The official tutorials document the canonical Timeline / Stack / Track structure, serialized schema objects, and time-range semantics.
Validate a CMX 3600 EDL · Calculate timecode · Audit a REAPER project · Browse video tools