[Specification (Published)] AMWA AS-11 X2
MXF Program Contribution - HD Intra

About this web page

This web page is the principal rendering / view of the AMWA AS-11 X2 Specification.

Full details of all the Components (Blocks, Notes, and the others) that form this Rules-based Specification are either shown directly on the current web page or are included in the "specification_data_files" directory that accompanies the page (with explicit links from the current page).

Important links
Specification Repository on GitHub	This repository is where the entire Specification (including this file and alternative renderings / views of the Specification) is stored and version controlled
List of Releases	Milestones marking significant points in the development of the Specification
Specifications Page on the AMWA Website	The home of Specifications on the AMWA website
Development and Implementation Resources	Provides resources such as Specification issue tracking, MXF sample files, and tools

AS-11: Media Contribution File Formats

The AMWA AS-11 Specifications define constrained media file formats for the delivery of finished media assets to a broadcaster or publisher. Each Specification is developed for a particular business purpose.

Purpose of the AS-11 X2 Specification

Aims

This Specification aims to define a file format for the delivery of finished HD intra-coded (I-Frame only) TV Programmes. It aims to define:

a vendor-neutral and broadcaster-neutral package, using open technologies for delivery of finished programming from program producers and program distributors to broadcast stations
a package that is sufficiently simple so as to limit the scope for interoperability problems
a self-contained & play-out ready package

Relationship to AS-11 UK DPP HD v1.1

This Specification builds on many aspects of AS-11 UK DPP HD v1.1 but updates several of the technologies used. Examples include: an update of the Picture Essence mapping, the introduction of Multichannel Audio labeling, and the embedding of Descriptive Metadata as XML documents.

Some notes on practical use

The content may be delivered at the broadcast bit-rate, picture format and aspect ratio, or it may be transcoded at the broadcast station to the bit-rates and formats required for particular broadcast channels. Similar transcoding may be applied to audio and captions; additionally, specific audio and caption tracks may be selected for different broadcast channels.
The content may be pre-packaged for broadcast without further changes or it may be segmented for ease of insertion or replacement of interstitials.
There may be more than one package per programme.
The package may contain some pre and post roll content not for transmission.

Understanding the Specification Blocks Tree

The Rules-Based Specification Framework

This Specification has been written using a 'Rules-based Specification Framework'. In this framework, each 'constraint' or 'rule' is expressed as a 'Component' which can be unambiguously identified by its ID (the Component ID is a web address / URL; there need not be any content available at this web address). These Components assemble into 'networks' or 'webs' to form complete Specifications, with many Components being re-used across a number of Specifications. Through this approach machine processable Specifications are developed which are less ambiguous and easier to implement and test. To read a more detailed introduction to the Rules-based Specification Framework refer to Rules-Based Specifications: Modelling and Processing.

Blocks (B) are the fundamental 'building bricks' of a Specification -- they provide its structure.
A Block can either link to Artefacts (A) that it 'owns' or link to other Blocks.
Artefacts provide the real content of a Specification. They may contain textual statements, code excerpts, or tables, for example.
Artefacts often refer to Terms (T) and References (R) as well as Blocks.
Blocks are sometimes described by Notes (N).
There are two special types of Block which allow the value of one Block to be set by another Block:
- Parameter Key Block (K) -- this is a Block whose value must be set elsewhere in the Specification (it effectively defines a "variable" or an "argument").
- Parameter Value Block (V) -- this is a Block which sets the value of a specific Parameter Key Block.

In this document the network of Blocks (and other Components) that form the Specification are shown as a 'tree': the Specification Blocks Tree. The letters in brackets above are used in the tree to identify the different kinds of Component.

Conformance

An implementation complies with this Specification if it complies with the Components from which it is constructed, as shown in the Specification Blocks Tree, subject to the following provisions:

An implementation complies with a Block if it complies with all of the normative Components from which it is constructed. "Informative" items (as defined below) do not have to be complied with.
"Note" Components are considered "informative". All other Components are considered "normative" unless otherwise noted.
Compliance with some Blocks is not mandatory. Such Blocks are marked with an alternative "conformance" state (such as "optional" or "recommended").
The name / title of a Component is considered "informative".
Prose Artefacts are written as statements of fact. An implementation complies with one of these Artefacts if the stated fact is True for the implementation.
Other Artefacts are "data files" (such as SMPTE Metadata Registers XML files or XML Schema files). Some of these may be partially rendered below. An implementation must always fully comply with these data files -- links are provided to such data files in the Specification Blocks Tree.
Note that an Artefact does not always make sense on its own: all of the Artefacts contained within a Block need to be read (in order) to understand the Block fully and correctly.

The Specification Blocks Tree

The following icons are used in the Specification Blocks Tree:

Block: Its meaning is defined by its contents, which can be Artefacts or other Blocks.
Parameter Key: A Block whose value must be set elsewhere in the Specification (it effectively declares a "variable" or an "argument").
Parameter Value: A Block which sets the value of a specific Parameter Key Block.
Note: This provides informative guidance on the implementation or application of a Block.
Artefact: A statement or a data file within a Block.
Note Artefact: A statement or a data file within a Note.

: An icon with a solid fill denotes constraints that are mandatory.
: An icon with an outline style denotes constraints that are not mandatory.

: Metadata about a Rules-based Specification Component.

Loading Specification Block Tree …

File Format with Parameter Values

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/FF_2_r006/

File Format with Parameter Keys

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/FF_0_r003/
Core MXF constraints
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/MXF_Core/
- MXF File Format
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/000/
  - The file conforms to SMPTE ST 377-1:2011.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/001/
    - Section 5.2.1 of SMPTE ST 377-1:2011 sets out a non-exhaustive list of changes from SMPTE ST 377:2004.
- Operational pattern 1a
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/010/
  - The file conforms to SMPTE ST 378:2004.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/011/
    - The file must be labelled as OP1a in the Operational Pattern property of all Partition Packs and the Preface Set, as required by SMPTE ST 377-1:2011 in Section 7.1 and Annex A, respectively.
- Closed Complete Header
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/020/
  - The Header Partition is "Closed" and "Complete".
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/014/
    - Byte 15 of the Header Partition Pack Key must be set to 04h and all Header Metadata must have correct values. Hence 'Distinguished Values' cannot be used for 'Best Effort' properties. See Section 6.2.3 of SMPTE ST 377-1:2011 for a full explanation.
- RIP present
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/040/
  - The file has a Random Index Pack.
- KAG size of 1
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/050/
  - Every Partition in the file uses a KLV Alignment Grid of 1.
- Generic Container
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/090/
  - The file uses the Generic Container.
- Internal Essence
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/100/
  - The Generic Container is internal to the file.
- Strict Frame Wrapping
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/110/
  - The Generic Container uses Frame Wrapping.
  - If the Generic Container contains Picture Essence then the related Edit Unit duration is equal to the duration of a video frame of the Picture Essence.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E8/
    - For example, this means that if the Picture Essence is field-encoded then each Edit Unit contains the data assosiated with both of the video fields for a video frame.
- One-to-one Track mapping
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/120/
  - Each Essence Track in the Top-Level File Package is referenced by exactly one Essence Track in the Material Package.
  - No division/combination of Audio Channels between Sound Tracks
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E19/
    - This prohibits:
      
      the mapping of audio channels from a multi-channel Sound Track in a Source Package to single-channel Sound Tracks in the Material Package
      
      the mapping of audio channels from single-channel Sound Tracks in a Source Package to multi-channel Sound Tracks in the Material Package
      
      which is specified in Annex E of SMPTE ST 382:2007.
Header Metadata KLV Fill (Recommended)
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/KLVF_B/
- When first created, the file includes a KLV Fill item of at least 4 MB in total length following the Header Metadata.
- Implementation Notes
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/note/002/
  - The "total length" is of the entire item and includes the length of the Key and Length fields.
    
    The extra space afforded by the KLV Fill allows Header Metadata to be edited and added to without rewriting the entire file.
- Definition of megabyte
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/note/E37/
  - The unit symbol "MB" refers to a megabyte, which is 1 000 000 bytes.
MXF Indexing and Partitioning
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/Index_0/
- The file is in accordance with either of: MXF Indexing and Partitioning strategy for VBE Essence or MXF Indexing and Partitioning strategy for CBE Essence.
  - MXF Indexing and Partitioning strategy for VBE Essence
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/block/MXF_Inter/
    - Segment the Essence Container
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/101b/
      - The Essence Container is segmented into Partitions after every X minutes of Essence where X is between one and ten inclusive.
      - Essence partitioning
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/E12/
        
        Explanation of Essence Segmenting and Partitions
        
        Refer to SMPTE ST 377-1:2011 Section 6.2.1 for the "Partition Rules Overview"
        
        Small segments
        
        There could be small segments of Essence under this regime. This would occur if, for example:
        
        There is less than one minute of Essence in total. In this case there is a single Essence segment and this Essence segment is short (less than one minute).
        
        There is 30.5 minutes of Essence and Essence is being segmented every 10 minutes. In this case the final segment is only 30 seconds long.
    - Index Each Essence Container Segment
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/060b/
      - Each Essence Container segment is indexed by Index Table Segment(s) that occur after it but before the next Essence Container segment.
      - These Index Table Segment(s) index every Edit Unit of every Essence Element in the Essence Container segment.
      - Indexing and Partitions
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/E13/
        
        Index Table Segment details
        
        The stated constraints mean that in each Index Table Segment a "Delta Entry Array" will be required. Additionally, if there is at least one <VBE> <Essence Element> in the <Essence Container> then an "Index Entry Array" could be required (the need for this will depend on, for example, whether <KLV Fill> padding has been used).
        
        Partitions
        
        This Block allows a number of options regarding which Partition the Index Table Segments are located in. For example, they could be in their own dedicated Partition or in the same Partition as the next Essence Container segment (because in a Partition Index Table Segments always come before an Essence Container segment). The Index Table Segments will not necessarily be in the Partition that immediately follows the Essence Partition: there could be other Partitions in between (such as a Generic Stream Partition).
        
        Index Table Repetition
        
        This Block places no constraint on Index Table Repetition. For example, a complete Index Table could additionally be included somewhere in the file if required.
    - Application to CBE Essence
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/E29/
      - While these constraints are designed for use with Variable Bytes per Element (VBE) Essence, it is possible to apply them to Constant Bytes per Element (CBE) Essence. There are more efficient ways to deal with CBE Essence, however.
  - MXF Indexing and Partitioning strategy for CBE Essence
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/block/MXF_Intra/
    - Index precedes Essence
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/060/
      - The file contains a complete Index Table before the Essence.
    - Index all Essence
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/070/
      - The Index Table indexes every Edit Unit of every Essence Element in the file.
    - Single Essence Partition
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/101/
      - The Generic Container is entirely contained in exactly one Partition.
    - Indexing and Partitions
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/007/
      - It's generally considered good MXF practice to have one 'thing' per Partition, so you'd have separate Partitions for Header Metadata, Essence, and Index Tables. This isn't a requirement but following best practice is encouraged.
        
        The Index Table could be placed in the Header Partition, its own Body Partition or in a Body Partition with the Essence. Indeed it could be distributed across all three of these locations. Decoders need to be able to cope with all of these posibilities.
