ST 390:2011 - SMPTE Standard - Material Exchange Format (MXF) — Specialized Operational Pattern “OP-Atom” (Simplified Representation of a Single Item)

This standard defines the specialized Operational Pattern “OP-Atom” or OP-Atom for the storage and exchange of an MXF file with a tightly defined structure for a single item of essence described by a single Essence Track. It defines the operating restrictions, Structural Metadata objects and individual attributes applied to the MXF file format specification to achieve interoperability when exchanging a single item of audio-visual material. Operational Pattern “OP-Atom” is intended to satisfy the demands of applications where there is a requirement for exchange of material and associated metadata together in a single file with an open and standardized format, yet also a demand for a simple, predictable, layout with minimum scope for variation. OP-Atom is specifically intended for applications where each Essence Track is held separately. Operational Pattern “OP-Atom” provides for a subset of MXF features. The provisions of OP-Atom make it unsuitable for certain applications, in these cases a generalized Operational Pattern or a different specialized Operational Pattern is used. In all cases, the suitability of this pattern needs to be judged on a per-application basis. Some specific areas to consider are: OP-Atom is optimized for applications where the record (file creation) process is completed before a playout (file read) process is started. Therefore, it is unsuitable in applications where the record/playout (file creation/file reading) processes occur concurrently; This Operational Pattern places a full Index Table in the Footer Partition which, with VBR essence, makes it impossible to use as a streaming format where stream delivery requires advanced knowledge of frame boundaries. With VBR essence, it also requires the (possibly very large) Index Table to be stored separately until the file recording ends; Each OP-Atom file holds a single track of essence data therefore many applications will need an external mechanism to synchronize essence among multiple files. This standard does not define such a synchronization method; however, it does include an annex detailing a method of informatively recording synchronization among files created as a group.