metarex.media uses MXF and OpenTimelineIO to preserve the original format of metadata for live, downstream & archival use.
What is it?
A project to create a body of free to use Open Source software that allows media metadata to be created, transmitted and stored over common links and file systems.
Why do I want it?
Because today, every Virtual Set and engineering heavy production is a custom build. Every QC report is unlinked to the master content and version workflows lose metadata when content is processed by third parties.
What is it good for? Carrying binary, text, isochronous and event driven metadata. Identifying the metadata via a registry and providing links to applications and schemas that can shed light on how to process that metadata. By harmonising the identification and transport of the metadata, an infrastructure can be built to keep the stuff that we currently lose.
What is it not good for? We will not harmonize schemas for tripod data, lens data, QC data or any other sort of metadata carried. That’s outside the scope. MetaRex will carry any metadata through the value chain to where it’s needed. MetaRex will identify that metadata and allow applications to enlighten the metadata or rmove it based on business rules.
What is it not yet good for?: At the end of 2022 MetaRex is just a paper specification, some pictures and a prototype register. At the end of 2023 we should have code for different computer languages and a framework for common tools and apps. By the end of 2024 we should have end to end workflows with common tools and a body of free software that reduces the barrier to transporting and preserving media chain metadata.
Where should I go next?
- Project : How is the project run
- Technology : How does it all work?
Was this page helpful?