AVC mapped with ST 381-3
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/P002/
- One Picture Track
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/180/
  - The Material Package contains exactly one Picture Track.
- AVC Byte Stream Format Picture Essence
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/P_AVC/
  - The Picture Essence is AVC and uses the AVC Byte Stream Format.
- ST 381-3 mapping
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/PM1/
  - The Picture Essence is mapped to the file as specified in SMPTE ST 381-3:2013.
  - The value of Byte 15 of the "Essence Container" label is 60h.
  - The Picture Essence Descriptor used is the {CDCIDescriptor}.
  - Use of the AVC Sub Descriptor
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E11/
    - SMPTE ST 381-3:2013 defines the AVC Sub Descriptor and states that it "should" be used. This Block places no additional constraints on the use of the AVC Sub Descriptor. Therefore, as far as this Block is concerned its use is regarded as optional but recommended. However, note that SMPTE ST 381-3:2013 does mandate how the values of the AVC Sub Descriptor are populated -- for certain AVC streams it would not be possible to fulfil these requirements and so in such cases there is no choice but to omit the AVC Sub Descriptor.
  - AVC has no external dependencies
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E7/
    - Everything to be displayed during the Material Package Picture Track needs to be decodable without references to external dependencies. For example, this means that:
      
      The required SPS and PPS will need to be present at an appropriate point / points in the wrapped AVC.
      
      For inter-frame coded material <Pre-Charge> and <Roll-Out> could be required.
  - Picture Element Length
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E10/
    - ST 381-3:2011 states:
      
      The length field of the KLV coded Element shall be 4 bytes BER long-form encoded (i.e. 83h.xx.yy.zz) for Frame wrapping.
      
      4 bytes BER long-form encoded length is limited to 16 MiB (FF.FF.FF). This might become restrictive at the maximum data rates allowed by AVC at Level 5.
- Picture Essence Constraints
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/param2/
  - This is a Parameter Key Block – its value is set by the Parameter Value Block Picture Essence Constraints
  - Specifies further constraints on the "Picture Essence" and its mapping to the MXF file.
Multichannel, 24-bit, 48 kHz, uncompressed PCM, mapped with ST 382
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/S0_r001/
- One Soundfield Group per Sound Track
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/220b/
  - Each Sound Track represents all of the Audio Channels for exactly one Soundfield Group.
- Uncompressed 24-bit PCM audio at 48 kHz
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/230/
  - For each Audio Channel the Sound Essence is "uncompressed PCM audio data" per SMPTE ST 382:2007, sampled at 48 kHz with 24 bits per sample.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/029/
    - As per Section 6 of SMPTE ST 382:2007 samples are stored as little-endian integers.
- Constrained ST 382 Wave PCM mapping
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/240b/
  - The Sound Essence is mapped to the file as "Wave Audio Essence" using the method described by SMPTE ST 382:2007.
  - In the {WAVEPCMDescriptor} the (ordinarily optional) "ElectrospatialFormulation" property is not present.
  - In the {WAVEPCMDescriptor} the (ordinarily optional) "ChannelAssignment" property is present.
  - In the {WAVEPCMDescriptor} the value of the "ChannelAssignment" property is the same for all Sound Tracks.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/006b/
    - This prohibits the use of the "AES3 Audio Essence Descriptor" defined in SMPTE ST 382:2007.
- Audio Layout
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/AL_r001/
  - An Audio Layout Mode is used with the properties set as specified by Audio Layout Mode 0 or one of the Audio Layout Modes specified by Extra Audio Layout Modes.
    - Audio Layout Mode
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/ALM_r001/
      - The value of Channel Assignment Label is a SMPTE Universal Label that is used as the value of the Sound Essence Descriptor property that signals channel assignment.
      - If MCA Labeling Present is "true" then Constrained Multichannel Audio Labeling Framework is used. Otherwise the Multichannel Audio Labeling Framework specified in SMPTE ST 377-4:2012 is not used.
        
        Constrained Multichannel Audio Labeling Framework
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/SN2/
        
        The file uses the Multichannel Audio Labeling Framework specified in SMPTE ST 377-4:2012.
        
        There is exactly one AudioChannelLabelSubDescriptor for each Audio Channel. This AudioChannelLabelSubDescriptor is strongly referenced by the "SubDescriptors" property of the Generic Sound Essence Descriptor of the Sound Track that contains the Audio Channel.
        
        There is exactly one SoundfieldGroupLabelSubDescriptor for each Soundfield Group. This SoundfieldGroupLabelSubDescriptor is strongly referenced by the "SubDescriptors" property of the Generic Sound Essence Descriptor of a Sound Track in the Soundfield Group.
        
        There is one or more GroupOfSoundfieldGroupsLabelSubDescriptor(s) for each Soundfield Group. Each of these GroupOfSoundfieldGroupsLabelSubDescriptors is strongly referenced by the "SubDescriptors" property of the Generic Sound Essence Descriptor of a Sound Track in the Soundfield Group.
        
        Each AudioChannelLabelSubDescriptor references exactly one SoundfieldGroupLabelSubDescriptor.
        
        Each SoundfieldGroupLabelSubDescriptor references all of the GroupOfSoundfieldGroupsLabelSubDescriptor(s) for the Soundfield Group it relates to.
        
        In each AudioChannelLabelSubDescriptor the following (ordinarily optional) properties are present: "MCA Tag Name", "MCA Channel ID".
        
        In each AudioChannelLabelSubDescriptor the following (ordinarily optional) properties are not present: "RFC 5646 Spoken Language".
        
        In each SoundfieldGroupLabelSubDescriptor the following (ordinarily optional) properties are present: "MCA Tag Name", "RFC 5646 Spoken Language".
        
        In each SoundfieldGroupLabelSubDescriptor the following (ordinarily optional) properties are not present: "MCA Channel ID".
        
        In each GroupOfSoundfieldGroupsLabelSubDescriptor the following (ordinarily optional) properties are present: "MCA Tag Name".
        
        In each GroupOfSoundfieldGroupsLabelSubDescriptor the following (ordinarily optional) properties are not present: "MCA Channel ID", "RFC 5646 Spoken Language".
        
        Implementation Notes
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/E6/
        
        Distribution and Repetition of SubDescriptors
        
        SoundfieldGroupLabelSubDescriptors and GroupOfSoundfieldGroupsLabelSubDescriptors could all be on one Sound Track or distributed. Hence, even the GroupOfSoundfieldGroupsLabelSubDescriptors might not be on the same Sound Track.
        
        If several Soundfield Groups reference a single Group of Soundfield Groups then there will be more than one GroupOfSoundfieldGroupsLabelSubDescriptor for that Group of Soundfield Groups. That is, it is repeated for each Soundfield Group that references it.
        
        Type of RFC5646SpokenLanguage property
        
        The value of this property is encoded as a US-ASCII string with one byte per character.
        
        Details:
        
        The RFC5646SpokenLanguage property of the {MCALabelSubDescriptor} is defined in SMPTE ST 377-4:2012 as having the type "ISO-8String". This type is undefined.
        
        However, the entry for RFC5646SpokenLanguage in the SMPTE Elements Register correctly lists the type as "ISO7", which refers to "ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for information interchange.". That is the same character repertoire referenced by IETF RFC 5646.
      - The value of Default Audio Layout defines any static properties of Audio Channels and Sound Tracks in the file.
      - Channel Assignment Signalling
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/ChannelAssignmentSignalling/
        
        There are different ways of signalling channel assignment depending on the format of the audio. For example:
        
        PCM uses the "ChannelAssignment" property of the {WAVEPCMDescriptor} Sound Essence Descriptor
        
        AAC uses the "MPEGAudioChannelAssignment" property of the {MPEGAudioDescriptor} Sound Essence Descriptor
    - Audio Layout Mode 0
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/ALM0/
      - Channel Assignment Label is ConstrainedMultichannelAudioLabelingFramework(Label).
        
        ConstrainedMultichannelAudioLabelingFramework(Label)
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/CA_L0/
        
        SMPTE Metadata Registers – Labels
        Kind UL Symbol Definition
        LEAF urn:smpte:ul:060e2b34.04010101.0d010801.02010000 ConstrainedMultichannelAudioLabelingFramework Identifies a specific application of the MXF Multichannel Audio Framework
        View the SMPTE Metadata Registers XML file(s):
        specification_data_files/www.amwa.tv_c0f7b64/block/CA_L0/artefacts/Labels.xml
        
        SMPTE Registers Node: SoundChannelLabeling
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/SoundChannelLabeling/
        
        SMPTE Metadata Registers – Labels
        Kind UL Symbol Definition
        NODE urn:smpte:ul:060e2b34.04010101.0d010801.02000000 SoundChannelLabeling
        View the SMPTE Metadata Registers XML file(s):
        specification_data_files/www.amwa.tv_c0f7b64/note/SoundChannelLabeling/artefacts/Labels.xml
      - MCA Labeling Present is "true".
      - Default Audio Layout is not set (no assumptions can be made about audio layout).
    - Extra Audio Layout Modes
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/param1/
      - This is a Parameter Key Block – its value is set by the Parameter Value Block Extra Audio Layout Modes
  - If Constrained Multichannel Audio Labeling Framework is used then any device or system that reads, writes or otherwise processes the file supports Labels for use in Multichannel Audio Labeling Framework.
    - Constrained Multichannel Audio Labeling Framework
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/SN2/
      - The file uses the Multichannel Audio Labeling Framework specified in SMPTE ST 377-4:2012.
      - There is exactly one AudioChannelLabelSubDescriptor for each Audio Channel. This AudioChannelLabelSubDescriptor is strongly referenced by the "SubDescriptors" property of the Generic Sound Essence Descriptor of the Sound Track that contains the Audio Channel.
      - There is exactly one SoundfieldGroupLabelSubDescriptor for each Soundfield Group. This SoundfieldGroupLabelSubDescriptor is strongly referenced by the "SubDescriptors" property of the Generic Sound Essence Descriptor of a Sound Track in the Soundfield Group.
      - There is one or more GroupOfSoundfieldGroupsLabelSubDescriptor(s) for each Soundfield Group. Each of these GroupOfSoundfieldGroupsLabelSubDescriptors is strongly referenced by the "SubDescriptors" property of the Generic Sound Essence Descriptor of a Sound Track in the Soundfield Group.
      - Each AudioChannelLabelSubDescriptor references exactly one SoundfieldGroupLabelSubDescriptor.
      - Each SoundfieldGroupLabelSubDescriptor references all of the GroupOfSoundfieldGroupsLabelSubDescriptor(s) for the Soundfield Group it relates to.
      - In each AudioChannelLabelSubDescriptor the following (ordinarily optional) properties are present: "MCA Tag Name", "MCA Channel ID".
      - In each AudioChannelLabelSubDescriptor the following (ordinarily optional) properties are not present: "RFC 5646 Spoken Language".
      - In each SoundfieldGroupLabelSubDescriptor the following (ordinarily optional) properties are present: "MCA Tag Name", "RFC 5646 Spoken Language".
      - In each SoundfieldGroupLabelSubDescriptor the following (ordinarily optional) properties are not present: "MCA Channel ID".
      - In each GroupOfSoundfieldGroupsLabelSubDescriptor the following (ordinarily optional) properties are present: "MCA Tag Name".
      - In each GroupOfSoundfieldGroupsLabelSubDescriptor the following (ordinarily optional) properties are not present: "MCA Channel ID", "RFC 5646 Spoken Language".
      - Implementation Notes
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/E6/
        
        Distribution and Repetition of SubDescriptors
        
        SoundfieldGroupLabelSubDescriptors and GroupOfSoundfieldGroupsLabelSubDescriptors could all be on one Sound Track or distributed. Hence, even the GroupOfSoundfieldGroupsLabelSubDescriptors might not be on the same Sound Track.
        
        If several Soundfield Groups reference a single Group of Soundfield Groups then there will be more than one GroupOfSoundfieldGroupsLabelSubDescriptor for that Group of Soundfield Groups. That is, it is repeated for each Soundfield Group that references it.
        
        Type of RFC5646SpokenLanguage property
        
        The value of this property is encoded as a US-ASCII string with one byte per character.
        
        Details:
        
        The RFC5646SpokenLanguage property of the {MCALabelSubDescriptor} is defined in SMPTE ST 377-4:2012 as having the type "ISO-8String". This type is undefined.
        
        However, the entry for RFC5646SpokenLanguage in the SMPTE Elements Register correctly lists the type as "ISO7", which refers to "ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for information interchange.". That is the same character repertoire referenced by IETF RFC 5646.
    - Labels for use in Multichannel Audio Labeling Framework
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/param4/
      - This is a Parameter Key Block – its value is set by the Parameter Value Block Labels for use in Multichannel Audio Labeling Framework
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E40/
    - "MCA Label Dictionary ID" Labels Used
      
      Note that no constraint is placed on which "MCA Label Dictionary ID" Labels can be used in the file. The stated constraint simply means that implementations that comply with this Block must be able to support all of the specified Labels. In practice this means that for most real Sound Tracks the specified Labels ought to be used but alternative Labels can be used if the need arises (for example to support the delivery of additional specialist Sound Tracks for which Labels have been privately agreed between the supplier and the broadcaster).
