AS-02-10-2011-11-18 MXF Versioning

AMWA Specification AMWA Application Specification AS-02 MXF Versioning
November 18, 2011 (version 1.0) Executive summary
New routes to market for entertainment media are resulting in an explosion of new devices and channels that enable consumers to watch their favorite content. For the content owners and distributors, this is a doubleedged sword. • • On the one hand, the overall market for content is increasing. On the other hand, the number of eyeball-contact minutes for any given distribution channel is decreasing.

This motivates content owners to search for more efficient ways of creating the media required for different distribution channels. One common way of looking at the world is to consider the media factory shown in figure 1.

english spanish description Dolby E french

Media Factory
STREAM

Figure 1: Media factory The media factory accepts its input in the form of tapes and files. Its role is to deliver the revenue generating deliverables to the downstream services and devices. The media factory may be a business in its own right, or it may be a function within a larger facility. As facilities migrate to file-based working from tape-based working, the media factory concept is appearing in organizations around the world. To make this media factory efficient and measurable is a business decision, ensuring that costs and efficiencies can be calculated.

Copyright © 2011 AMWA NOTES – The user’s attention is called to the possibility that implementation and compliance with this specification may require use of subject matter covered by patent rights. By publication of this specification, no position is taken with respect to the existence or validity of any claim or of any patent rights in connection therewith. The AMWA, including the AMWA Board of Directors, shall not be responsible for identifying patents for which a license may be required by an AMWA specification or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention.

AS-02-10-2011-11-18 MXF Versioning

Today, many media organizations do not keep the kind of Key Performance Indicators (KPIs) that would be traditionally employed if the factory were making mechanical widgets. There have been a number of revolutions in the overall design of mechanical factories in recent years that we can use to help our overall design of a media factory. "Lean Manufacturing", "Kanban" scheduling and "Total Quality Management" are all hot topics in factory design. There is no universal right answer to the way in which a factory should be built, but all of these mechanisms are aimed at the one central goal: • Reduce waste.

In order to achieve this, it is important to know what waste in a media factory actually is. The list can be quite long, but the high-level view includes: • • • • • • • • Moving media that does not need to be moved; Keeping media that does not need to be kept; Copying media that does not need to be copied; Processing media that does not need to be processed; Taking too long to process media that could be processed more quickly; Deleting data or metadata that needs to be recreated in a later process; Re-keying data or metadata that was previously known; Making a tape from a file that was previously a tape.

In general, waste in a media factory is the same as waste in any other factory. In achieving the result that the business needs, materials, time and/or resources are used unnecessarily. The MXF file format was designed to associate metadata and media so that factories could be created that were much more efficient than tape-based factories. It seems, however, that these factories have not magically appeared because of a large number of factors that need to be considered when migrating from a tape-based world to a file-based world. The MXF file format was developed to provide a wrapper agnostic to the number of audio channels. or the compression format, or the resolution of the video. It was developed to provide a metadata-rich way of performing business processes on an asset whilst leaving the fine detail to the underlying machines that manipulate the pixels. To allow a step change in waste reduction to be realized, the AS-02 application specification defines an efficient way of using MXF within the media factory. This is also a step change in cost-efficiency of handling media. A key factor in this cost-efficiency is that AS-02 is an application specification for MXF users to build workflows. Its design is oriented towards low-cost, high-efficiency media factories rather than towards any one vendor’s view of the world. The underlying design brings the best from the MXF media world and the best from the IT world to allow standards-based workflows to be created without requiring expensive customization. AS-02 can be considered as a set of constraints on the SMPTE-MXF toolbox. It is not a new MXF standard. It is a way of making the best use of the tools that exist. MXF was standardized in 2004 by the SMPTE. Since then, a large number of products, services and tools have been created that use MXF. The product types are split into three broad categories: 1. 2. 3. OP1a interleaved devices and tools – largely operating on files as if they were tapes; Atoms / referenced file devices – largely operating on source elements; Generic toolkits, SDK and transcoding tools – gluing the world together.

Neither the OP1a nor the atom way of using MXF is currently optimized for building a good factory.

Published specification - Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.doc Version 1.0, Nov-18-2011

Page 2 of 43

AS-02-10-2011-11-18 MXF Versioning Factories based on interleaved OP1a make the world look as much like a tape as possible to ease the migration from tape to file. This is a good thing because it introduces basic file-based working and the associated quickwin benefits. These benefits include faster than real time transfers and aggregation of large volumes of content onto single server, realizing genuine savings. These savings allow the concept of a media factory to be created in an otherwise tape-based world. The OP1a format has one major design principle – interleave the video and audio so that you always have the data for one frame of video close to the data for the synchronized sound. This is great for an acquisition device like a camera or for a playback device - like a single channel playout server - for which AS-03 is a good fit. However, this can lead to serious waste for media factory operations. For example, if you need to create a stereo audio from the surround sound audio track, why should you have to transfer the video at the same time? 90% of the data transferred is not touched. This is waste. The OP-Atom format (SMPTE 390M-2004), as used in Avid environments and Panasonic P2 cameras, was optimized for storing individual essence components in editing environments. The actual essence storage is almost perfect for a factory environment. The problem comes with the way in which the individual components are synchronized: • • OP-Atom synchronizes the components within each OP-Atom file, allowing for only one version; The dCinema community makes use of an XML structure for the same role.

The goal of the AS-02 work was to create a factory format that supports multiple versions and with no reinvention, making use of metadata-only MXF (SMPTE 377-1-2009) to provide component synchronization. With as few constraints as possible, we had to use the tools in MXF as they were written and implemented. One lesson learned in lean manufacturing is that if you get it right, it should feel like the design is just on the edge, where on the edge means: • • You could write some more specification, but it wouldn't be widely used; If you deleted any of the specification, you would lose many of the benefits.

MXF is only a file format. It is a tool that allows you to build a better media factory. Like all tools, it can be used well and it can be misused. The AS-02 application specification contains many - but not all - of the rules that you need to build a media factory. It only contains the rules that relate to the file format. Other rules are required to put the system together, such as those to do with communication between AS-02 processes and AS-02 services. An interface specification that creates a common dialog for interoperable services between media factories is a likely topic for a future AMWA specification. When a media asset is used within a media factory, there are several ways in which it can be used: • • • • • • • The unique identifier of the asset. Sometimes a filename, a house number or an UMID. The standardized metadata of the asset. Sometimes a database record, a MXF header or a QT header. The custom metadata of the asset. Often an XML file that may be lost when the asset is exchanged. A component of the asset. The video data or the data in one of the audio tracks. A simple version of the asset. The English soundtrack Internet version or the HD version. A complex version of the asset. Edited for family or aircraft viewing. A group of versions of the asset. All the mobile phone versions or the region 1 DVD versions.

Note how we are using the word asset and not the word file. You will see this is important when we come to talk about real implementations later. Also note that most of the uses of the term asset refer to anything from abstract metadata to several physical files. Most asset management systems have developed ways to handle

Published specification - Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.doc Version 1.0, Nov-18-2011

Page 3 of 43

AS-02-10-2011-11-18 MXF Versioning this complexity inside their databases. Prior to AS-02, no one had yet standardized the factory format that allows any two vendors to build products to that specification and have their equipment work out-of-the-box. AS-02 is a stable, specified way of using MXF that leads to efficient media factory design. It was originally designed by a group of ten companies to meet the needs of a single user who had a vision of an ultra-efficient media factory and has now been deployed in several facilities around the world. The uses of a media file given above were considered and application rules were written that allow devices to use MXF (was SMPTE 377M2004, now updated to SMPTE 377-1-2009) to achieve all of the use cases.

Contents
Executive summary .................................................................................................................. 1   Contents ................................................................................................................................. 4   1   Scope ............................................................................................................................... 6   2   Conformance language ....................................................................................................... 6   3   Reference documents ......................................................................................................... 7   4   Overview ........................................................................................................................... 7   4.1   File format requirements (informative) ......................................................................... 7   4.2   General AS-02 and shims ............................................................................................ 8   4.3   Asset structure, versions and bundles .......................................................................... 8   4.3.1   Introduction to the structure (informative) ............................................................ 8   4.3.2   MXF and non-MXF operations (informative) ........................................................ 10   4.3.3   AS-02 asset structure ........................................................................................ 11   4.3.4   Essence component file ..................................................................................... 11   4.3.5   Version file ....................................................................................................... 11   4.3.6   Simple version file ............................................................................................. 12   4.3.7   Bundle ............................................................................................................. 12   4.3.8   Simple bundle................................................................................................... 13   4.3.9   Extra folder ...................................................................................................... 13   4.3.10   Extra folder – role of a file ............................................................................... 13   4.3.11   Manifest file .................................................................................................... 14   4.3.12   Shim file ......................................................................................................... 14   5   Version file parameters and constraints ............................................................................. 14   5.1   Provision categorization ............................................................................................ 14   5.2   No essence in the version file .................................................................................... 14   5.3   Partitions carrying header metadata in the version file ................................................ 14   5.4   MXF header constraints in a version file ..................................................................... 14   5.5   MXF header constraints in a simple version file ........................................................... 15   5.6   Closed and complete metadata in the version file footer partition ................................. 16   5.7   No essence stream index tables in a version file ......................................................... 16   5.8   Version file KAG size of 1 .......................................................................................... 16   5.9   Minimum simple version duration .............................................................................. 16   5.10   Media integrity check for essence components .......................................................... 16   5.11   Channel mapping with track numbers ....................................................................... 16   5.12   Timecode ................................................................................................................ 17   5.13   Descriptive metadata parameters and constraints ...................................................... 17   5.13.1   SOM/EOM....................................................................................................... 17   5.13.2   Other descriptive metadata schemes ................................................................ 17   6   Essence component file parameters and constraints ........................................................... 17   6.1   Essence track parameters and constraints .................................................................. 17   6.1.1   General ............................................................................................................ 17   6.1.2   Mono essence................................................................................................... 17   6.1.3   Interleaving ...................................................................................................... 18   6.1.4   Partitions ......................................................................................................... 18  

Published specification - Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.doc Version 1.0, Nov-18-2011

Page 4 of 43

