24757 MXF White Paper v2

More documents

Recommendations

Info

Different types of file formats are used in today’sproduction environments. Each processing island adoptsa different format based on different operational policiesand technical requirements. There is, however, no standardfor file interchange among these processing islands.In order to implement file exchange, a neutral andadvanced format is necessary. This neutral characteristicdefines an intermediate common file format, which can beconverted to and from all the existing file formats with aminimum of computational efforts.This is one of the strengths of MXF and is shown inFig. 6. MXF can carry the equivalent informationcontained within an OMF, GXF or any other type offile format. At the same time, MXF is a subset ofAAF, for optimum interoperability with this powerfulauthoring file format. Therefore, the choice of MXF asan inter-island exchange format is a good choice, forit not only resolves today’s interoperability problemsbut also leads to the implementation of highly efficient,IT-based, production environments.Fig. 6 Inter-island format for various production formats
One of the typical models of IT-based production systemis shown in Fig. 7 below. All work servers are connectedvia an IT-based network (i.e. IP network). In addition, theingested materials are stored on near-line archives asMXF files, as well as shared with Production andOn-Air systems. These near-line MXF files will also bestored in long-term archive systems. The ingestedMXF files can then be transferred to the branches(affiliates) or other studios for re-purposing applications.In order to design this type of system, the key technologiesof MXF/AAF and meta-data are required as part of itsinfrastructure. The meta-data element UMID (UniqueMaterial IDentifier) is also essential to maximize therelationship (linkage) between the MXF/AAF file andmore extensive external meta-data. UMID specifies theidentification of each program material contained in thefiles, on a frame-by-frame or, scene-by-scene basis, or anyother form. UMID is just a pointer to link the packagedprogram segments to any associated external meta-data.Of course, MXF can carry rich meta-data, however, usershave valuable legacy meta-data in their own formats. ThisUMID linkage system supports the use of such externalmeta-data in conjunction with the ingested/archivedprogram materials.This meta-data friendliness is key for the migration toa future IT-based system.Fig. 7 Typical Model for IT based Platform
Page 2 and 3: This paper describes the implementa
Page 4 and 5: MXF has been defined as a flexible
Page 6 and 7: As said earlier, Pro-MPEG forum and
Page 10 and 11: MXF can contain meta-data in the he
Page 12 and 13: According to our model for an IT-ba
Page 14 and 15: The MXF format is defined as a wrap
Page 16 and 17: The EBU PITV group has started the
Page 18: Sony Electronics Inc.1 Sony DrivePa

24757 MXF White Paper v2

Create successful ePaper yourself

Delete template?

Save as template?