- Implementation Notes
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/note/E60/
  - Multichannel Audio Labeling Framework
    
    Each Sound Track will have:
    - one AudioChannelLabelSubDescriptor for each of its Audio Channels
    - one SoundfieldGroupLabelSubDescriptor
    - one or more GroupOfSoundfieldGroupsLabelSubDescriptors
    If two (or more) Soundfield Groups belong to the same Group of Soundfield Groups then the GroupOfSoundfieldGroupsLabelSubDescriptor will be repeated on each Sound Track that uses it.
Embedded XML Documents
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/DM0_r001/
- Each XML document identified by List of Embedded XML Documents is embedded in the file using XML Document in Header Metadata Carriage.
  - List of Embedded XML Documents
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/block/param0/
    - This is a Parameter Key Block – its value is set by the Parameter Value Block List of Embedded XML Documents
    - Lists XML documents to be embedded, defined in terms of:
      
      the namespace of the document's root element
      
      the name of the document's root element
      
      a Media type (MIME type) for the document
  - XML Document in Header Metadata Carriage
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/block/XML0/
    - The XML document is a complete XML document (with a single root element) that is UTF-8 encoded without a "Byte-Order Mark" (BOM).
    - The XML document is carried in the Header Metadata according to SMPTE RP 2057:2011.
    - The instance of "Text-Based DM Framework" is strongly referenced from a Constrained Static DM Track.
      - Constrained Static DM Track
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/056/
        
        A Constrained Static DM Track is a Static Track (DM) in the Material Package that contains a Sequence, which contains exactly one DM Segment, which strongly references an instance of a DM Framework.
        
        Track Name
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/039/
        
        The "Track Name" property of an Constrained Static DM Track does not identify the DM Scheme whose DM Framework it references. In the absence of other requirements for "Track Name", it is suggested that files use a value corresponding to the DM Scheme used in the track, e.g. "AS_11_Core", "AS_11_UKDPP".
    - The XML document is carried in the "UTF-8 Text Data" property of the "UTF-8 Text-based Set".
    - In the "UTF-8 Text-based Set" the property "Text-based Metadata Payload Scheme ID" has the value of DM_XML_Document.
      - DM_XML_Document
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/XMLDMLabel/
        
        SMPTE Metadata Registers – Labels
        Kind UL Symbol Definition
        LEAF urn:smpte:ul:060e2b34.04010101.0d010801.04010000 DM_XML_Document Descriptive Metadata XML Document in Header Metadata
        View the SMPTE Metadata Registers XML file(s):
        specification_data_files/www.amwa.tv_c0f7b64/block/XMLDMLabel/artefacts/Labels.xml
        
        SMPTE Registers Node: MetadataPayloadSchemes
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/MetadataPayloadSchemes/
        
        SMPTE Metadata Registers – Labels
        Kind UL Symbol Definition
        NODE urn:smpte:ul:060e2b34.04010101.0d010801.04000000 MetadataPayloadSchemes
        View the SMPTE Metadata Registers XML file(s):
        specification_data_files/www.amwa.tv_c0f7b64/note/MetadataPayloadSchemes/artefacts/Labels.xml
    - In the "UTF-8 Text-based Set" the property "Text Data Description" is present and has a value equal to the namespace of the root element of the XML document.
    - 2-byte Local Length Encoding is used for both the "Text-Based DM Framework" and the "UTF-8 Text-based Set".
    - ST 2057 Implementation Notes
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/E9/
      - XML Document size limits
        
        The constraints mean that Byte 6 of the two set keys will be 53h. The amount of text data must be equal to or less than 65535 bytes.
        
        Amendment
        
        A crucial amendment to ST 2057 exists and must be read carefully -- it changes the ULs of various keys used in the Standard.
- For each of these embedded XML documents, the "UTF-8 Text-based Set" that carries it is uniquely identified within the sets_in_scope by the value of its "Text Data Description" property; where sets_in_scope consists of all the instances of "Text-based Object" (as defined by SMPTE RP 2057:2011) present in the Material Package that have a value of DM_XML_Document for the "Text-based Metadata Payload Scheme ID" property.
  - DM_XML_Document
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/block/XMLDMLabel/
    - SMPTE Metadata Registers – Labels
      Kind UL Symbol Definition
      LEAF urn:smpte:ul:060e2b34.04010101.0d010801.04010000 DM_XML_Document Descriptive Metadata XML Document in Header Metadata
      View the SMPTE Metadata Registers XML file(s):
      specification_data_files/www.amwa.tv_c0f7b64/block/XMLDMLabel/artefacts/Labels.xml
    - SMPTE Registers Node: MetadataPayloadSchemes
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/MetadataPayloadSchemes/
      - SMPTE Metadata Registers – Labels
        Kind UL Symbol Definition
        NODE urn:smpte:ul:060e2b34.04010101.0d010801.04000000 MetadataPayloadSchemes
        View the SMPTE Metadata Registers XML file(s):
        specification_data_files/www.amwa.tv_c0f7b64/note/MetadataPayloadSchemes/artefacts/Labels.xml
- Other Text/XML Documents can also be Embedded
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/note/E82/
  - This Block does not prohibit other text documents (XML or otherwise) from also being embedded in the MXF file. This could be useful because it allows custom XML documents also to be carried along with the mandated XML document(s).
    
    Note that the stated constraints help readers in identifying the mandated XML document(s); if a device examines all sets / objects that meet all of the following criteria:
    - it is an instance of a "Text-based Object" (so it is a "Generic Stream Text-based Set", "UTF-8 Text-based Set" or "UTF-16 Text-based Set")
    - it is in the Material Package
    - the "Text-based Metadata Payload Scheme ID" property has the specified value
    then the set / object containing a specific mandated XML document can be uniquely identified by the value of its "Text Data Description" property (this property contains the namespace of the root element of the XML document).

Kind	UL	Symbol	Definition
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.02010000	ConstrainedMultichannelAudioLabelingFramework	Identifies a specific application of the MXF Multichannel Audio Framework

