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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.1 Shim identifier To aid system designers and equipment vendors. Clip wrapping strategy.tv/AS-02-shim/2010/hd-j2k.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning. This identifier is intended to signal the version of the shim that was in use when the bundle was created or modified. e. Some parameters can be left as none or not applicable (n/a).2 Shim Dimension Shim ID Description The identifier of this shim.g. Publishing the shim document at that URL may also encourage other organizations to copy the shim and hence minimize unnecessary invention in the industry. Not all the parameters are relevant in every design. 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.doc Version 1. Nov-18-2011 Page 27 of 43 . This minimizes the chances of a shim identifier clash with other organizations.0.txt The sections below are organized as a sheet to be filled in by a system designer who is constraining their system. A shim identifier (shim_id) shall identify the shim. the empty AS-02 generic shim is tabulated in this section.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. partition_spacing index_strategy_frame Strong Strong lead lead Index_strategy_clip Published specification . Parameter name shim_id AS-02 constraint Strong AS-02 values Shim-specific value 8. An example of a completed shim is given in annex A. 8. Frame wrapping strategy. http://amwa.AS-02-10-2011-11-18 MXF Versioning 8 Generic shim 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? How many bits/second at real time? Picture raster and aspect ratio? Maximum simultaneous video components? picture_family Picture bitrate picture_bitrate Gentle none Picture format Picture component limit picture_format picture_component_limit Gentle Moderate none 1 8. sampling or other) are encountered in programs? Physical storage strategy for audio.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.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. 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.0. Nov-18-2011 Page 28 of 43 .

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

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

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

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

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

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

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

Published specification .4 Sample manifest file (informative) The following manifest sample XML is a valid instance of the manifest schema.){7}[0-9a-fA-F]{8}"/> </xs:restriction> </xs:simpleType> <!-.){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> <!-. Nov-18-2011 Page 36 of 43 .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> <!-. It is non-functional and intended for informative purposes only.UL --> <xs:simpleType name="UL"> <xs:restriction base="xs:string"> <xs:pattern value="urn:smpte:ul:([0-9a-fA-F]{8}\.MICScopeType --> <xs:simpleType name="MICScopeType"> <xs:restriction base="xs:string"> <xs:enumeration value="essence_only"/> <xs:enumeration value="entire_file"/> </xs:restriction> </xs:simpleType> <!-.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> <!-.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> <!-.Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.0. 9.UMID --> <xs:simpleType name="UMID"> <xs:restriction base="xs:string"> <xs:pattern value="urn:smpte:umid:([0-9a-fA-F]{8}\.doc Version 1.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.xsd.

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

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

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

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

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

Nov-18-2011 Page 42 of 43 .doc Version 1.5 # Bundle Parameter Type Value This section intentionally blank in this case.AS-02-10-2011-11-18 MXF Versioning A.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. Published specification .Copyright © 2011 AMWA AMWA-AS-02-10-2011-11-18_MXF_Versioning.0. # Parameter Type Value A. This section intentionally blank in this case.

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

Sign up to vote on this title
UsefulNot useful