SMPTE's camera-metadata RDDs predate its new tracking protocol

The stage

SMPTE's own document library, as retrieved 16 September 2026, lists RDD 18, “Acquisition Metadata Sets for Video Camera Parameters,” and RDD 55, “Material Exchange Format — Carriage of ARRI Camera System Metadata,” among its registered disclosure documents. Separately, SMPTE runs an active On-Set Virtual Production (OSVP) initiative under its Rapid Industry Solutions program, whose own page describes the goal as building “a portfolio of essential tools” for the industry, including “knowledge resources,” without naming a specific RDD or recommended practice as its virtual-production metadata deliverable.

What the documents establish

RDD 18 and RDD 55 are general camera-acquisition and MXF-carriage metadata specifications; the document library's own titles do not describe either as written for virtual production specifically, so this entry does not claim that they were. SMPTE's standards overview page names newer active work areas, an AI in Media Task Force, a Sustainability Study Group, a Content Provenance and Authenticity Study Group, without listing a dedicated virtual-production metadata project by document number either. The three pages together establish that SMPTE's VP-specific effort currently lives in an open-ended initiative (OSVP) and a separately named newer protocol project, while its numbered camera-metadata carriage documents predate that initiative and were not written for it.

The department view

RDD 18 and RDD 55 matter most to a facility's pipeline engineer or data wrangler building the MXF ingest and archive layer that camera and lens metadata pass through in post, rather than to an on-set operator moving live tracking data to a render engine. That is a real division of labour the documents make visible: a legacy, file-based metadata-carriage specification serves a different stage of the pipeline than a live, on-set transport protocol, and a facility adopting one does not thereby adopt the other.

What to check before you build

Editorially: do not treat “SMPTE has a virtual-production metadata standard” as pointing to one document; ask a vendor which specific RDD or recommended practice, by number, its tool implements, rather than accepting an OSVP association as proof of compliance with a named specification. Because OSVP describes itself as an evolving portfolio, recheck its own page for a named deliverable before citing it as settled.

• Which specific RDD or recommended practice number does a vendor's metadata claim actually cite?
• Does the workflow in question need file-based MXF carriage (RDD 18/55) or a live on-set transport, and does the chosen document match?
• Has SMPTE's OSVP initiative since named a specific document as its virtual-production metadata deliverable?

SMPTE's own library shows camera-metadata documentation predating virtual production's current wave, doing real but general-purpose work, while its VP-specific effort remains a named initiative rather than a single settled standard.