Kind	UL	Symbol	Definition
NODE	urn:smpte:ul:060e2b34.04010101.0d010801.02000000	SoundChannelLabeling

Kind	UL	Symbol	Definition
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.04010000	DM_XML_Document	Descriptive Metadata XML Document in Header Metadata

Kind	UL	Symbol	Definition
NODE	urn:smpte:ul:060e2b34.04010101.0d010801.04000000	MetadataPayloadSchemes

Kind	UL	Symbol	Definition
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.04010000	DM_XML_Document	Descriptive Metadata XML Document in Header Metadata

Kind	UL	Symbol	Definition
NODE	urn:smpte:ul:060e2b34.04010101.0d010801.04000000	MetadataPayloadSchemes

AS-11 Segmentation DM (Descriptive Metadata)

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/530/
The file contains exactly one Program Segmentation Track.
- Program Segmentation Track
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/532/
  - A Program Segmentation Track is a Timeline Track that contains a Sequence that is composed of zero or more Filler objects and one or more DM Segment objects.
  - Each DM Segment object in the Program Segmentation Track represents, and aligns with, a region of program content in the Source Essence.
  - Each Filler object in the Program Segmentation Track represents, and aligns with, a region of non-program content in the Source Essence.
  - Track Name
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/038/
    - The "Track Name" property of the Program Segmentation Track does not identify the segmentation metadata scheme. In the absence of other requirements for "Track Name", it is suggested that files use a value corresponding to the DM Scheme used in the track, e.g. "AS_11_Segmentation".
  - Determining SOM and EOM
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/040/
    - The start and end timecodes for program regions, commonly referred to as "start of material" (som) and "end of material" (eom), can be determined based on the location of DM Segment objects on the Program Segmentation Track relative to the adjacent Timecode Track in the Material Package that contains the Program Segmentation Track.
  - Non-Programme Content
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/048/
    - Examples of non-programme content include: black, ident, clock.
This Track is in the Material Package.

Each DM Segment object in the Track strongly references an instance of DM_AS_11_Segmentation.

DM_AS_11_Segmentation

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/505S/

This DM Scheme is identified by DM_AS_11_Segmentation (the DM Scheme Label) and has the following members: DM_AS_11_Segmentation_Framework (the DM Framework).

DM_AS_11_Segmentation
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/505L/
- SMPTE Metadata Registers – Labels
  Kind UL Symbol Definition
  LEAF urn:smpte:ul:060e2b34.04010101.0d010701.0b020000 DM_AS_11_Segmentation AS-11 segmentation metadata scheme
  View the SMPTE Metadata Registers XML file(s):
  - specification_data_files/www.amwa.tv_c0f7b64/block/505L/artefacts/Labels.xml

Kind	UL	Symbol	Definition
LEAF	urn:smpte:ul:060e2b34.04010101.0d010701.0b020000	DM_AS_11_Segmentation	AS-11 segmentation metadata scheme

DM_AS_11_Segmentation_Framework

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/505F/

Framework / Group

UL: urn:smpte:ul:060e2b34.027f0101.0d010701.0b020100

Symbol: DM_AS_11_Segmentation_Framework

Properties / Elements in the Framework:

UL	Symbol	Definition	Type Symbol	Is Optional	Restrictions
urn:smpte:ul:060e2b34.01010101.0d010701.0b020101	AS_11_Part_Number	A number that both: uniquely identifies the part / segment within the programme; and identifies the position of the part / segment within the programme.	UInt16	false
urn:smpte:ul:060e2b34.01010101.0d010701.0b020102	AS_11_Part_Total	The count of parts / segments in the entire programme.	UInt16	false

View the SMPTE Metadata Registers XML file(s):

Implementation Notes
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/049_r001/
- The Track can be identified by an MXF reader by the presence of DM Segment objects that each strongly reference an instance of the "DM_AS_11_Segmentation_Framework" DM Framework.
- As the Track is in the Material Package, it is necessarily full from start to finish and is the same length as all other Timeline Tracks in the Material Package.
Repetition of Header Metadata
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/051/
- Repetition of Header Metadata in the Footer Partition is not considered to be another instance of any of the components of that Header Metadata.

Specification Identification

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/SpecID_1/

The Specification_Identifiers Element is present in the Preface of the Header Partition.

Specification_Identifiers

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/SpecID/

SMPTE Metadata Registers – Elements

Kind	UL	Symbol	Definition	Type Symbol	Restrictions
LEAF	urn:smpte:ul:060e2b34.01010101.0d010801.01010000	Specification_Identifiers	A set of AUIDs where each AUID identifies a "file format" "Block" to which the MXF file conforms. A "file format" "Block" is a "Block" (a Rules Framework Component) that is usually at (or close to) the root of a Rules-based Specification.	AUIDSet

View the SMPTE Metadata Registers XML file(s):

SMPTE Registers Node: Specification_Identification (Elements Register)
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/Specification_Identification_E/
- SMPTE Metadata Registers – Elements
  Kind UL Symbol Definition Type Symbol Restrictions
  NODE urn:smpte:ul:060e2b34.01010101.0d010801.01000000 Specification_Identification
  View the SMPTE Metadata Registers XML file(s):
  - specification_data_files/www.amwa.tv_c0f7b64/note/Specification_Identification_E/artefacts/Elements.xml

The value of this Element includes the Label Blocks_FF_0 and the Label(s) specified by File Format Specification Identification Label.
- Blocks_FF_0
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/SpecID_L0/
  - SMPTE Metadata Registers – Labels
    Kind UL Symbol Definition
    LEAF urn:smpte:ul:060e2b34.04010101.0d010801.05010000 Blocks_FF_0 Blocks File Format 0
    View the SMPTE Metadata Registers XML file(s):
    - specification_data_files/www.amwa.tv_c0f7b64/block/SpecID_L0/artefacts/Labels.xml
  - SMPTE Registers Node: Specification_Identification (Labels Register)
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/Specification_Identification_L/
    - SMPTE Metadata Registers – Labels
      Kind UL Symbol Definition
      NODE urn:smpte:ul:060e2b34.04010101.0d010801.05000000 Specification_Identification
      View the SMPTE Metadata Registers XML file(s):
      specification_data_files/www.amwa.tv_c0f7b64/note/Specification_Identification_L/artefacts/Labels.xml
- File Format Specification Identification Label
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/param3/
  - This is a Parameter Key Block – its value is set by the Parameter Value Block File Format Specification Identification Label

Dolby Audio Metadata (Optional)
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/DAM/
- The Dolby E Audio Metadata Serial Bitstream that describes an Audio Program is included in the file using Dolby E Audio Metadata Serial Bitstream Carriage.
  - Dolby E Audio Metadata Serial Bitstream Carriage
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/block/400/
    - The mapping of a Dolby E Audio Metadata Serial Bitstream into VANC Data Packets conforms to SMPTE 2020-B.
    - The mapping of VANC Data Packets into ANC Frame Elements is as specified in Constrained Ancillary Data Mapping.
      - Constrained Ancillary Data Mapping
        
        Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/402/
        
        The mapping of VANC Data Packets into ANC Frame Elements is as specified in SMPTE ST 436-1:2013 where "Payload Sample Coding" is "8-bit luma samples" (04h) and "Wrapping Type" is: "VANC Frame" (01h) (for interlaced or segmented progressive Picture Essence) or "VANC Progressive Frame" (04h) (for full-frame progressive Picture Essence).
    - The "Line Number" used for each field's VANC Data Packet in the ANC Frame Element is the same for all VANC Data Packets for that field for the identified Audio Program.
    - Implementation Notes
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/note/E2/
      - Use of Dolby E Audio Metadata Serial Bitstream Carriage
        
        The file can use Dolby E Audio Metadata Serial Bitstream Carriage to carry audio presentation metadata for zero, one or more than one SoundfieldGroups / Audio Programs.
        
        SDID value
        
        SMPTE ST 2020-1 specifies that the SDID value within the VANC Data Packet be used to identify the Sound Tracks that make up the Audio Program. For example, VANC Data Packets that contain Dolby E Audio Metadata Serial Bitstream for a 5.1 channel Audio Program starting at channel pair 5/6 will require the SDID value in the VANC Data Packet to be set to 04h.
        
        However, this approach only works inside an MXF file if every Audio Channel in the file is identifiable using a pan-file channel number. This is the case if, for example, the Sound Tracks in the MXF file are numbered mono Sound Tracks.
        
        However, if the Sound Tracks in the MXF file are Multichannel Sound Tracks then this approach does not work. Some consequences of this:
        
        The value to be used for SDID is undefined.
        
        If more than one 5.1 SoundfieldGroup (and at least one Dolby E Audio Metadata Serial Bitstream) is included in the file then an external mechanism is needed to relate SoundfieldGroups and Dolby E Audio Metadata Serial Bitstreams.
        
        The SDID values might need to be rewritten upon output so that they correctly identify the Audio Channels that are being used to carry the relevant SoundfieldGroup / Audio Program. For example, this might be the case when playing out an MXF file to SDI -- particularly if only certain audio is played out or the audio layout is changed.
        
        DID value
        
        VANC Data Packets that are carrying Dolby E Audio Metadata Serial Bitstream will have a DID value of 45h.
        
        Packets are not constant throughout
        
        SMPTE 2020-B requires that there is "one packet in each field of interlaced video formats". However, the two packets in each interlaced video frame are not identical.
        
        The values of SMPTE RDD 6 metadata properties might change from one frame to the next, but normally they will not. However, the VANC Data Packets in the file will not be identical even if the metadata is static: the "frame_count" will certainly increment and the "description_text" (if not null) will change.
        
        Other data being carried in the ANC Frame Element
        
        The ANC Frame Element can also contain HANC Data Packets and other VANC Data Packets in addition to those carrying Dolby E Audio Metadata Serial Bitstreams. Irrespective of what data is carried in the ANC Frame Element, there is only ever one Track (in each of the Material Package and Top-Level File Package), one Data Element, and one associated Essence Descriptor in the MXF file.
