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

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

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

In parallel. the order of precedence of the types of normative information in this document shall be as follows: Normative prose shall be the authoritative definition.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 . Today’s stereo audio gets upgraded to multi-channel and multi-lingual.AS-02-10-2011-11-18 MXF Versioning Unless otherwise specified.0 (Fifth Edition) Namespaces in XML 1. 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. All standards are subject to revision. In order to build systems that work at the MXF level rather than at the MPEG. AS-02 is an application specification providing a set of rules that MXF encoders and MXF decoders must follow. Unfortunately. constitute provisions of this recommended practice. 3 Reference documents The following standards contain provisions that. through reference in this text. then figures.doc Version 1. 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 . The compression format of today gets replaced with a better one from tomorrow. At the time of publication. over time. 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. The facility that started as SD introduces HD. In an ideal world. the editions indicated were valid. requirements for a facility change. distribution and publishing. Nov-18-2011 Page 7 of 43 .Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.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. and then any other language forms. Tables shall be next.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. followed by formal languages. This Published specification .0. JPEG2000 or DV level. a facility operates with a constant pressure to reduce the cost of production.

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

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

You can see in the figure that any customized metadata type is permitted within AS-02.AS-02-10-2011-11-18 MXF Versioning Extra metadata and content that is not MXF-wrapped is stored in the extra folder. package bundle (zip).doc Version 1.xml show_format. Published specification .Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. remove version and essence. seek. Examples of non-MXF operations include: move bundle. find unreferenced essence components. extract simple version etc.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. transfer bundle (FTP). update manifest. but may be further restricted within a shim.2 MXF and non-MXF operations (informative) AS-02 shall permit both MXF operations and non-MXF operations. purge extra files. record.mxf manifest. add extra file.xml version file media extra media-owner. All MXF operations shall result in files that comply with the MXF suite of specifications. The root folder contains two XML documents that are used to manage the asset.. create version. add track.0.tv qc-vendor. 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.doc amwa. Nov-18-2011 Page 10 of 43 .3. A non-MXF operation is one that does not involve parsing the MXF metadata.xml shim. remove track.com wss2016. Examples of MXF operations include: play. asset asset. jog. An MXF operation is one that involves parsing the MXF metadata. 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. checksum bundle.

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

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

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