.............................................. 34   9............................................................................................. 27   8...........................1........................................................... 23   6.....................doc Version 1..3...........2.....4   Application specification element (optional) ....................................... 38   10..... 38   10....................................................................................................... 28   8..................................... 32   9...................1   Shim name element ......................................................................................................................1............................................................ 31   9...4   Sample manifest file (informative) .........................................................5   Index tables ............................ 22   6..1   Manifest structure ..1   Shim structure .................. 20   6........................................................................ 23   6...............................1   Shim identifier ...........................................................................6   Video .......... 30   9   Manifest file format ....1   Baseline operational pattern ..................................................1   DMS-AS compliance ID ..............................................................................................................................................3   Size element.......................... 34   9..........................................................2..............................................................................................2..................................................7   Other VANC / VBI components ...... 30   9..................1............................ 38   10..............................1................................9   Other VBI and ANC data ...............................1......................................................6   Annotation text element (optional) ......compliance ID ............................ 36   10   Shim file format ...... 25   7........................................................................... 35   9..2.......2.........................................2   File element ..................................... 22   6.................................................................................................................................1   File identifier element ........0.......................4   Path element ................................................................................... 38   10... 26   7............................................................2............................................................2   Role element .............................................5   Sound components ........................ 19   6............................................................................................1...........6   KAG size ........................3   XML schema for manifests ......................................................................................................... 38   10...................................................................6   File list element .......................................................1..................................... 33   9........................8   Closed captioning and subtitles ............................................7   Audio .............1.................2...................... 30   8...................................5   Annotation text element (optional) ..2................................................................3   Header metadata parameters and constraints ..............................................2   Legacy shim identification ......................................................................................1...... 32   9............... 22   6...................................................4   Creation date element ...........................2........ 19   6................................ 22   6.................................................... 23   6.................2.1   Legacy bundles .............................. 26   8   Generic shim ........................................2.........................................................................................2   Bundle identifier element ....................................2   Shim identifier element....................................... 30   8.........................................................................1   Bundle name element ........................................................3   System item ...............................................8   Version files .....................................5   Random index pack .................... 35   9.......................................................................................3   Creator element .................... 22   6.....................2   Header metadata and operational pattern constraints .............................. 28   8...........................1............1..............3   General essence ..........AS-02-10-2011-11-18 MXF Versioning 6....2....................................................2   XML schema for shims ................... 31   9............1.............. 39   10...............2   Essence container label ..............................2   Shim .... 21   6................................... Nov-18-2011 Page 5 of 43 .............3   Annotation text element (optional) ....... 32   9...........9   Header metadata .....................Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning....................11   Descriptive metadata ..............................................................................................................10   Bundle . 28   8.... 34   9....................2........................... 31   9............1........................................... 18   6..... 29   8................................. 27   8...4   Picture components ....................................... 25   7   Legacy bundles ................ 32   9.........................................6   Caption components ............. 31   9...................................... 27   8.............................................................. 27   8..................................................................................1............................................................................................................ 34   9........ 39   Published specification ......1   Package labeling .....................4   Timecode .......................... 25   7.............5   Media integrity check element (optional) ............ 29   8...................................................................................................................................................1....................................................................

..........   Registered manifest file roles (normative) .................... all recommended provisions ("should") as described.... 2 Conformance language Normative text is text that describes elements of the design that are indispensable or contains the conformance language keywords: "shall"................................. The design of AS-02 recognizes that individual facilities are likely to have some variations... This has the goal that manufacturers can build MXF-compliant equipment......... The keyword “reserved” indicates a provision that is not defined at this time... or "may"...3   Version files ...........................5   Bundle ...... among several possibilities.... Informative text does not contain any conformance keywords............. Informative text is text that is potentially helpful to the user. A conformant implementation need not implement optional provisions ("may") and need not implement them as described........ one is recommended as particularly suitable...... 41   A. and may be defined in the future..Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning...3   Sample XML shim file (informative) ........ the physical layout rules of AS-02 may be relaxed.. or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited...........1   Essence component files ....... This allows the end user to build a customized workflow by configuring a piece of generic software / equipment and yet retain the interoperability that comes with a constrained open standard...... shall not be used.......... conforming to the AS-02 specification..... or that a certain course of action is preferred but not necessarily required........g........ by default.... variation is expected in the specific metadata rules and audio channel arrangements...............2   Simple version files .......... For that reason........ 42   A............. the AS-02 specification includes a shim specification that takes the rules of AS-02 and further constrains them for use in a facility...... The keyword “forbidden” indicates “reserved” and in addition indicates that the provision will never be defined in the future... The specification provides a lean and efficient approach to working with file-based media that is intended to reduce waste as part media facility operations....AS-02-10-2011-11-18 MXF Versioning 10........   AS-02 sample shim document (informative) . 40   A.......... The rules shall not be relaxed for business-to-business interchange.............. if implemented... "should" and "should not" indicate that............. The keywords "may" and "need not" indicate courses of action permissible within the limits of the document......... but not indispensable......4   Metadata in MXF-AS-02 ............. 40   A........... 42   Annex B............................. changed... 39   Annex A.... AS-02 provides constraints on the structure and use of standardized MXF files to provide new opportunities for interoperability both within and between media facilities... Also........................ specifically in the types of codecs and essence that are allowed............................................. Nov-18-2011 Page 6 of 43 ................. e...................... "should".................... 43   1 Scope AMWA’s application specification AS-02 defines the building blocks of interoperable media factories................................... Published specification .....doc Version 1.. The keywords. A conformant implementation according to this document is one that includes all mandatory provisions ("shall") and............................... 41   A....... normative.............. by avoiding unnecessary copy operations or the re-keying of metadata. except: the Introduction......................................... or added editorially without affecting interoperability.. Rather than specifying a new file format.......................... and can be removed................ without mentioning or excluding others... and they know that properties subject to shim specification need to be exposed to the end user... any section explicitly labeled as "informative" or individual paragraphs that start with "Note:” The keywords "shall" and "shall not" indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted........ Note: In a managed AS-02 environment within a single facility................ All text in this document is.0............... the media facilities where the versioning of assets takes place..

1 File format requirements (informative) AS-02 addresses the problem of having a common file format in a facility that has to handle many input formats and make many output formats. a facility operates with a constant pressure to reduce the cost of production. The compression format of today gets replaced with a better one from tomorrow.0. and then any other language forms. the order of precedence of the types of normative information in this document shall be as follows: Normative prose shall be the authoritative definition.AS-02-10-2011-11-18 MXF Versioning Unless otherwise specified. followed by formal languages.Generic Stream Partition 436-2006 Television – MXF Mappings for VBI Lines and Ancillary Data Packets 2029-2009 Uniform Resource Names for SMPTE Resources Extensible Markup Language (XML) 1. requirements for a facility change. In order to build systems that work at the MXF level rather than at the MPEG. distribution and publishing. At the time of publication.doc Version 1.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. Tables shall be next. the editions indicated were valid.0 (Fifth Edition) Namespaces in XML 1. In parallel. SMPTE SMPTE SMPTE SMPTE SMPTE SMPTE SMPTE SMPTE SMPTE SMPTE SMPTE SMPTE SMPTE W3C W3C W3C W3C W3C IETF IETF IETF IETF IETF 330M-2004 Television – Unique Material Identifier (UMID) 377-1-2009 Material Exchange Format (MXF) – File Format Specification 378M-2004 Television – Material Exchange Format (MXF) – Operational Pattern 1a 379-1-2009 Material Exchange Format (MXF) – MXF Generic Container 380M-2004 Television – Material Exchange Format (MXF) – Descriptive Metadata Scheme-1 381M-2005 Television – Material Exchange Format (MXF) – Mapping MPEG Streams into the MXF Generic Container 382M-2007 Material Exchange Format . This Published specification . then figures. over time. Nov-18-2011 Page 7 of 43 . The facility that started as SD introduces HD. through reference in this text. 3 Reference documents The following standards contain provisions that. and parties to agreements based on this recommended practice are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. Today’s stereo audio gets upgraded to multi-channel and multi-lingual. constitute provisions of this recommended practice. JPEG2000 or DV level. In an ideal world. All standards are subject to revision.Mapping AES3 and Broadcast Wave Audio into the MXF Generic Container 391M-2004 Television – Material Exchange Format (MXF) – Operational Pattern 1b 393M-2004 Television – Material Exchange Format (MXF) – Operational Pattern 2b 407M-2006 Television – MXF – Operational Patterns 3a and 3b 410-2008 Material Exchange Format . a single essence representation would be standardized on.0 (Third Edition) XML Schema Part 0: Primer (Second Edition) XML Schema Part 1: Structures (Second Edition) XML Schema Part 2: Datatypes (Second Edition) RFC RFC RFC RFC RFC 1321 1738 2104 3174 4122 The MD5 Message Digest Algorithm Uniform Resource Locators (URL) HMAC: Keyed-Hashing for Message Authentication US Secure Hash Algorithm 1 (SHA1) A UUID URN Namespace 4 Overview 4. Unfortunately. AS-02 is an application specification providing a set of rules that MXF encoders and MXF decoders must follow.

human or system. catch servers. Thus. A single essence component file will exist for each video. A version file in MXF format represents individual versions. It allows a device to query the image size without having to implement a decoder for each essence type – you simply read the MXF.0. They shall be limitations on the general provisions.1 Introduction to the structure (informative) MXF AS-02 is a component-based format.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. that apply to defined applications. 4. the general provisions may be non-restrictive in some areas and this is intentional.doc Version 1.3 Asset structure. this specification is divided into general provisions that apply to all applications and specific constraint sets. The general structure of an AS-02 bundle is shown in figure 2 below. It allows a business process to be specified with an action such as: If (16:9) then transcode(centre-cut-out) This action can be specified without the executor of process.3. Customized metadata and application specific files may be stored within the folder structure in defined locations. General provisions shall apply to all AS-02 files and thus represent the maximum required capability of ingest servers. needing to know the details of underlying codec type – that is something for the transcoder to figure out. Nov-18-2011 Page 8 of 43 . this allows business systems to deliver work order requests to content-manipulation devices. In general. Each of these shims tightly defines the codecs and layout for the particular business application. In this specification. Each shim shall provide a further set of constraints that reduce the range of variability that may be needed in well-defined categories of applications. transcoders and other AS-02 compliant devices. playout servers. In any given facility design or interchange specification based on AS-02. audio and data element. The group of files is referred to as a bundle. shim parameters shall be highlighted as follows: Shim parameter example Definition Semantic definition of the example shim parameter 4. For example. Published specification . Interleaving components together (as in SMPTE 386M D-10) is not allowed. which are in turn configured to support delivery specifications. there may be one or more tightly defined shims. or they may address requirements of particular broadcast station groups. The general structure of an AS-02 asset is folder-based. Shims shall not be used to add new required capability to the general provisions. versions and bundles 4. these categories may address particular type of programming or programming genres. a shim for HD content and a shim for web content.AS-02-10-2011-11-18 MXF Versioning brings many advantages.2 General AS-02 and shims To maximize commonality across applications. Typical examples are to have a shim for SD content. called shims.

Nov-18-2011 Page 9 of 43 .mxf asset_a0. as shown in figure 3.xml shim.mxf manifest. asset asset.mxf extra Media is forward referenced from the version file .xml version file media asset_v0.mxf asset_vanc0.mxf asset_a3. reference to the asset is by its root folder. Figure 3: Media folder contains MXF essence Published specification .xml media extra Figure 2: AS-02 file structure – a bundle In IT file-based operations.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.xml shim.mxf manifest. A media file is referred to as an Essence Component file.doc Version 1.0. Within that folder will exist one or more version files that reference media stored in the media subfolder.AS-02-10-2011-11-18 MXF Versioning asset asset.