Timecode constraints
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/TT0_r001/
- Timecode Track Presence
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/280/
  - The Material Package contains exactly one Timecode Track.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/021/
    - This Timecode Track provides "Synthetic Timecode" because its Timecode is "generated" from a single "Start Timecode" value that is associated with the beginning of the Material Package. This means that the Timecode is necessarily continuous throughout the entire playback of the MXF file.
- Constrained Timecode Track in Material Package
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/TTC_MP/
  - The Timecode Track in the Material Package is a Constrained Timecode Track.
    - Constrained Timecode Track
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/TTC/
      - A Constrained Timecode Track is a Timecode Track.
      - The value of the "Edit Rate" property of this Timecode Track is the same as the value of the "Edit Rate" property of the Picture Track in the same Package.
      - There is exactly one Timecode Component in this Timecode Track.
      - The value of the "Rounded Timecode Base" property of the Timecode Component is the "Edit Rate" of this Timecode Track rounded to the nearest integer.
- Timecode mode signalling
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/DF/
  - The value of the "Drop Frame" property of the Timecode Component in the Timecode Track in the Material Package is "False" (indicating non-drop frame timecode is in use) except in any of the following scenarios (in which case it is "True", indicating drop frame timecode is in use):
    - The "Rounded Timecode Base" property of the Timecode Component is 60 and the "Edit Rate" of the Timecode Track is mathematically equal to 60000/1001
    - The "Rounded Timecode Base" property of the Timecode Component is 30 and the "Edit Rate" of the Timecode Track is mathematically equal to 30000/1001
  - Rational Numbers
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E69/
    - Care must be taken when dealing with numbers expressed as a ratio of two integers ("rationals"). They are often used to represent temporal rates or image aspect ratios.
      
      When making comparisons of these values, it is insufficient to simply compare each of the numerators and each of the denominators. For example, 7/5 is mathematically equal to 14/10.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E81/
    - Note that for an "Edit Rate" of 24000/1001 the "Drop Frame" property will be "False" because drop frame timecode is not applicable to this rate.
- Timecode Track Precedence
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/290/
  - The Timecode Track in the Material Package defines the authoritative program timecode.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/022/
    - The Timecode defined by the Timecode Track in the Material Package must be used by all the components of a system that handles the file. Other Timecodes could be present in the file but these are not authoritative -- these other Timecodes could be used by certain systems for very specialist purposes (such as keeping track of where each frame of content originated from) but they must never be used as the authoritative / principal Timecode for the content.
Implementation Notes
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/implementation4/
- Essence Container Label
  
  The stated constraints mean that the <Essence Container Label> used to identify the <Picture Essence> mapping is always urn:smpte:ul:060e2b34.0401010a.0d010301.02106001 (MXFGCAVCByteStreamWithVideoStream0SIDFrameWrapped)

List of Embedded XML Documents
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/param_link_0/
- This is a Parameter Value Block – it sets the value of the Parameter Key Block List of Embedded XML Documents
- XML DM for Programmes
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/XML_DM_Programmes/
  - The namespace of the document's root element is Programmes Descriptive Metadata; the name of the document's root element is "Programmes_DM"; the Media type (MIME type) for the document is "application/xml"
    - Programmes Descriptive Metadata
      - Component metadata
        
        ID: http://www.amwa.tv/projects/rules/01/block/DM_Programmes/
      - XML Schema
        View the HTML Documentation for the XML Schema
        View the primary XML Schema file:
        specification_data_files/www.amwa.tv_c0f7b64/block/DM_Programmes/artefacts/DM_Programmes.xsd
        View the imported XML Schema file(s):
        specification_data_files/www.amwa.tv_c0f7b64/block/DM_Programmes/artefacts/import/DM_Identification.xsd
        specification_data_files/www.amwa.tv_c0f7b64/block/DM_Programmes/artefacts/import/DM_Programmes_DomainSpecific.xsd
        specification_data_files/www.amwa.tv_c0f7b64/block/DM_Programmes/artefacts/import/DM_InVisionAccessServices.xsd
        specification_data_files/www.amwa.tv_c0f7b64/block/DM_Programmes/artefacts/import/DM_ContentDetails.xsd
        specification_data_files/www.amwa.tv_c0f7b64/block/DM_Programmes/artefacts/import/DM_Common.xsd
        specification_data_files/www.amwa.tv_c0f7b64/block/DM_Programmes/artefacts/import/DM_Extras.xsd
Picture Essence Constraints
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/param_link_1/
- This is a Parameter Value Block – it sets the value of the Parameter Key Block Picture Essence Constraints
- RP 2027 Class 100 Picture Essence at 1080i25 with 10 bit samples
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/PE1/
  - The Picture Essence conforms to SMPTE RP 2027:2012 where: "Class" is "100"; "Television system" is "1080 line system"; "Frame Frequency" is "50i"; "The sequence parameter set and the picture parameter set shall be placed after the access unit delimiter at the beginning of every coded frame".
  - Each sample in each plane (chroma and luma) in the decoded Picture Essence has 10 bits.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/003/
    - Decoders must be able to play files that omit private SEI messages from the H.264 bitstream.
      
      Decoders must apply the parameters in the sequence parameter set and picture parameter set.
      
      With these encoding parameters the coded frame size will be 568832 bytes, including the coded frame, sequence parameter set, picture parameter set, SEI messages and/or padding for SEI messages.
      
      The decoded video always has 1080 lines, regardless of any MXF Descriptor property values.
      
      The term "Frame Frequency" is used as a heading in Table 5.2 in SMPTE RP 2027:2012, but for "50i" it is the "Field Frequency". This term is used later on in Section 5.3.
File Format Specification Identification Label
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/block/param_link_2/
- This is a Parameter Value Block – it sets the value of the Parameter Key Block File Format Specification Identification Label
- Blocks_FF_2
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/SpecID_L2/
  - SMPTE Metadata Registers – Labels
    Kind UL Symbol Definition
    LEAF urn:smpte:ul:060e2b34.04010101.0d010801.05030000 Blocks_FF_2 Blocks File Format 2
    View the SMPTE Metadata Registers XML file(s):
    - specification_data_files/www.amwa.tv_c0f7b64/block/SpecID_L2/artefacts/Labels.xml

Kind	UL	Symbol	Definition	Type Symbol	Restrictions
NODE	urn:smpte:ul:060e2b34.01010101.0d010801.01000000	Specification_Identification

Kind	UL	Symbol	Definition
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.05010000	Blocks_FF_0	Blocks File Format 0

Kind	UL	Symbol	Definition
NODE	urn:smpte:ul:060e2b34.04010101.0d010801.05000000	Specification_Identification

Kind	UL	Symbol	Definition
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.05030000	Blocks_FF_2	Blocks File Format 2

Labels for use in Multichannel Audio Labeling Framework

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/param_link_7_r003/
This is a Parameter Value Block – it sets the value of the Parameter Key Block Labels for use in Multichannel Audio Labeling Framework

Multichannel Audio Labels Collection 0

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/MCAL_Labels_Set_0_r003/

SMPTE Metadata Registers – Labels

Kind	UL	Symbol	Definition
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.01010100	AudioDescriptionStudioSignalDataChannel	Identifies an Audio Channel carrying a data signal in the format defined by BBC R&D White Paper WHP 198, intended to be used to control the fade and pan of the Main Program audio when it is being mixed with a Visually Impaired Narrative Audio Channel
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.01020100	AudioDescriptionStudioSignal	Identifies an Soundfield Group carrying a Visually Impaired Narrative Audio Channel and an Audio Description Studio Signal Data Channel - this is the two-channel Audio Description Studio Signal defined by BBC R&D White Paper WHP 198
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.01030100	AlternativeProgram	Identifies an alternative, complete audio program
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.01030200	AudioDescriptionProgramMix	Identifies a mix of the program audio with audio description audio
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.01030300	AudioDescription	Identifies a verbal description of the visual scene
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.01030400	MusicAndEffects	Identifies a mix of the Main Program with no dialogue
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.01030500	UnusedAudio	Identifies audio that is not used. The audio could be present for backward compatibility with devices and systems that require a set number of channels, beyond what is actually required to carry the content.
LEAF	urn:smpte:ul:060e2b34.0401010d.03020101.00000000	LeftAudioChannel	Identifies the Audio Channel intended to drive the Left loudspeaker
LEAF	urn:smpte:ul:060e2b34.0401010d.03020102.00000000	RightAudioChannel	Identifies the Audio Channel intended to drive the Right loudspeaker
LEAF	urn:smpte:ul:060e2b34.0401010d.03020103.00000000	CenterAudioChannel	Identifies the Audio Channel intended to drive the Center loudspeaker
LEAF	urn:smpte:ul:060e2b34.0401010d.03020104.00000000	LFEAudioChannel	Identifies the Audio Channel intended to drive the screen Low Frequency Effects loudspeaker
LEAF	urn:smpte:ul:060e2b34.0401010d.03020105.00000000	LeftSurroundAudioChannel	Identifies the Audio Channel intended to drive the Left Surround
LEAF	urn:smpte:ul:060e2b34.0401010d.03020106.00000000	RightSurroundAudioChannel	Identifies the Audio Channel intended to drive the Right Surround
LEAF	urn:smpte:ul:060e2b34.0401010d.0302010f.00000000	VisuallyImpairedNarrativeAudioChannel	A dedicated narration channel describing the main picture events for the visually impaired.
LEAF	urn:smpte:ul:060e2b34.0401010d.03020201.00000000	_51SoundfieldGroup	Identifies the 5.1 Soundfield Group
LEAF	urn:smpte:ul:060e2b34.0401010d.03020220.01000000	SMPTEST20678StandardStereo	Consists of Audio Channels L, R
LEAF	urn:smpte:ul:060e2b34.0401010d.03020320.01000000	SMPTEST20678MainProgram	Identifies SMPTE ST 2067-8 2067-8 Main Program

View the SMPTE Metadata Registers XML file(s):

specification_data_files/www.amwa.tv_c0f7b64/block/MCAL_Labels_Set_0_r003/artefacts/Labels.xml

AudioChannelLabelSubDescriptors use the SMPTE Metadata Registers Entries listed here in accordance with this table.