AS-02-10-2011-11-18 MXF Versioning 4.xml).11 Manifest file The root folder of the bundle shall contain a manifest file (manifest.12 Shim file The root folder of the bundle shall contain a file (shim.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. 5. Gently constrained: a range of values (for example. The sections below define the general provisions that shall apply to all AS-02 files. the names are chosen to be unique across the AS-02 namespace.3.3. Strongly constrained: a range of values or set of choices is listed that individual shims must choose between. that individual shims may further restrict. See section 9 for the specification of the format of this file. descriptive metadata schemes or essence types) is stated by the general AS-02 specification. The manifest file contains a list of all of the files and folders in the bundle. The manifest file shall also contain a unique identifier that shall provide the identification of the bundle as a whole. Published specification . including the version and essence component files. 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.2 No essence in the version file There shall be no essence containers in the version file. false When true. with their identifiers and relationships. 5.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. A version file may contain segmentation and editing information. See section 10 for the specification of the format of this file.0.4 MXF header constraints in a version file The following metadata constraints shall apply to the version file. Note: An essence container refers to the use of the MXF Generic Container to carry a stream of picture or sound essence. A distinctive font is used for the names of parameters.doc Version 1. Nov-18-2011 Page 14 of 43 . Shim parameter generic_streams_in_version Definition Default value: false Type: boolean Values: true. 5. To enable automated processing of shims. 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.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. and are syntactically valid XML NCNames. 5 Version file parameters and constraints 5. 4. bitrates) or choices (for example.5. Named parameters are specified whose values shall define further constraints that apply in specific shims. there may be generic stream containers in the version file.xml) that contains all of the shim parameters and their values for the bundle.

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

Essence component files shall only contain this metadata when the version files sign essence_only. A false value indicates that track numbers may exist in the 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. it is necessary to identify which of the audio essence components are mapped to which output channel. 5. For example.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.0.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. crc16. false When using audio components in an application that involves physical mapping of audio to ports on equipment. entire_file. no_mic Version files may contain media integrity check information of the entire essence component file (entire_file). mic_type Default value: crc32 Type: list of permitted enumerations Values: HMAC-SHA1.6 Closed and complete metadata in the version file footer partition During update of a version file. A true value indicates that track numbers shall be present and may be used by equipment. 5. simple versions with a duration value of a single frame may not play out correctly. crc32.AS-02-10-2011-11-18 MXF Versioning 5.8 Version file KAG size of 1 The KAG size of a version file shall be 1. the header of the file may be in the progress of being updated. just the essence stream (essence_only) or not at all (no_mic). 5. If it is found that the version file header is open and the footer is closed. then this should be indicative of an update in progress and appropriate caution should be taken. This is done via the track number property in the material package tracks. but should not interpreted by equipment Published specification . 5.10 Media integrity check for essence components Shim parameter mic_scope Definition Default value: essence_only Type: enumeration Values: essence_only. Generic stream index tables may be included for data tracks. Nov-18-2011 Page 16 of 43 .doc Version 1. 5.11 Channel mapping with track numbers Shim parameter track_numbers Definition Default value: false Type: boolean Values: true.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. md5 Version files may contain a media integrity check using one of the valid mechanisms. performance criteria can be specified that reflects the operation of a 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. Drop Frame (DF).12 Timecode Shim parameter tc_mode Definition Default value: file_specific Type: enumeration Values: DF.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. sound. When the essence is a specific variant. The timecode counting mode of a version file may be specified so that file writers create consistent outputs. OP2 or OP3 essence tracks in the material package. When working with 50Hz material. 6.0. 5.1 Essence track parameters and constraints 6.1.13.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. file_specific. In AS-02 essence component files. NDF. it should be annotated with metadata.2 Mono essence Only one essence track shall exist in the file package.e. non-Drop Frame (NDF) or file_specific values are permitted. • • • • Header partition shall contain only metadata. an 8kByte fill shall follow the header partition to allow for in-place extension. Note: AS-03 files shall use only OP1a and may contain DMS-Segmentation metadata tracks. Nov-18-2011 Page 17 of 43 .4 with the following additional constraints below. 6. These parameters are described in the sections below.3. All data sets shall follow MXF generation ID rules. AS-02 version and essence component files may contain DMS-Segmentation metadata tracks. On creation. bit 3 of byte 15 of the operational pattern identifier shall be set to zero to represent uni-track. the value NDF is recommended. data.13. 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. signaling that every essence container has one and only one essence track. They shall be subject to the general constraints listed in section 4. Published specification .AS-02-10-2011-11-18 MXF Versioning 5. A value of file_specific is intended for applications and facilities where DF or NDF cannot be known apriori. Parameters may be further constrained by shims as described in the annexes or external documents.1 General AS-02 essence component files shall each contain a single essence component of a single essence type.doc Version 1.1. Only one type of essence element shall be present (i. 5. When working with 60Hz or 24Hz material DF or NDF is recommended according to the working practises of the facility. picture or compound) in the essence container.13 Descriptive metadata parameters and constraints 5.

the index partition shall either lead (i. Essence. one body partition with clip wrapped essence. follow or file_specific As above. 6. but applies to clip wrapped files.1. Index table. Published specification .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.e. precede) the essence partition that it indexes or follow the essence partition that it indexes.0. Figure 5: Clip wrapped file partition structure A RIP shall be present in all essence component files. lead means that the calculated index table immediately follows the header partition. 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. follow or file_specific At each partition point in a given frame wrapped essence component file. When the index tables are calculated (PCM audio). one body partition with an index table.5 Index tables Frame wrapped essence shall have distributed index tables to aid process-during-write applications.1.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. 6. This shall be specified application by application.AS-02-10-2011-11-18 MXF Versioning 6. index_strategy_clip Default value: lead Type: enumeration Values: lead. SMPTE 410-2008 generic stream. This is shown in figure 5.1. Shim parameter index_strategy_frame Definition Default value: lead Type: enumeration Values: lead. 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. The “file_specific” option covers applications where the strategy cannot be defined. a footer partition.3 Interleaving AS-02 files shall not contain interleaved essence components.doc Version 1. Nov-18-2011 Page 18 of 43 .

g.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. with version files used to select the most appropriate representation.1.doc Version 1. All kinds shall be considered as mono-essence and shall be described by a single track in the file package. picture_bitrate Default value: none Type: list of integer ranges A list of supported bitrates or ranges of bitrates for compressed video. Nov-18-2011 Page 19 of 43 . for example 5.1. Compressed audio files may contain multiple channels within a single soundfield. Multi-channel audio carried as data in an audio file (e. The audio within a compound essence container shall be ignored in AS-02 operations.AS-02-10-2011-11-18 MXF Versioning 6. The media file of a bundle may contain both a combined file and separate files for the same audio.264 JPEG2000”.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. This definition is expected to appear in the SMPTE multi-channel audio specification. 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.0. it is common to find six tracks of audio from a single soundfield combined into a single PCM stream. Note: In existing digital cinema workflows. Published specification . Therefore. Note: A soundfield is defined as the acoustical space in which the intended audio image is created. Note: This parameter allows a facility to document the capacity of their decoding devices.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. 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.1. Stereo and multi-channel audio may be represented as separate PCM audio files. such as playout servers. picture_component_limit Default value: 1 Type: non-negative integer or unlimited When a number is given. for example “1920/1080/50p/16:9”. for example for different languages. 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. specifies the maximum number of video essence component files that can be simultaneously decoded from an AS-02 bundle. you would not expect different languages to be present within the same soundfield. Video files shall be frame wrapped with complete index tables. Compressed audio files shall be described by a single track in the file package. 6. PCM audio channels from a different soundfield shall be in different files.

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

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

including any discontinuities therein.may be specified in each shim.2.AS-02-10-2011-11-18 MXF Versioning Shim parameter ANC_render Definition Default value: false Type: boolean When true. such as playout servers.2.drop-frame or non-drop frame . Timecode mode . Note: This specification does not permit a mixture of approaches. VBI data shall be encoded as active video within the video image.2. bit 2: streamable set to “0” to signal that the essence in the file is streamable. 6.doc Version 1. 6. all VANC and VBI data is merged into a single essence component file. Nov-18-2011 Page 22 of 43 . 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.2. This data should also be present in a separate ANC essence component file. When set to false. there is only one track. Note: This provision is intended to maximize compatibility with legacy MXF decoder applications. Whatever the parameter is set to. Note: This parameter allows a facility to document the capacity of their decoding devices.4 Timecode The timecode of an AS-02 version shall be controlled in the version file. 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.e. There may be several timecode tracks in the header metadata of an essence component.1 Baseline operational pattern The operational pattern of an AS-02 essence component file shall be signaled as OP1a. 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 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.3 System item The generic container system item may be present but should not be used by AS-02 files. indicates that all data essence component files for VANC and VBI data shall be split into separate files. bit 3: uni-track set to “0” to signal that the essence in the file is atomic. This provision is intended to capture source timecodes and does not affect the material package of any version file. timecode in any generic container system shall be copied to the file package header metadata. 6.2 Header metadata and operational pattern constraints 6.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. 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. i. 6. Published specification . data_separation Default vale: true Type: boolean When true.0.

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

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

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

This minimizes the chances of a compliance_id clash with other organizations. e. Published specification . For example. image resolutions may change. audio arrangements may change and codecs may change.34.0.2 Legacy shim identification . or some private MXF scheme. Nov-18-2011 Page 26 of 43 . 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. http://amwa.AS-02-10-2011-11-18 MXF Versioning 7.02.01.01. It is included for file readers that need to be backwards compatible with legacy files.01 7. The descriptive metadata scheme identifiers shall be carried in the preface set of the MXF file according to SMPTE 377M.txt The compliance_id shall be stored as FrameworkThesaurusName property of a SMPTE 380M Production Framework.0b.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. 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.2. using a constrained SMPTE 380M scheme would result in the following label in the preface set: DMS1 06.01. for example a SMPTE 380M based scheme. The string should identify the version of the shim to which the file was created. 04.01.doc Version 1.1).Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.01.0e.tv/AS-02-shim/2010/hd-j2k.01. For example.g.2. Note: The compliance ID may change over time within a shim.04.1 DMS-AS compliance ID Each AS-02 shim shall define a compliance ID string. 0d. Publishing the shim document at that URL may also encourage other organizations to copy the shim and hence minimize unnecessary invention in the industry. A legacy bundle shall contain one or more DMS identifiers indicating the constrained DMS in use. 01. 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.2b.

e.0.doc Version 1.tv/AS-02-shim/2010/hd-j2k. A shim identifier (shim_id) shall identify the shim. Not all the parameters are relevant in every design.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. This minimizes the chances of a shim identifier clash with other organizations. 8.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.1 Shim identifier To aid system designers and equipment vendors.g. This identifier is intended to signal the version of the shim that was in use when the bundle was created or modified. An example of a completed shim is given in annex A. http://amwa.AS-02-10-2011-11-18 MXF Versioning 8 Generic shim 8.txt The sections below are organized as a sheet to be filled in by a system designer who is constraining their system. 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.2 Shim Dimension Shim ID Description The identifier of this shim. Publishing the shim document at that URL may also encourage other organizations to copy the shim and hence minimize unnecessary invention in the industry. Clip wrapping strategy. Frame wrapping strategy. 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. Nov-18-2011 Page 27 of 43 . the empty AS-02 generic shim is tabulated in this section. 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. partition_spacing index_strategy_frame Strong Strong lead lead Index_strategy_clip 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.AS-02-10-2011-11-18 MXF Versioning 8.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. sampling or other) are encountered in programs? Physical storage strategy for audio. 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.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 .0.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 .Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.doc Version 1.

Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.doc Version 1. Is an edl a series of synchronous butt edits? Minimum duration of a simple version.AS-02-10-2011-11-18 MXF Versioning 8. VBI data to be rendered into the active picture. VBI data to be rendered into the active picture.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. Nov-18-2011 Page 29 of 43 .0. What VBI essence types are allowed? Captions to be inserted in video in a custom manner.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. 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 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 .

Dimension Description Parameter name compliance_id AS-02 constraint None AS-02 values None Shim identifier The legacy compliance ID of this file.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. Shimspecific constraint Fully Shim-specific values 9 Manifest file format Each AS-02 bundle shall have a single manifest file. located in the root level folder of the bundle.11 Descriptive metadata Note: The shim identifier property "compliance_id" is included for legacy files only.0.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. Note: Setting this property to 1 and the simple_version property to true is used to indicate that only simple bundles are acceptable. including the version and essence component files. track_numbers Timecode tc_mode Strong <shim specific> 8. Nov-18-2011 Page 30 of 43 . 8. Published specification .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.doc Version 1. as described in section 7.2.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.1.

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

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

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

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

0/manifest" elementFormDefault="qualified" attributeFormDefault="unqualified"> <!-. including essence and any wrapper. Nov-18-2011 Page 35 of 43 .the media integrity check was calculated for the wrapped essence stream of an essence component file.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.org/2001/XMLSchema" xmlns:mft=”http://www. <xs:schema xmlns:xs="http://www.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 .tv/as-02/1.6 Annotation text element (optional) Annotation text (AnnotationText) elements may be present and shall be a list of zero or more free-form.amwa.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.2. human-readable annotations describing the file.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> <!-.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. entire_file .amwa.doc Version 1. 9.0.0/manifest” targetNamespace="http://www.w3.tv/as-02/1. 9.AS-02-10-2011-11-18 MXF Versioning • • essence_only .

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.0.MICScopeType --> <xs:simpleType name="MICScopeType"> <xs:restriction base="xs:string"> <xs:enumeration value="essence_only"/> <xs:enumeration value="entire_file"/> </xs:restriction> </xs:simpleType> <!-.){7}[0-9a-fA-F]{8}"/> </xs:restriction> </xs:simpleType> <!-. 9.xsd. Nov-18-2011 Page 36 of 43 .){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> <!-. It is non-functional and intended for informative purposes only.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> <!-.doc Version 1.UMID --> <xs:simpleType name="UMID"> <xs:restriction base="xs:string"> <xs:pattern value="urn:smpte:umid:([0-9a-fA-F]{8}\.Copyright © 2011 AMWA AMWA-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.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> <!-. Published specification .AS-02-10-2011-11-18 MXF Versioning <!-.IdType --> <xs:simpleType name="IdType"> <xs:union memberTypes="mft:UUID mft:UMID mft:UL mft:emptyID"/> </xs:simpleType> <!-.UL --> <xs:simpleType name="UL"> <xs:restriction base="xs:string"> <xs:pattern value="urn:smpte:ul:([0-9a-fA-F]{8}\.

13000000.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.01010105.f7693d57.13000000.5f0bc2f2 </mft:FileID> <mft:Role>essencecomponent</mft:Role> <mft:Size>1932121</mft:Size> <mft:Path>media/AmberFin_AS02_MP2_720i25_4_a1.01010105.tv/as-02/1.31540580.01010d11.0.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 .01010811.31540580.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.Manual Generation .23480022.amwa.0" encoding="UTF-8"?> <mft:Manifest xmlns:mft="http://www.01010105.mxf</mft:Path> <mft:MIC type="md5" scope="entire_file">a2b275b19bfa4bfebcc422f604e25b8d</mft:MIC> </mft:File> <mft:File> <mft:FileID> urn:smpte:umid:060a2b34.bbaffc56.w3.mxf</mft:Path> <mft:MIC type="md5" scope="entire_file">1cca0628ed8d1d7aba35858a567a3d2c</mft:MIC> </mft:File> </mft:FileList> </mft:Manifest> Published specification .2e41fc56.doc Version 1. Nov-18-2011 Page 37 of 43 .</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.mxf</mft:Path> <mft:MIC type="md5" scope="entire_file">fc8578b82d4eb729be0212633f81318f</mft:MIC> <mft:AnnotationText>Single version file of this AS-02 bundle.5f0bc2f2 </mft:FileID> <mft:Role>essencecomponent</mft:Role> <mft:Size>62517511</mft:Size> <mft:Path>media/AmberFin_AS02_MP2_720i25_4_v0.23480022.01010511.5f0bc2f2 </mft:FileID> <mft:Role>version</mft:Role> <mft:Size>16153</mft:Size> <mft:Path>AmberFin_AS02_MP2_720i25_4.mxf</mft:Path> <mft:MIC type="md5" scope="entire_file">9805614535f364690491a5ac16e8c620</mft:MIC> </mft:File> <mft:File> <mft:FileID> urn:smpte:umid:060a2b34.13000000.5f0bc2f2 </mft:FileID> <mft:Role>essencecomponent</mft:Role> <mft:Size>1932121</mft:Size> <mft:Path>media/AmberFin_AS02_MP2_720i25_4_a2.23480022.01010105.01010811.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.0/manifest" xmlns:xsi="http://www.31540580.13000000.905f0022.d240fc56.</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.AS-02-10-2011-11-18 MXF Versioning <?xml version="1.31540580.

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

4 Application specification element (optional) Application specification element (ApplicationSpec) is reserved for future use.0/shim" xmlns:xsi="http://www.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. Nov-18-2011 Page 39 of 43 .amwa.0.amwa.tv/as-02/1.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.txt</ShimID> <AnnotationText>An example shim for HD J2k created by AMWA</AnnotationText> </Shim> Published specification .1.amwa.w3.w3. It is non-functional and intended for informative purposes only. <xs:schema xmlns:xs="http://www. 10. The value of the element shall be of type xs:string.AS-02-10-2011-11-18 MXF Versioning Note: Annotation text elements are intended only for display as guidance to a user.xsd.0" encoding="UTF-8"?> <Shim xmlns="http://www.doc Version 1.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. <?xml version="1.0/shim" targetNamespace="http://www. 10.tv/AS-02-shim/2010/hd-j2k.org/2001/XMLSchema-instance"> <ShimName>Network HD Contribution</ShimName> <ShimID>http://amwa.tv/as-02/1.0/shim" elementFormDefault="qualified" attributeFormDefault="unqualified"> <!-.3 Sample XML shim file (informative) The following sample shim XML is a valid instance of the shim schema. 10.org/2001/XMLSchema" xmlns:shim="http://www.

No ANC or VBI information is rendered into the active picture The following list of video essence types is permitted.AS-02-10-2011-11-18 MXF Versioning Annex A. All ancillary data.2B.01. No other proprietary ANC formats are maintained. 48kHz or 96kHz Published specification .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. Nov-18-2011 Page 40 of 43 . AS-02 sample shim document (informative) A. both VBI and ANC in this case. # 1 2 Parameter mono_essence_op1a VBI_custom and ANC_custom Type boolean boolean Value True. audio and ancillary data essences that make up the asset.0. YRsiz2 = 1} Resolution 1920x1080 23.mxf MXF SMPTE 422M Mapping JPEG 2000 codestreams into the MXF generic container Codec JPEG 2000 Constraints YUV 422 10bit. YRsiz0 = 1. False.34. YRsiz1 = 1.0C. Ssiz0 = 9.03.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. XRsiz0 = 1. 100Mbps CDCI picture essence descriptor fields: Essence container UL 06. All essence components are stored as mono-essence OPa1a files False.01.04. XRsiz2 = 2.mxf.01. is stored as separate SMPTE 436M streams in essence component files. XRsiz1 = 2.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. Ssiz1 = 9.0E. Ssiz2 = 9. 3. Stored in media\*_v0.0D. 01.1 Essence component files The essence component files contain the video. The table below specifies the constraints on the essence and its wrapping as MXF. 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??.02. Sampling / structure 24-bit.doc Version 1.01.

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

5 # Bundle Parameter Type Value This section intentionally blank in this case.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. 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. This section intentionally blank in this case.0.AS-02-10-2011-11-18 MXF Versioning A. # Parameter Type Value A.

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