Hand off capture with a media and metadata matrix

Media without context is only part of the handoff

Editorial, VFX, color, and conform need different things, but they share one requirement: a later user must be able to identify what a file is, where it belongs, and what happened on set. “Send all metadata” is not a deliverable. It obscures the real questions: which identifiers are authoritative, what is camera-originated versus stage-originated, what is a reference only, and what has to travel with the camera media on day one?

SMPTE RDD 58:2021 describes a data structure and carriage for live-production metadata. It is a Registered Disclosure Document, not a SMPTE standard or a complete virtual-production handoff specification. Its relevance here is narrower: structured metadata needs an explicit format and transport, not merely a claim that it exists somewhere in a control system.

Define deliverables by consumer

Create a matrix that names the item, owner, destination, identifier, timing, and verification method. The matrix should distinguish original camera media from proxies, sound reports, camera reports, lens data, timecode records, slate/take mapping, tracking data, stage or scene revision, playback/render reference, color/calibration artefacts, and stills or recorded references. Do not assume every recipient needs every file; do assume each critical file needs a durable link to the take or shot.

Mark reference material honestly

Netflix’s OpenVPCal documentation says its calibration can export an OpenColorIO configuration and/or a display-to-display 3D LUT, and it distinguishes camera, target, screen, and reference color spaces. That supports a useful handoff discipline: name what a color file represents and its intended scope. Do not label a viewing LUT, a wall correction, and a final grading transform as interchangeable. The same discipline applies to monitor captures and reference movies: useful for identifying a stage look, not automatically authoritative final color.

Atlas proposed package layout

Deliver a readme first, then immutable media manifests, then per-shot folders or database links. The readme identifies the show, shoot date, timebase, naming rule, folder map, contacts/roles, and known exceptions. A single exceptions log can be more valuable than a polished directory tree: missing lens data, restarted timecode, a fallback playback state, a replaced card, or a tracking gap should be discoverable without detective work.

Illustrative: take C003_014 has original media, a proxy, a camera report, a tracking export, a reference movie, and a state record pointing to environment revision E12 and playback revision P07. The editor may use the proxy; VFX may use the original and tracking; color may consult the camera report and calibration package. All three can find the same take because the identifiers agree.

• Write an item-by-item matrix with owner, destination, identifier, timing, and verification.
• Separate originals, references, transforms, and calibration artifacts.
• Attach stage/content revision to each relevant shot or take.
• Publish exceptions in the handoff rather than relying on memory or chat history.