SMPTE Metadata Registers Symbol	MCA Tag Name	MCA Tag Symbol
`AudioDescriptionStudioSignalDataChannel`	AD Studio Signal Data Channel	`chADSSdc`
`LeftAudioChannel`	Left	`chL`
`RightAudioChannel`	Right	`chR`
`CenterAudioChannel`	Center	`chC`
`LFEAudioChannel`	LFE	`chLFE`
`LeftSurroundAudioChannel`	Left Surround	`chLs`
`RightSurroundAudioChannel`	Right Surround	`chRs`
`VisuallyImpairedNarrativeAudioChannel`	Visually Impaired Narrative	`chVIN`

⚠ The MCA Tag Name "Visually Impaired-Narrative" (with a hyphen) is used elsewhere, such as in IMF and D-Cinema.

SoundfieldGroupLabelSubDescriptors use the SMPTE Metadata Registers Entries listed here in accordance with this table.

SMPTE Metadata Registers Symbol	MCA Tag Name	MCA Tag Symbol	Constituent Audio Channels (in no particular order)
`AudioDescriptionStudioSignal`	AD Studio Signal	`sgADSS`	`chVIN` `chADSSdc`
`_51SoundfieldGroup`	5.1	`sg51`	`chL` `chR` `chC` `chLFE` `chLs` `chRs`
`SMPTEST20678StandardStereo`	Standard Stereo	`sgST`	`chL` `chR`

GroupOfSoundfieldGroupsLabelSubDescriptors use the SMPTE Metadata Registers Entries listed here in accordance with this table.

SMPTE Metadata Registers Symbol	MCA Tag Name	MCA Tag Symbol
`AlternativeProgram`	Alternative Program	`ggAPg`
`MusicAndEffects`	Music and Effects	`ggME`
`AudioDescription`	Audio Description	`ggAD`
`AudioDescriptionProgramMix`	Audio Description Program Mix	`ggADPgMx`
`SMPTEST20678MainProgram`	Main Program	`ggMPg`
`UnusedAudio`	Unused Audio	`ggUnAu`

SMPTE Registers Node: InterpretiveSoundEssence
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/InterpretiveSoundEssence/
- SMPTE Metadata Registers – Labels
  Kind UL Symbol Definition
  NODE urn:smpte:ul:060e2b34.04010101.0d010801.01000000 InterpretiveSoundEssence SMPTE Label identifiers for Sound Essence interpretive data
  View the SMPTE Metadata Registers XML file(s):
  - specification_data_files/www.amwa.tv_c0f7b64/note/InterpretiveSoundEssence/artefacts/Labels.xml
SMPTE Registers Node: AudioChannel
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/AudioChannel/
- SMPTE Metadata Registers – Labels
  Kind UL Symbol Definition
  NODE urn:smpte:ul:060e2b34.04010101.0d010801.01010000 AudioChannel SMPTE Label identifiers for Audio Channel interpretive data
  View the SMPTE Metadata Registers XML file(s):
  - specification_data_files/www.amwa.tv_c0f7b64/note/AudioChannel/artefacts/Labels.xml
SMPTE Registers Node: SoundfieldGroup
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/SoundfieldGroup/
- SMPTE Metadata Registers – Labels
  Kind UL Symbol Definition
  NODE urn:smpte:ul:060e2b34.04010101.0d010801.01020000 SoundfieldGroup SMPTE Label identifiers for Soundfield Groups interpretive data
  View the SMPTE Metadata Registers XML file(s):
  - specification_data_files/www.amwa.tv_c0f7b64/note/SoundfieldGroup/artefacts/Labels.xml
SMPTE Registers Node: GroupOfSoundfieldGroups
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/GroupOfSoundfieldGroups/
- SMPTE Metadata Registers – Labels
  Kind UL Symbol Definition
  NODE urn:smpte:ul:060e2b34.04010101.0d010801.01030000 GroupOfSoundfieldGroups SMPTE Label identifiers for Groups of Soundfield Groups interpretive data
  View the SMPTE Metadata Registers XML file(s):
  - specification_data_files/www.amwa.tv_c0f7b64/note/GroupOfSoundfieldGroups/artefacts/Labels.xml
MCA Tag Symbol prefixes
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/E26/
- The MCA Tag Symbols for labels that are used here but defined elsewhere have had prefixes applied to the values specified in their defining documents.
  
  These prefixes (ch for Audio Channel; sg for Soundfield Group; gg for Group of Soundfield Group) are also applied by the Digital Cinema and IMF applications of the Multichannel Audio Labeling framework (SMPTE ST 377-4), so this Specification uses the same MCA Tag Symbols as used in those applications.
Labels used here but defined elsewhere
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/E27/
- Some of the Labels listed here are defined elsewhere. For a full explanation of such Labels, refer to the document detailed in the DefiningDocument element for the Label in the relevant XML.
Labeling Audio Description
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/E32/
- The anticipated application of these Labels to "Audio Decsription" is as follows:
  - AudioDescription will be used with AudioDescriptionStudioSignal
  - AudioDescriptionProgramMix will be used with SMPTEST20678StandardStereo
  Other valid combinations of "Soundfield Group" and "Group of Soundfield Groups" Labels are also possible.
Unused Audio Labelling
- Component metadata
  - ID: http://www.amwa.tv/projects/rules/01/note/E80/
- The "Unused Audio" label is expected to be used when channels are part of a fixed audio layout but are not used for the program or associated content. The Audio Channel and Soundfield Group labels are still used to label the physical properties of the unused audio, but the Soundfield Group references the "Unused Audio" Group Of Soundfield Groups label to indicate the channels are unused.

Kind	UL	Symbol	Definition
NODE	urn:smpte:ul:060e2b34.04010101.0d010801.01000000	InterpretiveSoundEssence	SMPTE Label identifiers for Sound Essence interpretive data

Kind	UL	Symbol	Definition
NODE	urn:smpte:ul:060e2b34.04010101.0d010801.01010000	AudioChannel	SMPTE Label identifiers for Audio Channel interpretive data

Kind	UL	Symbol	Definition
NODE	urn:smpte:ul:060e2b34.04010101.0d010801.01020000	SoundfieldGroup	SMPTE Label identifiers for Soundfield Groups interpretive data

Kind	UL	Symbol	Definition
NODE	urn:smpte:ul:060e2b34.04010101.0d010801.01030000	GroupOfSoundfieldGroups	SMPTE Label identifiers for Groups of Soundfield Groups interpretive data

Extra Audio Layout Modes

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/param_link_8/
This is a Parameter Value Block – it sets the value of the Parameter Key Block Extra Audio Layout Modes

Permitted Extra Audio Layout Modes

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/EALM_12/

The following are permitted: Audio Layout Mode 1, Audio Layout Mode 2.

Audio Layout Mode 1

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/ALM1/

Channel Assignment Label is ConstrainedMultichannelAudioLabelingFramework_with_Default_Audio_Layout_A.

ConstrainedMultichannelAudioLabelingFramework_with_Default_Audio_Layout_A

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/CA_L1/

SMPTE Metadata Registers – Labels

Kind	UL	Symbol	Definition
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.02020000	ConstrainedMultichannelAudioLabelingFramework_with_Default_Audio_Layout_A	Identifies a specific application of the MXF Multichannel Audio Framework with default audio layout 'A'

View the SMPTE Metadata Registers XML file(s):

specification_data_files/www.amwa.tv_c0f7b64/block/CA_L1/artefacts/Labels.xml

MCA Labeling Present is "true".
Default Audio Layout is Default Audio Layout 'A'.
- Default Audio Layout 'A'
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/AL_Default_A/
  - If there is at least one Sound Track then the first one is {Stereo Main Programme} and the channels are in the following order (from first to last): left, right.
  - If there are at least two Sound Tracks then the second one is {5.1 Main Programme} and the channels are in the following order (from first to last): left, right, centre, LFE, left surround, right surround.
  - The order of Descriptors, SubDescriptors, Sound Tracks, Audio Channels and Sound Essence is consistent and as stated here.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E28/
    - All of the Sound Tracks defined by this Default Audio Layout are optional, so there could be zero Sound Tracks.
      
      Sound Tracks in this Default Audio Layout are identified by the order in which they appear.
      
      So, if you are using this Layout and want to deliver 5.1 Main Programme only (with no Stereo Main Programme) then your file will have to include two tracks, like so:
      
      first Sound Track: 2-channel (silence is advised)
      
      second Sound Track: 6-channel (5.1 Main Programme content)
      
      No mechanism is provided here for signaling that the first Sound Track does not actually contain Stereo Main Programme.
  - Reg-XML Example
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/AL_Default_A_RegXML_Example/
    - View the Reg-XML file:
      specification_data_files/www.amwa.tv_c0f7b64/note/AL_Default_A_RegXML_Example/artefacts/default_audio_layout_a_regxml.xml

Audio Layout Mode 2

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/ALM2/

Channel Assignment Label is Default_Audio_Layout_A_without_MCA_Labeling.

Default_Audio_Layout_A_without_MCA_Labeling

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/block/CA_L2/

SMPTE Metadata Registers – Labels

Kind	UL	Symbol	Definition
LEAF	urn:smpte:ul:060e2b34.04010101.0d010801.02030000	Default_Audio_Layout_A_without_MCA_Labeling	Identifies default audio layout A without use of the MXF Multichannel Audio Framework

View the SMPTE Metadata Registers XML file(s):

specification_data_files/www.amwa.tv_c0f7b64/block/CA_L2/artefacts/Labels.xml