doc amwa. An MXF operation is one that involves parsing the MXF metadata. checksum bundle. but may be further restricted within a shim.AS-02-10-2011-11-18 MXF Versioning Extra metadata and content that is not MXF-wrapped is stored in the extra folder. Published specification . An example of a typical extra folder is shown in figure 4. The first of these is the manifest (section 9) that lists all the files in the bundles. extract simple version etc. The second of these is the shim (section 10) that provides an identifier for the shim that was used at the time the bundle was created or last modified. add track. All MXF operations shall result in files that comply with the MXF suite of specifications.xml shim.2 MXF and non-MXF operations (informative) AS-02 shall permit both MXF operations and non-MXF operations.tv qc-vendor. The root folder contains two XML documents that are used to manage the asset. transfer bundle (FTP). A non-MXF operation is one that does not involve parsing the MXF metadata.mxf manifest. purge extra files.0.com wss2016. package bundle (zip). seek. add extra file.com Extras link to the mxf version or media files using non-MXF (possibly proprietary) mechanisms Figure 4: Extra folder contains non-MXF metadata and content 4.xml show_format.. Examples of non-MXF operations include: move bundle. Nov-18-2011 Page 10 of 43 . update manifest.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. Examples of MXF operations include: play. asset asset. jog. remove version and essence. find unreferenced essence components. remove track.xml version file media extra media-owner. create version.3.doc Version 1. record. You can see in the figure that any customized metadata type is permitted within AS-02.

it shall be stored in a version file that has the same filename as the root folder and shall have a “. 4.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. each of which is fully explained in section 5.mxf". the name of the root folder shall be used as the file-system name of the AS-02 bundle (see section 4. it is not necessary to parse every essence component file in the bundle first. 5. 3.5 Version file A version file shall contain only a single MXF material package and shall have the following properties. An essence component file shall be regularly partitioned when frame wrapped. 2. In addition to the essence component files. An essence component file shall have distributed and complete index tables. Published specification .doc Version 1. An essence component file shall be clip wrapped for PCM audio. The folder structure shall be referred to as an AS-02 bundle. For example: "media/a03. As a result. OP2b or OP3b. index tables or essence. 4.mxf” extension.3. a decoder can locate a matching media MXF file for a specific component. 9. A version file shall be a valid MXF file with external essence: OP1b. 1. An essence component file should not have a system item. Systems may use this property to construct Uniform Resource Locators (URLs. 8. In a file system. An essence component file shall be a mono essence MXF file. 12. Note: By using the top-level file package identifier as both the primary package identifier and external identifier of an essence component file (as used in the manifest file). AS-02 version files reference the file package UMIDs of the essence components. An individual version of an AS-02 asset shall have the primary package property set to the UMID of the material package in the version file. the "BundleID" field of the manifest file shall indicate the identity of the bundle. 4. 1.4 Essence component file An essence component file shall be a media file in the media folder with the following properties that are further described in section 5. 6. AS-02 assets include metadata that describe different versions of the asset. 11.AS-02-10-2011-11-18 MXF Versioning 4.3. If an “original” version.3. An essence component file shall have a KAG size of 1. AS-02 version files shall not reference essence components outside of the bundle. a filename specified as the pathname of the file relative to the root of the essence component file within a bundle shall be used as a substitute for the UMID. An essence component file shall have the primary package set to the identity of the top-level file package within the essence component file.6). 10. 4. Each body partition in an essence component file shall have metadata. Each version shall be described in a separate version file. 2. An essence component file shall be signaled as closed and complete in the header or footer partition. The UMID of the top-level file package in the essence component file shall be the unique identifier of the essence component. RFC 1738) from the file system pathname of the bundle.3. 3. 5. An essence component file shall be signaled as OP1a. For non-MXF operations. “primary” version or “default” version exists. 6. Nov-18-2011 Page 11 of 43 . An essence component file shall be frame wrapped for video and SMPTE 436M essence. Note: No path component is required as the version file is in the root folder.3 AS-02 asset structure The various essence components and metadata collections of an AS-02 asset should be logically organized as a folder structure. the filename of the version file within a bundle shall be used as a substitute for the UMID. The UMID of the material package in the version file shall be the unique identifier of that version. In an asset management system. For non-MXF operations. Essence components in the media folder may exist that are not referenced by any version file. 7.0.

All essence components that can be referenced by a version file shall be placed in a subfolder called "media". A simple version file should contain metadata to describe the intended usage of each essence component. File system linking mechanisms shall not be used within the AS-02 bundle. audio. 5.doc Version 1.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. 4. A simple version file shall be a valid MXF file with external essence: OP1b.0. the term “composition” is used as a substitute for the term “version”.3.3. A version file may reference any of the essence components in the media folder. The maximum number of versions in a bundle may be constrained by the max_versions shim parameter. audio languages. In the case that they do. even if only a single essence component is contained in the bundle and the version file would also be valid as an OP1a file. All version files shall be placed in the root folder.6 Simple version file A simple version file is intended for simple bundle applications that do not require segmentation (OP2b) or editing (OP3b). Multiple references may be made to some essence components. Nov-18-2011 Page 12 of 43 . e. The name of the root folder shall be considered as the identification filename of the bundle.e. video keys or caption service. all files under the root folder shall be physically stored there. i. Version files may refer to multiple video. In applications where non-MXF version information is required.3. Note: This includes unreferenced essence that may be re-linked at some later date. Other subfolders may exist. All other files not referenced by a version file shall be placed in a subfolder called "extra". All essence components shall be referenced only once.mxf file that stores the media synchronization information. 4. 8. All essence component files shall have the same duration measured in edit units as required by the OP1b specification. Note: The intent of a simple version is that any software or device acting on that version shall use all of the referenced tracks. it shall be stored in an XML file in the root folder and shall have the same name as the related . 6. 9. 4. 2. The term “AS-02 composition file” shall be treated as equivalent to the term “AS-02 version file”. 1.AS-02-10-2011-11-18 MXF Versioning 7.7 Bundle All the files belonging to the asset shall be stored beneath a single root folder of a bundle. Additional constraints over and above section 4. 3. Note: With reference to point 4. Note: OP1b is specifically to be used as the operational pattern for simple version files.g. the precedence of the tracks shall be determined by the MXF track number property. Published specification . In some communities. 3.5 are listed below and clarified further in section 5. the number of audio samples in the underlying essence container may vary slightly in the case of non-integer number of audio samples per video frame. Shim parameter max_versions Definition Default value: unlimited Type: positive integer and unlimited Values: 1 to unlimited Maximum number of version files permitted in a bundle. and data tracks. The bundle of files shall have the following properties: 1. 11. 2. but are not used in this application specification. 4. 10. Unique and non-zero track numbers shall be used. Figure 2 shows the logical structure of an AS-02 asset bundle.

4. it may be required to keep a number of ".a filename specified as the pathname of the file relative to the root. The simple version file shall reference all the essence components in the media folder. The AS-02 specification provides a mechanism that shall be used for specifying the roles of these files within a manifest. Only one simple version file shall exist in a simple bundle. These files may be stored in any appropriate subfolder on the extras folder. The simple version file shall have the same name as the root folder. A specific example of a role is the provision of caption source files. It is intended for deterministic access. Permissible but very weak linkage .doc Version 1. QC reports and other associated files shall be placed in the extra folder or in a subfolder thereof.com/ extra/bbc. In a multi-lingual workflow. each of the essence component files shall be referenced from at most one OP1b program version header. 3.3. The use of these role identifiers is application-specific and should be mandated in the shim document if required. This linkage may be via: • • • Recommended practice . These roles shall be as specified in Annex B. easy essence tracking and easy deletion. at some point in its lifecycle. Note: This provides for a simple and error-free content aging / content deletion strategy that does not require reference counting. Note: This bundle is intended for use in single version applications. For example: • • • AMWA metadata is stored in: Sony metadata would be stored in: BBC metadata would be stored in: extra/amwa. web or IPTV deliverables.3.8 Simple bundle A simple bundle shall be used for single version interchange and is restricted as follows: 1.3. captions may be rendered to the broadcast. It is recommended that individual business should put their private metadata in a folder with a name corresponding an established Internet domain name. documents found in the extra folder should contain some linkage back to one or more of the MXF versions or components.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.AS-02-10-2011-11-18 MXF Versioning 4.tv/ extra/sony.dxfp" files with the asset so that.co. 2.the UMID of the version file’s material package. Published specification . Subfolders within the extra folder shall be used to manage individual metadata files to prevent filename collisions and the inadvertent overwriting of files. In a simple bundle. custom XML.cap" or ".by the presence of the file in the bundle. All AS-02 constraints shall apply unless overridden here.9 Extra folder The extra folder shall provide a facility to associate additional metadata and associated files within the AS-02 bundle.0. tools from multiple vendors intrinsically share files that exist in the extra folder. 4. such as on a playout server.scc" or ". In general. 4.10 Extra folder – role of a file In many workflows. Their role should be signaled as caption in the manifest file. Common usage .uk/ The management of the data in each business folder is outside the scope of this specification but may form part of an individual shim. Nov-18-2011 Page 13 of 43 . Metadata describing a show layout (position of the breaks).