MCA Labeling Present is "false".
Default Audio Layout is Default Audio Layout 'A'.
- Default Audio Layout 'A'
  - Component metadata
    - ID: http://www.amwa.tv/projects/rules/01/block/AL_Default_A/
  - If there is at least one Sound Track then the first one is {Stereo Main Programme} and the channels are in the following order (from first to last): left, right.
  - If there are at least two Sound Tracks then the second one is {5.1 Main Programme} and the channels are in the following order (from first to last): left, right, centre, LFE, left surround, right surround.
  - The order of Descriptors, SubDescriptors, Sound Tracks, Audio Channels and Sound Essence is consistent and as stated here.
  - Implementation Notes
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/E28/
    - All of the Sound Tracks defined by this Default Audio Layout are optional, so there could be zero Sound Tracks.
      
      Sound Tracks in this Default Audio Layout are identified by the order in which they appear.
      
      So, if you are using this Layout and want to deliver 5.1 Main Programme only (with no Stereo Main Programme) then your file will have to include two tracks, like so:
      
      first Sound Track: 2-channel (silence is advised)
      
      second Sound Track: 6-channel (5.1 Main Programme content)
      
      No mechanism is provided here for signaling that the first Sound Track does not actually contain Stereo Main Programme.
  - Reg-XML Example
    - Component metadata
      - ID: http://www.amwa.tv/projects/rules/01/note/AL_Default_A_RegXML_Example/
    - View the Reg-XML file:
      specification_data_files/www.amwa.tv_c0f7b64/note/AL_Default_A_RegXML_Example/artefacts/default_audio_layout_a_regxml.xml

Audio Layout Modes summary

Component metadata
- ID: http://www.amwa.tv/projects/rules/01/note/E14/

A summary of the {Audio Layout Mode}s available in this Specification is in the table below. Note that every MXF file must use one of the listed modes.

In all defined modes there can be between 0 and 127 (inclusive) Sound Tracks in the MXF file.

Mode Name	"Channel Assignment Label"	"MCA Labeling Present"	"Default Audio Layout"
Audio Layout Mode 0	ConstrainedMultichannelAudioLabelingFramework	true	NOT SET (no assumptions can be made)
Audio Layout Mode 1	ConstrainedMultichannelAudioLabelingFramework_with_Default_Audio_Layout_A	true	Default Audio Layout 'A'
Audio Layout Mode 2	Default_Audio_Layout_A_without_MCA_Labeling	false	Default Audio Layout 'A'

Table of Terms

Term	Explanation
2-byte Local Length Encoding	A syntax encoding for "Local Sets" that uses 2-byte Tags and 2-byte Lengths. ID: http://www.amwa.tv/projects/rules/01/term/2-byte%20Local%20Length%20Encoding/ Defined By: SMPTE ST 377-1
ANC Frame Element	A KLV triplet containing one frame's worth of an Essence Element carrying ANC packets such as VANC Data Packets. ID: http://www.amwa.tv/projects/rules/01/term/ANC%20Frame%20Element/ Defined By: SMPTE ST 436-1
Audio Channel	A distinct collection of sequenced audio samples that are intended for delivery to a single loudspeaker or other reproduction device. ID: http://www.amwa.tv/projects/rules/01/term/Audio%20Channel/ Defined By: SMPTE ST 377-4
Audio Program	A collection of one or more audio channels. ID: http://www.amwa.tv/projects/rules/01/term/Audio%20Program/ Defined By: SMPTE ST 2020-1
AudioChannelLabelSubDescriptor	A subclass of MCALabelSubDescriptor used to describe an Audio Channel. ID: http://www.amwa.tv/projects/rules/01/term/AudioChannelLabelSubDescriptor/ Defined By: SMPTE ST 377-4
AVC	Advanced Video Coding. A DCT-based video compression format. ID: http://www.amwa.tv/projects/rules/01/term/AVC/ Defined By: ITU-T Rec H.264
AVC Byte Stream Format	A format designed to enable delivery of AVC NAL units as an ordered stream of bytes or bits. ID: http://www.amwa.tv/projects/rules/01/term/AVC%20Byte%20Stream%20Format/ Defined By: ITU-T Rec H.264
Channel Assignment Label	A property of an Audio Layout Mode ID: http://www.amwa.tv/projects/rules/01/term/Channel%20Assignment%20Label/
Default Audio Layout	A property of an Audio Layout Mode ID: http://www.amwa.tv/projects/rules/01/term/Default%20Audio%20Layout/
Descriptive Metadata	Generic term used for descriptive data whose purpose is to describe Essence data. ID: http://www.amwa.tv/projects/rules/01/term/Descriptive%20Metadata/ Defined By: SMPTE ST 377-1
DM Framework	A Descriptive Metadata Class that is a Subclass of Descriptive Framework. ID: http://www.amwa.tv/projects/rules/01/term/DM%20Framework/ Defined By: SMPTE ST 377-1
DM Scheme	A mechanism for defining collections of Descriptive Metadata. ID: http://www.amwa.tv/projects/rules/01/term/DM%20Scheme/ Defined By: SMPTE ST 377-1
DM Scheme Label	An identifier for a DM Scheme. It is stored in an MXF file's Preface::DMSchemes property to signify the use of that DM Scheme in the file. ID: http://www.amwa.tv/projects/rules/01/term/DM%20Scheme%20Label/ Defined By: SMPTE ST 377-1
DM Segment	An MXF structure used to generically contain Descriptive Metadata on a Track. ID: http://www.amwa.tv/projects/rules/01/term/DM%20Segment/ Defined By: SMPTE ST 377-1
Dolby E Audio Metadata Serial Bitstream	A serial communication protocol that is used to transfer audio metadata between various products manufactured by Dolby. ID: http://www.amwa.tv/projects/rules/01/term/Dolby%20E%20Audio%20Metadata%20Serial%20Bitstream/ Defined By: SMPTE RDD 6
Edit Unit	A temporal division of a Track. ID: http://www.amwa.tv/projects/rules/01/term/Edit%20Unit/ Defined By: SMPTE ST 377-1
Essence	A bitstream comprising picture, sound or data. ID: http://www.amwa.tv/projects/rules/01/term/Essence/ Defined By: SMPTE ST 377-1
Essence Container	A part of an MXF file that carries one or more Essence streams. ID: http://www.amwa.tv/projects/rules/01/term/Essence%20Container/ Defined By: SMPTE ST 377-1
Essence Element	The entire essence stream of a single Track. ID: http://www.amwa.tv/projects/rules/01/term/Essence%20Element/ Defined By: SMPTE ST 379-2
Essence Track	A type of Track that references Essence. ID: http://www.amwa.tv/projects/rules/01/term/Essence%20Track/ Defined By: SMPTE ST 377-1
Filler	An MXF structure used to describe empty space on a Timeline Track. ID: http://www.amwa.tv/projects/rules/01/term/Filler/ Defined By: SMPTE ST 377-1
Frame Wrapping	A method for dividing and interleaving Essence Elements for each frame of Picture Essence. ID: http://www.amwa.tv/projects/rules/01/term/Frame%20Wrapping/ Defined By: SMPTE ST 379-2
Generic Container	MXF data structure used to store Essence data in an MXF file. ID: http://www.amwa.tv/projects/rules/01/term/Generic%20Container/ Defined By: SMPTE ST 379-2
Generic Sound Essence Descriptor	A Subclass of the File Descriptor. It is designed to provide generic parametric information which describes the Sound Essence. ID: http://www.amwa.tv/projects/rules/01/term/Generic%20Sound%20Essence%20Descriptor/ Defined By: SMPTE ST 377-1
Group of Soundfield Groups	A collection of one or more Soundfield Groups which all have the same program content or the same purpose. ID: http://www.amwa.tv/projects/rules/01/term/Group%20of%20Soundfield%20Groups/ Defined By: SMPTE ST 377-4
GroupOfSoundfieldGroupsLabelSubDescriptor	A subclass of MCALabelSubDescriptor used to describe a Group of Soundfield Groups. ID: http://www.amwa.tv/projects/rules/01/term/GroupOfSoundfieldGroupsLabelSubDescriptor/ Defined By: SMPTE ST 377-4
Header Metadata	MXF data structures that collectively describe the data in the Essence data in an MXF file. ID: http://www.amwa.tv/projects/rules/01/term/Header%20Metadata/ Defined By: SMPTE ST 377-1
Header Partition	The first Partition in the MXF file. This Partition always contains a copy of the Header Metadata. ID: http://www.amwa.tv/projects/rules/01/term/Header%20Partition/ Defined By: SMPTE ST 377-1
Index Table	A structure in an MXF file used to efficiently access Essence data. ID: http://www.amwa.tv/projects/rules/01/term/Index%20Table/ Defined By: SMPTE ST 377-1
Index Table Segment	A part of an Index Table. ID: http://www.amwa.tv/projects/rules/01/term/Index%20Table%20Segment/ Defined By: SMPTE ST 377-1
KLV Alignment Grid	A notional byte spacing which may be used to align KLV items within a Partition. ID: http://www.amwa.tv/projects/rules/01/term/KLV%20Alignment%20Grid/ Defined By: SMPTE ST 377-1
KLV Fill	Refers to the well-defined means of inserting empty, "fill", data in an MXF file. ID: http://www.amwa.tv/projects/rules/01/term/KLV%20Fill/ Defined By: SMPTE ST 377-1
Material Package	An MXF data structure that describes an output timeline of the file. ID: http://www.amwa.tv/projects/rules/01/term/Material%20Package/ Defined By: SMPTE ST 377-1
MCA Labeling Present	A property of an Audio Layout Mode ID: http://www.amwa.tv/projects/rules/01/term/MCA%20Labeling%20Present/
MCALabelSubDescriptor	An abstract superclass used in the Multichannel Audio Labeling Framework, derived from the MXF SubDescriptor. ID: http://www.amwa.tv/projects/rules/01/term/MCALabelSubDescriptor/ Defined By: SMPTE ST 377-4
Package	An MXF structure that aggregates one or more Tracks. ID: http://www.amwa.tv/projects/rules/01/term/Package/ Defined By: SMPTE ST 377-1
Partition	A portion of the MXF file. An MXF file consists of a sequence of Partitions. ID: http://www.amwa.tv/projects/rules/01/term/Partition/ Defined By: SMPTE ST 377-1
Picture Essence	A type of Essence containing predominantly picture data. ID: http://www.amwa.tv/projects/rules/01/term/Picture%20Essence/ Defined By: SMPTE ST 377-1
Picture Essence Descriptor	MXF technical metadata that describes the Picture Essence. ID: http://www.amwa.tv/projects/rules/01/term/Picture%20Essence%20Descriptor/ Defined By: SMPTE ST 377-1
Picture Track	A type of Essence Track that references Picture Essence. ID: http://www.amwa.tv/projects/rules/01/term/Picture%20Track/ Defined By: SMPTE ST 377-1
Preface	The root of the Strong Reference tree of the Header Metadata. ID: http://www.amwa.tv/projects/rules/01/term/Preface/ Defined By: SMPTE ST 377-1
Random Index Pack	A table that contains the byte offsets of all Partitions. ID: http://www.amwa.tv/projects/rules/01/term/Random%20Index%20Pack/ Defined By: SMPTE ST 377-1
Sequence	A Structural Metadata Class that is a Subclass of Structural Component. ID: http://www.amwa.tv/projects/rules/01/term/Sequence/ Defined By: SMPTE ST 377-1
SMPTE 2020-B	A method (sometimes known as "Method B") for mapping audio metadata into vertical ancillary data. ID: http://www.amwa.tv/projects/rules/01/term/SMPTE%202020-B/ Defined By: SMPTE ST 2020-1
Sound Essence	A type of Essence containing sound data. ID: http://www.amwa.tv/projects/rules/01/term/Sound%20Essence/ Defined By: SMPTE ST 377-1
Sound Essence Descriptor	MXF technical metadata that describes the Sound Essence. ID: http://www.amwa.tv/projects/rules/01/term/Sound%20Essence%20Descriptor/ Defined By: SMPTE ST 377-1
Sound Track	A type of Essence Track that references Sound Essence. ID: http://www.amwa.tv/projects/rules/01/term/Sound%20Track/ Defined By: SMPTE ST 377-1
Soundfield Group	A collection of Audio Channels meant to be played out simultaneously through a given Soundfield Configuration. ID: http://www.amwa.tv/projects/rules/01/term/Soundfield%20Group/ Defined By: SMPTE ST 377-4
SoundfieldGroupLabelSubDescriptor	A subclass of MCALabelSubDescriptor used to describe a Soundfield Group. ID: http://www.amwa.tv/projects/rules/01/term/SoundfieldGroupLabelSubDescriptor/ Defined By: SMPTE ST 377-4
Source Essence	Essence data referenced by a Source Package. ID: http://www.amwa.tv/projects/rules/01/term/Source%20Essence/ Defined By: SMPTE ST 377-1
Source Package	MXF data structure that describes source Essence. ID: http://www.amwa.tv/projects/rules/01/term/Source%20Package/ Defined By: SMPTE ST 377-1
Static Track (DM)	A Track carrying unchanging Descriptive Metadata. ID: http://www.amwa.tv/projects/rules/01/term/Static%20Track%20(DM)/ Defined By: SMPTE ST 377-1
Timecode	An annotation of elapsed time along a Track. ID: http://www.amwa.tv/projects/rules/01/term/Timecode/ Defined By: SMPTE ST 377-1
Timecode Component	An MXF structure that stores Timecode information. ID: http://www.amwa.tv/projects/rules/01/term/Timecode%20Component/ Defined By: SMPTE ST 377-1
Timecode Track	An MXF Track that stores one or more Timecode Components. ID: http://www.amwa.tv/projects/rules/01/term/Timecode%20Track/ Defined By: SMPTE ST 377-1
Timeline Track	A specialized MXF Track that describes a timeline by specifying an origin and rate. ID: http://www.amwa.tv/projects/rules/01/term/Timeline%20Track/ Defined By: SMPTE ST 377-1
Top-Level File Package	A Source Package that is internal to the file and which is directly referenced by a Material Package of the file. ID: http://www.amwa.tv/projects/rules/01/term/Top-Level%20File%20Package/ Defined By: SMPTE ST 377-1
Track	MXF data structure used to describe the content structure. ID: http://www.amwa.tv/projects/rules/01/term/Track/ Defined By: SMPTE ST 377-1
VANC Data Packet	An ancillary data packet in the vertical ancillary data space (VANC). ID: http://www.amwa.tv/projects/rules/01/term/VANC%20Data%20Packet/ Defined By: SMPTE ST 291-1

Table of References

Name

Information

ITU-T Rec H.264

Advanced Video Coding for Generic Audio-Visual Services

ID: http://www.amwa.tv/projects/rules/01/external_reference/ITU%20T-Rec-H.264/

SMPTE RDD 6

Description and Guide to the Use of the Dolby E Audio Metadata Serial Bitstream

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20RDD%206/

SMPTE RP 2027

AVC Intra-frame Coding Specification for SSM Card Applications

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20RP%202027/

SMPTE RP 2027:2012
AVC Intra-frame Coding Specification for SSM Card Applications http://dx.doi.org/10.5594/SMPTE.RP2027.2012 ID: http://www.amwa.tv/projects/rules/01/external_reference_revision/SMPTE%20RP%202027-2012/

SMPTE RP 2057

Text-Based Metadata Carriage in MXF

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20RP%202057/

SMPTE RP 2057:2011
Text-Based Metadata Carriage in MXF http://dx.doi.org/10.5594/SMPTE.RP2057.2011 ID: http://www.amwa.tv/projects/rules/01/external_reference_revision/SMPTE%20RP%202057-2011/

SMPTE ST 2020-1

Format of Audio Metadata and Description of the Asynchronous Serial Bitstream Transport

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20ST%202020-1/

SMPTE ST 291-1

Ancillary Data Packet and Space Formatting

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20ST%20291-1/

SMPTE ST 377-1

Material Exchange Format (MXF) — File Format Specification

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20ST%20377-1/

SMPTE ST 377-1:2011
Material Exchange Format (MXF) — File Format Specification http://dx.doi.org/10.5594/SMPTE.ST377-1.2011 ID: http://www.amwa.tv/projects/rules/01/external_reference_revision/SMPTE%20ST%20377-1-2011/

SMPTE ST 377:2004
Material Exchange Format (MXF) −− File Format Specification http://dx.doi.org/10.5594/SMPTE.ST377.2004 ID: http://www.amwa.tv/projects/rules/01/external_reference_revision/SMPTE%20ST%20377-1-2004/

SMPTE ST 377-4

MXF Multichannel Audio Labeling Framework

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20ST%20377-4/

SMPTE ST 377-4:2012
MXF Multichannel Audio Labeling Framework http://dx.doi.org/10.5594/SMPTE.ST377-4.2012 ID: http://www.amwa.tv/projects/rules/01/external_reference_revision/SMPTE%20ST%20377-4-2012/

SMPTE ST 378

MXF Operational pattern 1A (Single Item, Single Package)

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20ST%20378/

SMPTE ST 378:2004
MXF Operational pattern 1A (Single Item, Single Package) http://dx.doi.org/10.5594/SMPTE.ST378.2004 ID: http://www.amwa.tv/projects/rules/01/external_reference_revision/SMPTE%20ST%20378-2004/

SMPTE ST 379-2

MXF Generic Container

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20ST%20379-2/

SMPTE ST 381-3

Material Exchange Format—Mapping AVC Streams into the MXF Generic Container

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20ST%20381-3/

SMPTE ST 381-3:2013
Material Exchange Format—Mapping AVC Streams into the MXF Generic Container http://dx.doi.org/10.5594/SMPTE.ST381-3.2013 ID: http://www.amwa.tv/projects/rules/01/external_reference_revision/SMPTE%20ST%20381-3-2013/

SMPTE ST 382

Mapping AES3 and Broadcast Wave Audio into the MXF Generic Container

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20ST%20382/

SMPTE ST 382:2007
Mapping AES3 and Broadcast Wave Audio into the MXF Generic Container http://dx.doi.org/10.5594/SMPTE.ST382.2007 ID: http://www.amwa.tv/projects/rules/01/external_reference_revision/SMPTE%20ST%20382-2007/

SMPTE ST 436-1

MXF Mappings for VI Lines and Ancillary Data Packets

ID: http://www.amwa.tv/projects/rules/01/external_reference/SMPTE%20ST%20436-1/

SMPTE ST 436-1:2013
MXF Mappings for VI Lines and Ancillary Data Packets http://dx.doi.org/10.5594/SMPTE.ST436-1.2013 ID: http://www.amwa.tv/projects/rules/01/external_reference_revision/SMPTE%20ST%20436-1-2013/

THIS AMWA SPECIFICATION IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN PARTICULAR, ANY WARRANTY OF NON-INFRINGEMENT IS EXPRESSLY DISCLAIMED. ANY USE OF THIS SPECIFICATION SHALL BE MADE ENTIRELY AT THE IMPLEMENTER'S OWN RISK, AND NEITHER AMWA, NOR ANY OF ITS MEMBERS OR CONTRIBUTORS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY IMPLEMENTER OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER, DIRECTLY OR INDIRECTLY, ARISING FROM THE USE OF THIS SPECIFICATION.

Readers are advised that any IPR contribution forms associated with this project are available from the AMWA

[Specification (Published)] AMWA AS-11 X2 MXF Program Contribution - HD Intra

About this web page

AS-11: Media Contribution File Formats

Purpose of the AS-11 X2 Specification

Aims

Relationship to AS-11 UK DPP HD v1.1

Some notes on practical use

Understanding the Specification Blocks Tree

The Rules-Based Specification Framework

Conformance

The Specification Blocks Tree

Explanation of Essence Segmenting and Partitions

Small segments

Index Table Segment details

Partitions

Index Table Repetition

Distribution and Repetition of SubDescriptors

Type of RFC5646SpokenLanguage property

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

Distribution and Repetition of SubDescriptors

Type of RFC5646SpokenLanguage property

"MCA Label Dictionary ID" Labels Used

Multichannel Audio Labeling Framework

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

XML Document size limits

Amendment

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

Framework / Group

Properties / Elements in the Framework:

SMPTE Metadata Registers – Elements

SMPTE Metadata Registers – Elements

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

Use of Dolby E Audio Metadata Serial Bitstream Carriage

SDID value

DID value

Packets are not constant throughout

Other data being carried in the ANC Frame Element

Essence Container Label

XML Schema

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

SMPTE Metadata Registers – Labels

Table of Terms

Table of References

[Specification (Published)] AMWA AS-11 X2
MXF Program Contribution - HD Intra