A version file may contain segmentation and editing information. 5 Version file parameters and constraints 5. there may be generic stream containers in the version file. 5.3 Partitions carrying header metadata in the version file Header metadata in header and footer partitions shall follow the provisions of 377-1 section 7.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. bitrates) or choices (for example.11 Manifest file The root folder of the bundle shall contain a manifest file (manifest. and are syntactically valid XML NCNames. 4.doc Version 1. Fully constrained: a single choice or parameter value that all AS-02 applications will use identically • • Shims shall always express constraints that are equal to or stronger than the general specification.12 Shim file The root folder of the bundle shall contain a file (shim. The manifest file shall also contain a unique identifier that shall provide the identification of the bundle as a whole. Nov-18-2011 Page 14 of 43 . the names are chosen to be unique across the AS-02 namespace. A distinctive font is used for the names of parameters. that individual shims may further restrict.2 No essence in the version file There shall be no essence containers in the version file. To enable automated processing of shims. false When true.AS-02-10-2011-11-18 MXF Versioning 4.3. See section 10 for the specification of the format of this file. The manifest file contains a list of all of the files and folders in the bundle.xml) that contains all of the shim parameters and their values for the bundle.xml). Named parameters are specified whose values shall define further constraints that apply in specific shims.3. See section 9 for the specification of the format of this file.1 Provision categorization Each provision within the general specification and within each individual shim is categorized as one of the following: • • Unconstrained: everything permitted by SMPTE 377-1-2009. Strongly constrained: a range of values or set of choices is listed that individual shims must choose between. including the version and essence component files. Gently constrained: a range of values (for example. Published specification . Note: An essence container refers to the use of the MXF Generic Container to carry a stream of picture or sound essence.4 MXF header constraints in a version file The following metadata constraints shall apply to the version file. descriptive metadata schemes or essence types) is stated by the general AS-02 specification. The sections below define the general provisions that shall apply to all AS-02 files. 5.0. with their identifiers and relationships. Use of the MXF Generic Container to carry generic data streams in version files is acceptable if the shim parameter defined above is set to true. 5. Shim parameter generic_streams_in_version Definition Default value: false Type: boolean Values: true.5.

Published specification . The path shall be a URI relative to the version file and shall be correct at the time that the file was created. There shall be 1 material package. Shall not be present. 0 or more top-level file package(s) per essence component. Lower level source packages should be preserved in the version file by applications that edit or modify component files. 5. If the network locator does not point to the essence component file. sync_cut Default value: false Type: boolean When true.5 MXF header constraints in a simple version file The following additional constraints apply to a simple version file Set name Content Storage Material Package Constraint There shall be 1 top-level file package per essence component. There shall be 1 identification set added by each application altering the file. Shall be signaled as OP1b. For a closed file.AS-02-10-2011-11-18 MXF Versioning Set name Preface Identification Content Storage Constraint As per SMPTE 377-1-2009 revision. When false. Shall be signaled as OP1b. Data) Network Locator Definition Default value: 1 frame Type: free text The smallest duration that can be used in a material package timeline source clip property. Decoders shall use the network locator(s) as a hint and the UMIDs shall always be used to verify the integrity of the network locator value. All essence shall be externally referenced. no restriction on lower level packages. the version file may become an OP3b edit decision list. the durations shall be correct in the header metadata. This effectively constrains version files to be OP2b butt-edits of pre-conformed clips. OP2b or OP3b for multi-track version files. Unresolved UMID references shall not be permitted. Shall be compliant with OP1b.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. Shim parameter sub_clip_limit Essence Container Data Operational Pattern Material Package Source Package (File / Physical) Sequence (all cases) SourceClip (Picture. The timecode properties shall be compliant with MXF 377-1-2009. OP2a or OP3a for single-track version files. When complex essence types are in use. the UMIDs shall be resolved via some other mechanism. Primary package shall be a material package. There shall be a copy of the file package from each of the essence component files in the version file. The duration rules shall be the same as for the version file sequence as above. Shall be compliant with OP1b.doc Version 1. Text Locator Timecode Timeline Track SubClip Optional. this parameter needs to specify whether or not sub-clips may start or end within GOPs / access units or other structural elements of the encoding scheme. References shall only be made to file packages within the version file. material package source clips are constrained such that all tracks shall cut synchronously. Sound. Open files may use distinguished values as described in 377-1. One network locator shall exist for each file package. such as for long-GOP MPEG. Nov-18-2011 Page 15 of 43 .0.

entire_file. Essence component files shall only contain this metadata when the version files sign essence_only. crc16. 5. 5. 5. performance criteria can be specified that reflects the operation of a facility. simple versions with a duration value of a single frame may not play out correctly. 5. A true value indicates that track numbers shall be present and may be used by equipment.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.9 Minimum simple version duration Shim parameter min_sv_dur Definition Default value: 10 seconds Type: floating point Values: gently-constrained The minimum simple version duration parameter ensures that in an application specification. A false value indicates that track numbers may exist in the file. Nov-18-2011 Page 16 of 43 . If it is found that the version file header is open and the footer is closed. false When using audio components in an application that involves physical mapping of audio to ports on equipment.0. 5.6 Closed and complete metadata in the version file footer partition During update of a version file.11 Channel mapping with track numbers Shim parameter track_numbers Definition Default value: false Type: boolean Values: true. mic_type Default value: crc32 Type: list of permitted enumerations Values: HMAC-SHA1. but should not interpreted by equipment Published specification .7 No essence stream index tables in a version file Essence stream index tables shall not be included in any partition of a version file.AS-02-10-2011-11-18 MXF Versioning 5. just the essence stream (essence_only) or not at all (no_mic). Generic stream index tables may be included for data tracks. For example.doc Version 1. the header of the file may be in the progress of being updated. This is done via the track number property in the material package tracks. it is necessary to identify which of the audio essence components are mapped to which output channel. no_mic Version files may contain media integrity check information of the entire essence component file (entire_file). Applications reading the file should atomically read the closed and complete header metadata partition (it is small) and shall use that version of the metadata.10 Media integrity check for essence components Shim parameter mic_scope Definition Default value: essence_only Type: enumeration Values: essence_only. md5 Version files may contain a media integrity check using one of the valid mechanisms. then this should be indicative of an update in progress and appropriate caution should be taken. crc32.8 Version file KAG size of 1 The KAG size of a version file shall be 1.

Note: AS-03 files shall use only OP1a and may contain DMS-Segmentation metadata tracks. 5. On creation. Parameters may be further constrained by shims as described in the annexes or external documents.AS-02-10-2011-11-18 MXF Versioning 5. The timecode counting mode of a version file may be specified so that file writers create consistent outputs. When the essence is a specific variant. All data sets shall follow MXF generation ID rules.3.4 with the following additional constraints below. it should be annotated with metadata. OP2 or OP3 essence tracks in the material package. sound. signaling that every essence container has one and only one essence track. NDF. Only one type of essence element shall be present (i. picture or compound) in the essence container. A value of file_specific is intended for applications and facilities where DF or NDF cannot be known apriori. 6. In AS-02 essence component files.12 Timecode Shim parameter tc_mode Definition Default value: file_specific Type: enumeration Values: DF. These parameters are described in the sections below. Published specification .2 Mono essence Only one essence track shall exist in the file package.1 Essence track parameters and constraints 6. Nov-18-2011 Page 17 of 43 . file_specific. data. AS-02 version and essence component files may contain DMS-Segmentation metadata tracks. the value NDF is recommended.e. an 8kByte fill shall follow the header partition to allow for in-place extension. 6. Drop Frame (DF).1 General AS-02 essence component files shall each contain a single essence component of a single essence type.doc Version 1. bit 3 of byte 15 of the operational pattern identifier shall be set to zero to represent uni-track. non-Drop Frame (NDF) or file_specific values are permitted.1.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.13. When working with 60Hz or 24Hz material DF or NDF is recommended according to the working practises of the facility.2 Other descriptive metadata schemes Private application-specification-defined schemes and extensions to SMPTE 380M DMS-1-based schemes shall be identified in the preface.0.1 SOM/EOM Specific start-of-message (SOM) and end-of-message (EOM) metadata shall be provided in AS-02 version files using sequences of source references on MXF OP1.13 Descriptive metadata parameters and constraints 5.1. • • • • Header partition shall contain only metadata. They shall be subject to the general constraints listed in section 4. 6 Essence component file parameters and constraints Note: Shim constraints for essence components are expressed in the same manner as for version files in section 5.13. When working with 50Hz material. 5.

Nov-18-2011 Page 18 of 43 . index_strategy_clip Default value: lead Type: enumeration Values: lead. precede) the essence partition that it indexes or follow the essence partition that it indexes. This shall be specified application by application. follow or file_specific As above. Regular shall mean that any variation in the regularity shall be less than the smaller of 1 second or 10% of the period partition_spacing.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. Shim parameter partition_spacing Clip wrapped files shall have the following structure: a header partition.0.4 Partitions A partition in an AS-02 compliant essence component file shall only have one of the following types of data in it: • • • • Header metadata. Shim parameter index_strategy_frame Definition Default value: lead Type: enumeration Values: lead. When the index tables are calculated (PCM audio). follow or file_specific At each partition point in a given frame wrapped essence component file. one body partition with an index table.5 Index tables Frame wrapped essence shall have distributed index tables to aid process-during-write applications.e. 6. 6. but applies to clip wrapped files. Published specification .3 Interleaving AS-02 files shall not contain interleaved essence components. SMPTE 410-2008 generic stream.1. one body partition with clip wrapped essence.doc Version 1.1.1. This is shown in figure 5. Index table. the index partition shall either lead (i. lead means that the calculated index table immediately follows the header partition.AS-02-10-2011-11-18 MXF Versioning 6. The “file_specific” option covers applications where the strategy cannot be defined. Definition Default value: 60 seconds Type: floating point Values: strongly-constrained for frame wrapped files Body partitions in a frame wrapped file shall occur at regular temporal spacing indicated by this parameter. Figure 5: Clip wrapped file partition structure A RIP shall be present in all essence component files. Essence. a footer partition.

AS-02-10-2011-11-18 MXF Versioning 6. This definition is expected to appear in the SMPTE multi-channel audio specification. picture_bitrate Default value: none Type: list of integer ranges A list of supported bitrates or ranges of bitrates for compressed video. such as playout servers. inside a SMPTE 377-1-2009 data container) shall be in a single essence component file and shall be described by a single MXF track in the file package. for example “MPEG-2 H. Multi-channel audio carried as data in an audio file (e. All kinds shall be considered as mono-essence and shall be described by a single track in the file package. Shim parameter picture_family Definition Default value: none Type: list of strings A list of supported video essence compression families including any family-specific elements such as GOP structures and profiles. you would not expect different languages to be present within the same soundfield. Note: A soundfield is defined as the acoustical space in which the intended audio image is created. Compressed audio files shall be described by a single track in the file package. Therefore.7 Audio PCM audio files shall contain either mono audio or stereo audio or multi-channel audio. picture_format Default value: none Type: list of formatted strings A list of permitted video frame sizes and rates.1. with version files used to select the most appropriate representation. for example for different languages. it is common to find six tracks of audio from a single soundfield combined into a single PCM stream.1.doc Version 1. The media file of a bundle may contain both a combined file and separate files for the same audio.1.6 Video Video essence in AS-02 files may be of one of a selection of compression families and acceptable variability should be defined by individual shims. Note: This parameter allows a facility to document the capacity of their decoding devices.0. Published specification . for example 5. Stereo and multi-channel audio may be represented as separate PCM audio files. The audio within a compound essence container shall be ignored in AS-02 operations. 6.g. specifies the maximum number of video essence component files that can be simultaneously decoded from an AS-02 bundle.264 JPEG2000”. for example “1920/1080/50p/16:9”. Compressed audio files may contain multiple channels within a single soundfield.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. picture_component_limit Default value: 1 Type: non-negative integer or unlimited When a number is given. Note: In existing digital cinema workflows. Video files shall be frame wrapped with complete index tables. PCM audio channels from a different soundfield shall be in different files. Nov-18-2011 Page 19 of 43 . Audio from a compound essence containers representing more than one soundfield shall be extracted into a separate essence component files to ensure AS-02 compliance.

During the adoption period. this will be of the form “mono only files”. Note: This parameter allows a facility to document the capacity of their decoding devices. Variable bitrate compressed audio files shall be clip wrapped with a variable bitrate (VBR) index table. This data shall also be placed in a separate SMPTE 436M essence component file. The following shim parameters shall be used to indicate when legacy captioning or subtitle formats are used in the bundle. Published specification . specifies the maximum number of audio essence component files that can be simultaneously decoded from an AS-02 bundle. VBI data and VANC data may appear in the same SMPTE 436M essence component file.8 Closed captioning and subtitles Closed caption data and subtitling data carried in VBI or VANC shall be frame wrapped with complete index tables and shall not be interleaved in the video file. such as playout servers. compression types and any format specific elements such as delay setting. Shim parameter CC_data_essence Definition Default value: none Type: list of strings A list of supported data essence types for closed captioning including specific parameters.doc Version 1. Typically. Nov-18-2011 Page 20 of 43 . Constant bitrate compressed audio files shall be clip wrapped with a calculated index table. audio_file_arrangement Default value: none Type: free text A description of the physical storage strategy for audio. audio_component_limit Default value: unlimited Type: non-negative integer or unlimited When a number is given.g. This data shall be stored in a SMPTE 436M essence component file in the media folder. permitted soundfield arrangements. carriage in MPEG picture user data).1. subtitles.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.AS-02-10-2011-11-18 MXF Versioning Shim parameter audio_family Definition Default value: none Type: list of strings A list of supported audio essence families including bitrates. and VBI data. such as VBI lines. VBI and / or VANC for closed caption data shall be encapsulated in the video essence using a defined method (e.0. Non-caption data may also exist in the SMPTE 436M essence component file. 6. “stereo only files”. Note: This provision is to support legacy playback devices and should be avoided wherever possible as it can leads to the SMPTE 436M captions and it custom copy changing independently. “stereo files with optional Dolby E in a file” etc. VANC. Different languages for captions shall be carried in separate files. CC_custom Default value: false Type: boolean When true. where this data is contained in a large number of legacy file types. The intent of the AS-02 specification is that SMPTE 436M shall be used for the carriage of captioning. it is understood that legacy formats will exist. PCM audio files shall be clip wrapped with a calculated index table.

this is only true for SD images that are coded as “tall MPEG” (i. VBI data shall be encoded as active video within the video image. Decoders should be able to merge different kinds of data. the VBI area is in the active picture).AS-02-10-2011-11-18 MXF Versioning Shim parameter CC_render Definition Default value: false Type: boolean When true. Usually. Shim parameter VBI_data_essence Definition Default value: none Type: list of strings A list of supported data essence types including specific parameters such as VBI lines supported.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. for example on playout. this is only true for SD images that are coded as “tall MPEG” (i. such as playout servers. carriage in MPEG picture user data) as well as being present in a separate VBI essence component file.doc Version 1. ANC_custom Default value: false Type: boolean When true.9 Other VBI and ANC data Other VBI and VANC data shall be carried in SMPTE 436M. copy the VBI and VANC data into a separate file and when creating an AS-02 bundle. ANC data shall be encapsulated in the video essence using a defined method (e. ANC_data_essence Default value: none Type: list of strings A list of supported data essence types including specific parameters such as ANC packet types supported. the VBI area is in the active picture). 6. Any data in a separate SMPTE 436M file shall override any data of the same type carried within the video file.e. specifies the maximum number of closed caption files that can be merged when decoding an AS-02 bundle. Note: To preserve data that is intimate with a timeline essence component.1. VBI_custom Default value: false Type: boolean When true. carriage in MPEG picture user data) as well as being present in a separate ANC essence component file. Usually. Note: This parameter allows a facility to document the capacity of their decoding devices.e. Published specification . as per section 6. This data should also be placed in a separate VBI essence component file. The original data should be deleted from where it is originally sourced to avoid it leaking back into the workflow. VBI_render Default value: false Type: boolean When true.1. CC_component_limit Default value: unlimited Type: non-negative integer or unlimited When a number is given. VBI data shall be encapsulated in the video essence using a defined method (e. This data should also be placed in a separate VBI essence component file.8. VBI data for closed captions shall be encoded as active video within the video image.g. Nov-18-2011 Page 21 of 43 . The following shim parameters shall be used to indicate when legacy VBI or VANC formats are used in the bundle. Different types of VBI and VANC data should be split up into separate files.g.0.

Timecode mode . including any discontinuities therein. Metadata in the system item that is to be used in an AS-02 operation should be copied or moved to other containers such as the header metadata or SMPTE 436M data tracks. all VANC and VBI data is merged into a single essence component file. bit 3: uni-track set to “0” to signal that the essence in the file is atomic. 6. When set to false. such as playout servers.4 Timecode The timecode of an AS-02 version shall be controlled in the version file. Whatever the parameter is set to.1 Baseline operational pattern The operational pattern of an AS-02 essence component file shall be signaled as OP1a.doc Version 1. This data should also be present in a separate ANC essence component file. 6. data_component_limit Default value: unlimited Type: non-negative integer or unlimited When a number is given. specifies the maximum number of VBI or VANC files that can be merged when decoding an AS-02 bundle.2.may be specified in each shim. The following recommendations may be applied in a shim: Shim parameter sys_item_tc Definition Default value: false Type: boolean Indicates whether it is acceptable for the essence component file to carry timecode in the generic container system item. There may be several timecode tracks in the header metadata of an essence component. 6. data_separation Default vale: true Type: boolean When true.2 Essence container label AS-02 essence component files shall each specify essence container labels that shall correspond to the essence container used in that file. indicates that all data essence component files for VANC and VBI data shall be split into separate files. This provision is intended to capture source timecodes and does not affect the material package of any version file.2 Header metadata and operational pattern constraints 6.drop-frame or non-drop frame . Nov-18-2011 Page 22 of 43 . Note: This parameter allows a facility to document the capacity of their decoding devices. Published specification . bit 2: streamable set to “0” to signal that the essence in the file is streamable.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.e. The qualifier bits of the operational pattern in AS-02 essence component files shall be set as follows: • • • bit 1: internal essence set to “0” to signal internal essence only. i. Note: This specification does not permit a mixture of approaches. 6.0. VBI data shall be encoded as active video within the video image.2. there is only one track.2.AS-02-10-2011-11-18 MXF Versioning Shim parameter ANC_render Definition Default value: false Type: boolean When true.3 System item The generic container system item may be present but should not be used by AS-02 files. Note: This provision is intended to maximize compatibility with legacy MXF decoder applications.2. timecode in any generic container system shall be copied to the file package header metadata.

5 Random index pack All AS-02 version and essence component files. This specification may be a private xml specification or a SMPTE specification. Lower level source packages shall be preserved by applications that edit or modify component files.6 KAG size AS-02 essence component files shall have a KAG size of 1 unless this requirement conflicts with an underlying essence container specification. For progressive material.0. the value in that essence container specification shall be used. BodySID and IndexSID shall be present and shall be different. "none". Clip wrapped audio shall have the edit rate set to the audio sampling rate.2. KLV extension syntax (SMPTE 377-2) shall be used for MXF metadata extensions. 1 material package.2. One single entry corresponding to the single generic container. Header metadata shall exist in the header partition and may have optional fill. For interlaced J2k field coded material and for interlaced MPEG field coded material. with no run-in. describing a business rule of the presence of absence of tags. Source Package (File / Physical) Track (Timeline) There shall be a single essence descriptor for the essence. this is usually the field rate. For example: "SMPTE MCA language". "SMPTE MCA language & spatial".doc Version 1. The edit rates property of a track for material that is frame coded shall be equal to the rate of content packages in the essence. 2. Nov-18-2011 Page 23 of 43 . All files shall have a footer partition unless: 1. 1 top-level file package. 6. this is the underlying frame rate.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. The footer of an essence component file may contain a copy of the header metadata and it shall be marked closed and complete. Published specification . Shim parameter track_tag_policy Essence Container Data Material Package Definition Default value: none Type: free text Specifies how material package tracks in the essence component file are tagged with metadata. All files shall comply with SMPTE 377-12009.3 Header metadata parameters and constraints The header partition of an essence component file shall start at the first byte of the file. When a conflict exists. Each device altering the file shall add 1 identification set. Note: Once a published standard.AS-02-10-2011-11-18 MXF Versioning 6. when closed and complete. the underlying essence container specification forbids the existence of a footer. 6. the file is in the process of being written. shall contain a random index pack as per SMPTE 377-1-2009. Compliant with OP1a mono essence – shall contain only a single essence track. Any specific constraints on the header metadata shall be: Set name Preface Identification Content Storage Constraint As per SMPTE 377-1-2009. no restriction on lower level packages. For MPEG interlaced material this is usually the frame rate. Primary package shall be file package.

Not present in essence component files. “external”. Shall be present for all ANC components. The header metadata shall always be valid in a component file. or derive it from the specified source. aspect ratio. Sequence (all cases) SourceClip (Picture. Shim parameter ingest_TC Static Track Wave Audio Essence Descriptor VBI Data Descriptor ANC Data Descriptor Multiple Descriptor Network Locator Text Locator Timecode Definition Default value: none Type: extensible enumeration Values: “LTC”. This recommendation constrains the EBU recommendation on timecode in MXF. Shall be present for all VBI components.AS-02-10-2011-11-18 MXF Versioning Set name Event Track Constraint Only used for descriptive metadata tracks. Open files may use distinguished values as described in 377-1.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. lead_TC Default value: FP Type: enumeration Values: MP.which may be discontinuous shall be captured in the source package that is referenced by the top-level file package. The material package timecode and the top-level file package timecode with the lowest value of TrackNumber shall be identical. Duration values shall use the same rule as for sequences. Shall be present only for component files that have VBI and ANC data present. “source” or <value> Indicates that ingest (file creation) applications shall start the material package timecode and the top-level file package timecode at a given value. VerticalSubsampling. display width and height. This may often be the duration of the track. This is discouraged. To prevent metadata morphing. Note that metadata on an event track shall have its event duration equal to the validity of the metadata on the timeline. FP Indicates that an application requiring the timecode of the component file shall use the lowest numbered by TrackNumber file package timecode track (default) or the material package timecode track of the essence component file. Applications manipulating files should be aware that metadata described as static may no longer be static after splicing and editing operations. MaxGOP. “VITC”. static metadata should be placed on an event track with the duration set to the duration of the file. BpictureCount. shall include picture essence coding. the durations shall be correct in the header metadata. Shall be present for all MPEG video component files.0. Any captured timecode . Nov-18-2011 Page 24 of 43 . constant Bframes. Not present in essence component files. Bitrate. Shall be present for all uncompressed PCM audio component files.doc Version 1. ProfileAndLevel. Sound. Metadata may be present on a static track. “DVITC”. otherwise it shall not be used. This means that the process shown in figure 6 shall be followed: Published specification . Data) MPEG Descriptor For a closed file.

FTP and other operation require the parsing of the version file and the potential re-naming of the essence components. copy. the header or footer shall be marked closed and complete.doc Version 1. a legacy bundle is defined as a simple bundle with the following additional restrictions: 1. Nov-18-2011 Page 25 of 43 . 4. 5. The footer may contain a copy of the header metadata and it shall be marked closed and complete.AS-02-10-2011-11-18 MXF Versioning Figure 6: Valid header metadata process Open and incomplete partitions are created during file writing operation. 9. 8.1 Package labeling All applications that modify an MXF file shall create a new identification set in the file and shall preserve existing identification sets.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. A legacy bundle shall not have a root folder. There shall be no extra folder in a legacy bundle. It is recommended that file readers be able to accept files with these structures. 7. 6. Audio essence in a legacy bundle shall be uncompressed broadcast wave format (BWF) wrapped in SMPTE 382M. Legacy bundles are not required to have a shim file. Many legacy bundles may share the same "media. It can therefore allow the detection of differences between "master" metadata and "derived" metadata when an MXF process modifies a file. Full details are given in SMPTE 377-1-2009. 2. To retain backwards compatibility with the initial rollout and to provide a migration path for original equipment.0. A random index pack shall follow the footer.dir" folder. 6. 10. The disadvantage of legacy bundles is that non-MXF operations are very difficult. This information may be used to flag the fact that metadata reconciliation may be required. 7 Legacy bundles This section specifies AS-02 structures that have been created prior to the approval of this AS-02 specification document. The media subfolder shall be named "media. no root folder was included in the specification. A legacy bundle shall be identified by the filename of its simple version file.dir".3. When the writing operation is finished. 3. Legacy bundles are not required to have a manifest file. Note: This feature may be used to audit metadata modification in the essence component file. 7. Video essence in a legacy bundle shall be long-GOP MPEG2 wrapped in SMPTE 381M. Many legacy bundles may exist in the same folder. Most move. Published specification .1 Legacy bundles When AS-02 was initially proposed. The new identification set provides a generation ID that may be used to identify which elements of the file have changed.

01.txt The compliance_id shall be stored as FrameworkThesaurusName property of a SMPTE 380M Production Framework.01 7.01.0b. Published specification .g. 01. 0d. for example a SMPTE 380M based scheme.tv/AS-02-shim/2010/hd-j2k. It is included for file readers that need to be backwards compatible with legacy files.2.01.34. The descriptive metadata scheme identifiers shall be carried in the preface set of the MXF file according to SMPTE 377M.doc Version 1.01.2 Legacy shim identification .0e. For example.02. Shim parameter compliance_id Definition Default value: none Type: UTF-16 string It is recommended that the organization creating the shim uses an XML namespace identifier URI structure as a compliance_id. or some private MXF scheme.1 DMS-AS compliance ID Each AS-02 shim shall define a compliance ID string. For example. An application that is comparing compliance_id strings shall perform a UTF-16 case sensitive comparison that ignores whitespace at the start and end of strings. image resolutions may change. At least one DMS identifier in the legacy bundle shall be used in order to indicate the compliance ID of the AS-02 file (section 7.1).2b.01.04. audio arrangements may change and codecs may change. e. Publishing the shim document at that URL may also encourage other organizations to copy the shim and hence minimize unnecessary invention in the industry.compliance ID This section describes the way in which shims were signaled in files created prior to the first publication of the AMWA AS-02 specification. The string should identify the version of the shim to which the file was created.01. http://amwa. Note: The compliance ID may change over time within a shim.AS-02-10-2011-11-18 MXF Versioning 7.0. Nov-18-2011 Page 26 of 43 . 04.2. A legacy bundle shall contain one or more DMS identifiers indicating the constrained DMS in use.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. This minimizes the chances of a compliance_id clash with other organizations. using a constrained SMPTE 380M scheme would result in the following label in the preface set: DMS1 06.

partition_spacing index_strategy_frame Strong Strong lead lead Index_strategy_clip Published specification . the empty AS-02 generic shim is tabulated in this section. e. Clip wrapping strategy. A shim identifier (shim_id) shall identify the shim.3 General essence Dimension Description Parameter name AS-02 constraint Strong AS-02 values 60s Shimspecific constraint Shim-specific values Partition spacing Indexing strategy Indexing strategy Regular partition spacing. Nov-18-2011 Page 27 of 43 .g.txt The sections below are organized as a sheet to be filled in by a system designer who is constraining their system.1 Shim identifier To aid system designers and equipment vendors. http://amwa.AS-02-10-2011-11-18 MXF Versioning 8 Generic shim 8. This minimizes the chances of a shim identifier clash with other organizations. Publishing the shim document at that URL may also encourage other organizations to copy the shim and hence minimize unnecessary invention in the industry.0. 8. Not all the parameters are relevant in every design.2 Shim Dimension Shim ID Description The identifier of this shim.tv/AS-02-shim/2010/hd-j2k. Shim parameter shim_id Definition Default value: none Type: UTF-16 string It is recommended that the organization creating the shim uses an XML namespace URI as a shim_id. The entry in the parameter name column is intended for use as the name of an XML element in a machinereadable template for the shim. An example of a completed shim is given in annex A. This identifier is intended to signal the version of the shim that was in use when the bundle was created or modified.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. Some parameters can be left as none or not applicable (n/a). Parameter name shim_id AS-02 constraint Strong AS-02 values Shim-specific value 8. Frame wrapping strategy.doc Version 1.

AS-02-10-2011-11-18 MXF Versioning 8.6 Caption components Dimension Description Parameter name AS-02 constraint None AS-02 values None Shimspecific constraint Shim-specific values CC essence schemes CC custom formatting CC in-vision render CC component limit What caption essence types are allowed? Captions to be inserted in video in a custom manner? Captions inserted into the active picture? Maximum simultaneous caption components? CC_data_essence CC_custom Moderate false CC_render Moderate false CC_component_limit Moderate unlimited Published specification . Maximum simultaneous audio components? audio_family Audio file arrangement Audio component limit audio_file_arrangement None Moderate none unlimited audio_component_limit 8.doc Version 1.4 Picture components Dimension Description Parameter name AS-02 constraint Gentle AS-02 values none Shimspecific constraint Shim-specific values Picture essence schemes What picture signal schemes (compression. Nov-18-2011 Page 28 of 43 .5 Sound components Dimension Description Parameter name AS-02 constraint None AS-02 values none Shimspecific constraint Shim-specific values Sound essence schemes What sound signal schemes (compression.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.0. sampling or other) are encountered in programs? How many bits/second at real time? Picture raster and aspect ratio? Maximum simultaneous video components? picture_family Picture bitrate picture_bitrate Gentle none Picture format Picture component limit picture_format picture_component_limit Gentle Moderate none 1 8. sampling or other) are encountered in programs? Physical storage strategy for audio.

Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. What is the scope of the media integrity check? What algorithm is used for MIC? simple_versions_only generic_streams_in_version sub_clip_limit Gentle Gentle 1s false sync_cut min_sv_dur Gentle 10s Media integrity scope Media integrity type mic_scope Moderate essence_o nly crc32 mic_algorithm Moderate Published specification . Nov-18-2011 Page 29 of 43 .AS-02-10-2011-11-18 MXF Versioning 8. VBI data to be rendered into the active picture. Maximum simultaneous data components? Different types of VBI/VANC in separate files? VBI_data_essence None Moderate None false VBI_custom VBI_render Moderate false ANC_data_essence None Moderate None false ANC_custom ANC_render Moderate false data_component_limit Moderate unlimited data_separation Moderate true 8. What VBI essence types are allowed? Captions to be inserted in video in a custom manner. Is an edl a series of synchronous butt edits? Minimum duration of a simple version.0.doc Version 1.7 Other VANC / VBI components Dimension Description Parameter name AS-02 constraint AS-02 values Shimspecific constrai nt Shim-specific values VBI essence schemes VBI custom formatting VBI in-vision rendering ANC essence schemes ANC custom formatting ANC in-vision rendering Data component limit Separate data component files What VBI essence types are allowed? VBI data inserted in video in a custom manner.8 Version files Dimension Description Parameter name AS-02 constraint Gentle Strong AS-02 values false false Shimspecific constraint Shimspecific values Version file complexity Version file bloating Short clip limit Version file complexity File length Simple version files only? Can generic streams be put in a version file? Shortest length of a clip in an EDL. VBI data to be rendered into the active picture.

10 Bundle Dimension Description Parameter name max_versions AS-02 constraint None AS-02 values None Shimspecific constraint Shim-specific values Maximum versions Maximum number of versions. Note: Setting this property to 1 and the simple_version property to true is used to indicate that only simple bundles are acceptable.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. track_numbers Timecode tc_mode Strong <shim specific> 8.doc Version 1. Dimension Description Parameter name compliance_id AS-02 constraint None AS-02 values None Shim identifier The legacy compliance ID of this file. including the version and essence component files.11 Descriptive metadata Note: The shim identifier property "compliance_id" is included for legacy files only. Nov-18-2011 Page 30 of 43 .0. located in the root level folder of the bundle. 8. Shimspecific constraint Fully Shim-specific values 9 Manifest file format Each AS-02 bundle shall have a single manifest file.2.AS-02-10-2011-11-18 MXF Versioning Dimension Description Parameter name AS-02 constraint Gentle AS-02 values false Shimspecific constraint Shimspecific values Channel ID Is channel mapping done with track numbers? Timecode counting mode. Published specification . as described in section 7.1.9 Header metadata Dimension Description Parameter name sys_item_tc AS-02 constraint Moderate AS-02 values false Shimspecific constraint Shim-specific values System item timecode handling Track tag metadata Ingest timecode handling Timecode precedence Is the system item timecode copied to the header? How are tracks tagged? What timecode source shall be dominant when creating files? What timecode source shall be dominant when using essence files? track_tag_policy None Strong None none ingest_TC lead_TC Strong FP 8. The manifest file contains a list of all of the files and folders in the bundle.

as defined in IETF RFC 4122. 9. The manifest file shall be named manifest. Nov-18-2011 Page 31 of 43 . elements shown with a grey outline are optional.0.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.0).3 of this document for the formal element definition. human-readable annotation describing the person.1. facility or system (hardware/software) that created the bundle. Published specification . and is illustrated in figure 7. 9.1 Bundle name element The bundle name (BundleName) element uniquely contains the file name of the root-level folder of the bundle.2 Bundle identifier element For overall management of the asset.3 Creator element The creator (Creator) element shall be a free-form.AS-02-10-2011-11-18 MXF Versioning The manifest shall be encoded as an XML document (W3C XML 1.1 Manifest structure The top-level element in the manifest file shall be designated Manifest. The bundle identifier shall be encoded as a URN-encoded UUID.1. 9. Note: This will allow easy differentiation between bundles. Note: The creator property is intended only for display as guidance to a user. Each unique bundle shall have a distinct bundle identifier.1.xml. the bundle identifier (BundleID) element shall uniquely identify the bundle. Figure 7: Manifest structure element Note: In figure 7. See the XML schema declaration in section 9. 9.doc Version 1.

The creation date shall be encoded as xs:dateTime type.2 File element A manifest shall contain a list of files and folders. 9.6 File list element The file list (FileList) element shall contain the list of File elements that each describe the files and folders contained in the bundle. A file (File) element shall represent any file or folder that exists in the AS-02 bundle.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. See the XML schema declaration in section 9.doc Version 1. Each file shall be described by a file element.1. Nov-18-2011 Page 32 of 43 .3 of this document for a normative definition.5 Annotation text element (optional) Annotation text (AnnotationText) elements may be present and shall be a list of zero or more free-form. Published specification . human-readable annotations describing the bundle.1. Note: Annotation text elements are intended only for display as guidance to a user.1.0.4 Creation date element The creation date (CreationDate) element shall be set to the time and date at which the bundle was created.AS-02-10-2011-11-18 MXF Versioning 9. The manifest shall not include a file element entry for the manifest itself. The structure of the File element is described in section 9. 9. as illustrated in figure 8.2. The order of File elements in the list shall not be significant. 9.

1 File identifier element The file identifier (FileID) element shall represent the unique identifier associated with the described file.0. this value shall be extracted from the file and used in the manifest. 9.2. Nov-18-2011 Page 33 of 43 . Published specification . such as the primary package identifier of a version file or essence component file. If the file contains no defined identifier.AS-02-10-2011-11-18 MXF Versioning Figure 8 – File element with optional media integrity check Note: In figure 8. then the creator of the manifest file shall generate the identifier. elements shown with a grey outline are optional. Where the file has its own unique identifier.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.doc Version 1.

This size shall be expressed as an integer number of bytes.5 Media integrity check element (optional) The media integrity check (MIC) element contains the media integrity check value for the file. 3.3 Size element The size (Size) element contains the size of the file in bytes. All other files shall have a UUID encoded as a URN according to IETF RFC 4122. as specified in IETF RFC 1321. 9. relative to the root of the bundle.1 Element value The value of the media integrity check element (MIC) shall be of type xs:hexBinary.2 Type attribute The media integrity check type (type) attribute shall be present and shall indicate the algorithm used to create the media integrity check value for the AS-02 asset. Note: The choice of CRC types is based on ones in common use and easy to decode.0.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. The intention is to replace this section with a reference to AMWA's application specification for content integrity (AS-06) once work is completed. the file identifier shall be encoded as a URN representation of the UMID according to SMPTE 2029-2009. Where the native identifier of the file is a SMPTE UMID (SMPTE 330M). 9.2 Role element The role (Role) element shall be used to describe how the file is used within the bundle. computed according to the CRC-16-CCITT polynomial. The possible values of this parameter shall be: • • • • hmac-sha1 . md5 . Nov-18-2011 Page 34 of 43 . computed according to CRC-32C (Castagnoli) polynomial.2. The list is left deliberately short to minimize complexity when implementing a decoder. 9.4 Path element The path (Path) element contains the relative URI of the file. the file identifier shall be encoded as a URN representation of the universal label according to SMPTE 2029-2009. 4. To ensure full coverage of the range of content integrity types.17-bits polynomial length cyclic redundancy check.5. 2. 9. as defined in IETF RFC 2104 and IETF RFC 3174. 9.wikipedia. Where the native identifier of the file is a SMPTE UMID (SMPTE 330M) starting with the fixed 16-bytes 060a2b34h 01010105h 01010f20h 13000000h.2. The allowed values for the role element shall be as specified in Annex B.33-bits polynomial length cyclic redundancy check. The value of the element shall be used both for display as guidance for the user and as machine-interpretable information for content processing. The possible values of this parameter shall be: Published specification . 9. encoded as type xs:positiveInteger.2.2.5. crc32 .AS-02-10-2011-11-18 MXF Versioning The value of the identifier shall be encoded according to the following rules.5. crc16 .3 Scope attribute The media integrity check scope (scope) attribute shall be present and shall indicate the scope over which media integrity check values are calculated.2. See: http://en.org/wiki/Cyclic_Redundancy_Check. the size value shall be present and set to zero. For folders. Note: For more information on calculating CRCs.2.message digest algorithm 5. applied in order: 1.2. Where the native identifier of the file is a SMPTE universal label. the last 16-bytes of the UMID shall be used as a UUID encoded as a URN according to IETF RFC 4122.doc Version 1. 9.secure hash algorithm. implementers are advised to check the current status of this document and AS-06. the related Wikipedia page is a good place to start.

3 XML schema for manifests The XML Schema document presented in this section normatively defines the structure of a manifest using a machine-readable language.doc Version 1. 9. including essence and any wrapper.0. entire_file .amwa.6 Annotation text element (optional) Annotation text (AnnotationText) elements may be present and shall be a list of zero or more free-form. <xs:schema xmlns:xs="http://www.ManifestType --> <xs:complexType name="ManifestType"> <xs:sequence> <xs:element name="BundleName" type="xs:string"/> <xs:element name="BundleID" type="mft:UUID"/> <xs:element name="Creator" type="xs:string"/> <xs:element name="CreationDate" type="xs:dateTime"/> <xs:element name="AnnotationText" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="FileList"> <xs:complexType> <xs:sequence> <xs:element name="File" type="mft:FileType" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> <!-. 9.tv/as-02/1.the media integrity check value was calculated for the entire file. Note: Annotation text elements are intended only for display as guidance to a user.tv/as-02/1.FileType --> <xs:complexType name="FileType"> <xs:sequence> <xs:element name="FileID" type="mft:IdType"/> <xs:element name="Role" type="mft:FileRole"/> <xs:element name="Size" type="xs:nonNegativeInteger"/> <xs:element name="Path" type="xs:anyURI"/> <xs:element name="MIC" minOccurs="0"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:hexBinary"> <xs:attribute name="type" type="mft:MICTypeType" use="required"/> <xs:attribute name="scope" type="mft:MICScopeType" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="AnnotationText" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> Published specification .the media integrity check was calculated for the wrapped essence stream of an essence component file. Nov-18-2011 Page 35 of 43 .amwa.org/2001/XMLSchema" xmlns:mft=”http://www.2.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.0/manifest" elementFormDefault="qualified" attributeFormDefault="unqualified"> <!-.w3. human-readable annotations describing the file.AS-02-10-2011-11-18 MXF Versioning • • essence_only .0/manifest” targetNamespace="http://www.

IdType --> <xs:simpleType name="IdType"> <xs:union memberTypes="mft:UUID mft:UMID mft:UL mft:emptyID"/> </xs:simpleType> <!-. It is non-functional and intended for informative purposes only. Published specification .){3}[0-9a-fA-F]{8}"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="emptyID"> <xs:restriction base="xs:string"> <xs:pattern value=""/> </xs:restriction> </xs:simpleType> <!-.MICScopeType --> <xs:simpleType name="MICScopeType"> <xs:restriction base="xs:string"> <xs:enumeration value="essence_only"/> <xs:enumeration value="entire_file"/> </xs:restriction> </xs:simpleType> <!-. 9.UMID --> <xs:simpleType name="UMID"> <xs:restriction base="xs:string"> <xs:pattern value="urn:smpte:umid:([0-9a-fA-F]{8}\.){7}[0-9a-fA-F]{8}"/> </xs:restriction> </xs:simpleType> <!-. Nov-18-2011 Page 36 of 43 .MICTypeType --> <xs:simpleType name="MICTypeType"> <xs:restriction base="xs:string"> <xs:enumeration value="hmac-sha1"/> <xs:enumeration value="crc32"/> <xs:enumeration value="crc16"/> <xs:enumeration value="md5"/> </xs:restriction> </xs:simpleType> <!-.FileRole --> <xs:simpleType name="FileRole"> <xs:restriction base="xs:string"> <xs:enumeration value="file"/> <xs:enumeration value="version"/> <xs:enumeration value="essencecomponent"/> <xs:enumeration value="shim"/> <xs:enumeration value="manifest"/> <xs:enumeration value="qc"/> <xs:enumeration value="graphic"/> <xs:enumeration value="caption"/> <xs:enumeration value="folder"/> </xs:restriction> </xs:simpleType> <xs:element name="Manifest" type="mft:ManifestType"/> </xs:schema> Note: The schema is available from the AMWA FTP site as file AS-02/AS-02-10-2011-11-17_Manifest.UL --> <xs:simpleType name="UL"> <xs:restriction base="xs:string"> <xs:pattern value="urn:smpte:ul:([0-9a-fA-F]{8}\.UUID --> <xs:simpleType name="UUID"> <xs:restriction base="xs:string"> <xs:pattern value="urn:uuid:[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fAF]{4}-[0-9a-fA-F]{12}"/> </xs:restriction> </xs:simpleType> <!-.doc Version 1.xsd.0.AS-02-10-2011-11-18 MXF Versioning <!-.4 Sample manifest file (informative) The following manifest sample XML is a valid instance of the manifest schema.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.

mxf</mft:Path> <mft:MIC type="md5" scope="entire_file">a2b275b19bfa4bfebcc422f604e25b8d</mft:MIC> </mft:File> <mft:File> <mft:FileID> urn:smpte:umid:060a2b34.905f0022.d240fc56.5f0bc2f2 </mft:FileID> <mft:Role>essencecomponent</mft:Role> <mft:Size>1932121</mft:Size> <mft:Path>media/AmberFin_AS02_MP2_720i25_4_a2.5f0bc2f2 </mft:FileID> <mft:Role>essencecomponent</mft:Role> <mft:Size>62517511</mft:Size> <mft:Path>media/AmberFin_AS02_MP2_720i25_4_v0.31540580.AS-02-10-2011-11-18 MXF Versioning <?xml version="1.01010511.01010811.01010105.org/2001/XMLSchema-instance"> <mft:BundleName>AmberFin_AS02_MP2_720i25_4</mft:BundleName> <mft:BundleID>urn:uuid:D08C1211-5172-4875-96D5-1B731E1D71CD</mft:BundleID> <mft:Creator>AS-02 Reference Manifest File MP2 .01010105.23480022.13000000.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.xml</mft:Path> <mft:MIC type="md5" scope="entire_file">b587ea43b80900fcf5112aaafcc31ab8</mft:MIC> </mft:File> <mft:File> <mft:FileID>urn:uuid:ACC8E4E7-5D37-4CE6-889D-E88C3DA4023C</mft:FileID> <mft:Role>folder</mft:Role> <mft:Size>0</mft:Size> <mft:Path>extra</mft:Path> <mft:AnnotationText>Size and MIC are not encoded for folders.bbaffc56.mxf</mft:Path> <mft:MIC type="md5" scope="entire_file">fc8578b82d4eb729be0212633f81318f</mft:MIC> <mft:AnnotationText>Single version file of this AS-02 bundle.Richard Cartwright AMWA</mft:Creator> <mft:CreationDate>2011-12-06T10:53:22-00:00</mft:CreationDate> <mft:FileList> <mft:File> <mft:FileID> urn:smpte:umid:060a2b34.13000000.w3.13000000.01010d11.31540580.23480022.0/manifest" xmlns:xsi="http://www.mxf</mft:Path> <mft:MIC type="md5" scope="entire_file">1cca0628ed8d1d7aba35858a567a3d2c</mft:MIC> </mft:File> </mft:FileList> </mft:Manifest> Published specification .amwa.0" encoding="UTF-8"?> <mft:Manifest xmlns:mft="http://www.2e41fc56.31540580.5f0bc2f2 </mft:FileID> <mft:Role>essencecomponent</mft:Role> <mft:Size>1932121</mft:Size> <mft:Path>media/AmberFin_AS02_MP2_720i25_4_a1.01010105.5f0bc2f2 </mft:FileID> <mft:Role>version</mft:Role> <mft:Size>16153</mft:Size> <mft:Path>AmberFin_AS02_MP2_720i25_4. Nov-18-2011 Page 37 of 43 .mxf</mft:Path> <mft:MIC type="md5" scope="entire_file">9805614535f364690491a5ac16e8c620</mft:MIC> </mft:File> <mft:File> <mft:FileID> urn:smpte:umid:060a2b34.Manual Generation .tv/as-02/1.doc Version 1.</mft:AnnotationText> </mft:File> <mft:File> <mft:FileID>urn:uuid:03EF7F92-8339-4A2A-BB7D-562A5A486ADF</mft:FileID> <mft:Role>folder</mft:Role> <mft:Size>0</mft:Size> <mft:Path>media</mft:Path> </mft:File> <mft:File> <mft:FileID> urn:smpte:umid:060a2b34.01010105.01010811.</mft:AnnotationText> </mft:File> <mft:FileID>urn:uuid:D67509D3-5579-4388-8148-9FF1E08BBB59</mft:FileID> <mft:Role>shim</mft:Role> <mft:Size>411</mft:Size> <mft:Path>shim.f7693d57.31540580.23480022.0.13000000.

g. Note: This document does not specify the process by which a shim identified is generated.1. Figure 9: Top-level shim structure Note: In figure 9. 10.doc Version 1. The shim file contains an identifier for the constraints of the shim in the form of a URI namespace reference to the shim that is being used. 10.1 Shim structure The top-level element in the shim file shall be designated Shim.4 of this document for explicit type information.1. Network HD Contribution. The value of the element shall be of type xs:string.2 Shim identifier element The shim identifier (ShimID) element contains the string identifier of this shim specification (section 8).1. See the XML schema declaration in Section 10. The shim file shall be encoded as an XML document [XML 1. Published specification . 10. Nov-18-2011 Page 38 of 43 . located in the root level folder of the bundle.AS-02-10-2011-11-18 MXF Versioning 10 Shim file format Each AS-02 bundle shall have a single shim file.3 Annotation text element (optional) Annotation text (AnnotationText) elements may be present and shall be a list of zero or more free-form.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.0]. elements with grey outline are optional. The shim file shall be named shim.1 Shim name element A name for the AS-02 shim according to a controlled vocabullary. as shown in figure 9. Note: Implementers need to be aware that the shim schema will be actively further developed within AMWA to be a machine-readable list of shim constraints. human-readable annotations describing the shim. e. The value of the element shall be of type xs:anyURI.xml. 10.0.

<?xml version="1.org/2001/XMLSchema" xmlns:shim="http://www. <xs:schema xmlns:xs="http://www.amwa.tv/AS-02-shim/2010/hd-j2k.ShimType --> <xs:complexType name="ShimType"> <xs:sequence> <xs:element name="ShimName" type="xs:string"/> <xs:element name="ShimID" type="xs:anyURI" minOccurs="0"/> <xs:element name="AnnotationText" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="ApplicationSpec" type="xs:string" minOccurs="0"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> <xs:element name="Shim" type="shim:ShimType"/> </xs:schema> Note: The schema is available from AMWA as FTP site as file AS-02/AS-02-10-2011-11-17_Shim.0/shim" elementFormDefault="qualified" attributeFormDefault="unqualified"> <!-.w3.1.4 Application specification element (optional) Application specification element (ApplicationSpec) is reserved for future use.amwa.xsd.3 Sample XML shim file (informative) The following sample shim XML is a valid instance of the shim schema.tv/as-02/1. 10. 10. 10.txt</ShimID> <AnnotationText>An example shim for HD J2k created by AMWA</AnnotationText> </Shim> Published specification .0. Nov-18-2011 Page 39 of 43 . It is non-functional and intended for informative purposes only.amwa.tv/as-02/1.2 XML schema for shims The XML schema document presented in this section normatively defines the structure of a shim file using a machine-readable language.tv/as-02/1.0/shim" xmlns:xsi="http://www. The value of the element shall be of type xs:string.0/shim" targetNamespace="http://www.w3.0" encoding="UTF-8"?> <Shim xmlns="http://www.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.AS-02-10-2011-11-18 MXF Versioning Note: Annotation text elements are intended only for display as guidance to a user.doc Version 1.org/2001/XMLSchema-instance"> <ShimName>Network HD Contribution</ShimName> <ShimID>http://amwa.

XRsiz2 = 2. Ssiz2 = 9.01. XRsiz0 = 1. MXF SMPTE 382M Mapping AES3 and Broadcast Wave Audio into the MXF Generic Container Codec Uncompressed BWF Constraints Stored as Stereo pairs. Stored in media\*_a??.03. both VBI and ANC in this case. No ANC or VBI information is rendered into the active picture The following list of video essence types is permitted. 3. # 1 2 Parameter mono_essence_op1a VBI_custom and ANC_custom Type boolean boolean Value True.01. YRsiz2 = 1} Resolution 1920x1080 23.04. Sampling / structure 24-bit. XRsiz1 = 2. All ancillary data. audio and ancillary data essences that make up the asset.2B. AS-02 sample shim document (informative) A. Ssiz0 = 9. Nov-18-2011 Page 40 of 43 .01.98p 3 4 VBI_render and ANC_render boolean picture_family list 5 audio_family The following list of audio essence types is permitted. The table below specifies the constraints on the essence and its wrapping as MXF. 48kHz or 96kHz Published specification . Ssiz1 = 9.00 JPEG 2000 picture subdescriptor field values: Rsiz – 0 Xsiz – 1920 Ysiz – 1080 XOsiz – 0 YOsiz – 0 XTsiz – 1920 YTsiz – 1080 XTOsiz – 0 YTOsiz – 0 Csiz – 3 Picture component sizing – {Number of component = 3.AS-02-10-2011-11-18 MXF Versioning Annex A. No other proprietary ANC formats are maintained.02. YRsiz0 = 1.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. False. Stored in media\*_v0. is stored as separate SMPTE 436M streams in essence component files. All essence components are stored as mono-essence OPa1a files False.01.1 Essence component files The essence component files contain the video.mxf.0D. YRsiz1 = 1.0C.01. 01.0E.doc Version 1.mxf MXF SMPTE 422M Mapping JPEG 2000 codestreams into the MXF generic container Codec JPEG 2000 Constraints YUV 422 10bit. 100Mbps CDCI picture essence descriptor fields: Essence container UL 06.0.34.

audio channels are labeled from “1”. This should be indicated here. All of the tracks in present in the version file must be cut synchronously. N/A Media integrity check is not used. All other MXF timecodes shall be considered to be annotations. # 1 2 3 4 5 Parameter generic_streams_in_version min_sv_dur mic_algorithm mic_scope track_numbers Type Boolean Time Enum Enum Boolean Value False. 00:57:30. In a stereo pair. http://www. The lead timecode shall be taken from the timecode component of the material package of version file. Value 1 sec. Video tracks are labeled “1”.3 # 1 2 sync_cut Version files Parameter Type Time boolean Some facilities only use simple version files.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. The track numbers will be written into the material package of the version file. True. A. The simple version files do not describe any edits to the components. 1 sec.00 is the expected start timecode of the first frame of any complete asset.2 Simple version files A simple version file (SPV) links together the essence components to create a complete asset. Stored in media\*_vanc??.0. No generic streams are permitted in a simple version file.scc files in "extra\captions" folder. constraining the version files to be butt-edits of pre-conformed clips.AS-02-10-2011-11-18 MXF Versioning # 6 Parameter CC_data_essence Type Value The following list of data essence types is permitted. the track number applies to the left channel. Index tables are in the partition after the essence. 7 8 9 partition_spacing index_strategy_frame and index_strategy_clip track_tag_policy time enum specification 10s between partitions.tv/as-02/hd/v0/2010 10 11 ingest_TC lead_TC enum enum 12 shim_id UL list A. True. All MP tracks are tagged with their nominal track position. Nov-18-2011 Page 41 of 43 . Lagging. The minimum size of a clip built into an edit list is 1 second.doc Version 1. sub_clip_limit Published specification . N/A Media integrity check is not used.mxf MXF SMPTE 436M MXF mappings for VBI lines and ancillary data packets Contents SMPTE 291M VANC data Coding Processing Packets used to create . the right channel shall take the value of the left channel plus one. The minimum duration of an AS-02 file compliant with this shim is 1 second. MP::TC. This depends on the asset being ingested and is not fixed by this specification.amwa.

0.5 # Bundle Parameter Type Value This section intentionally blank in this case.AS-02-10-2011-11-18 MXF Versioning A. This section intentionally blank in this case. Published specification . Nov-18-2011 Page 42 of 43 .doc Version 1.4 Metadata in MXF-AS-02 Here we detail any special metadata to be included in the file or any constraints on the metadata used in the workflow.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. # Parameter Type Value A.

Manifest file in the root folder. A quality control report.g. overlay etc.stl. It shall be the responsibility of an application that creates a new file in the bundle to assign the correct role. All . Note: As specified in section 9. Graphics files for bugs. extra extra/amwa.mxf file in the root folder of the bundle that represent a version of the asset. . media.dfxp. to clear out all the graphics files prior to distribution. This helps implementers persist intentionally empty folders.mxf files in the media sub folder unless overridden by some other role.AS-02-10-2011-11-18 MXF Versioning Annex B.doc Version 1.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.2.tv) shall have an entry in the manifest. the manifest file shall not be listed as a file within a manifest.mxf files in the media subfolder may be labeled as graphic if the intention is that it shall be overlayed by some process onto the main video.0.cap. shim graphic Shim Graphics files Shim file in the root folder. . . Nov-18-2011 Page 43 of 43 . Note: The purpose of roles is for an AS-02 aware application to be able to. sami and other files used to source captions should be labeled as caption. It shall be the responsibility of applications that modify or transcode bundles to persist those roles in the new manifest. All . for example: quickly locate the correct QC file in a workflow. Role file essencecomponent version manifest Contents Just a file Essence component Version file Manifest file Description Default file role. All subfolders (e. Note that . Registered manifest file roles (normative) This annex contains a registered list of different roles that may be assigned to a file in the manifest. smill. qc caption folder QC reports Caption source files Folders Published specification . logos. This role type of manifest is included for use in future or external applications. Dependent data files should be labeled as file.