1、 Copyright 2014 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue., White Plains, NY 10601 (914) 761-1100 Approved May 13, 2014 Table of Contents Page Foreword . 2 Intellectual Property 2 Introduction 2 1 Scope 3 2 Conformance Notation 3 3 Normative References 3 4 Glossary of
2、 Acronyms, Terms and Data Types 4 5 Carrying Data in the MXF Generic Container . 4 5.1 Frame Wrapping 4 5.2 Clip Wrapping . 5 5.3 Custom Wrapping 5 5.4 Element and Item Constraints 5 6 KLV Coding of Aux Data Elements . 5 6.1 Data Element Key 5 6.2 Length 6 6.3 Value 6 6.3.1 Frame Wrapped 6 7 Constra
3、ints 6 8 Label for Aux Data Essence Container Identification 6 9 Aux Data Essence Descriptor 6 10 Composition Playlist Extensions 7 10.1 Extension Elements . 7 10.2 Namespace 7 10.3 AuxData 8 10.3.1 DataEssenceCoding optional 8 11 Schema 8 12 Sample (Informative) . 9 Annex A Bibliography (Informativ
4、e) . 10 Page 1 of 10 pages SMPTE ST 429-14:2014 SMPTE STANDARD D-Cinema Packaging Aux Data Track File SMPTE ST 429-14:2014 Page 2 of 10 pages Foreword SMPTE (the Society of Motion Picture and Television Engineers) is an internationally-recognized standards developing organization. Headquartered and
5、incorporated in the United States of America, SMPTE has members in over 80 countries on six continents. SMPTEs Engineering Documents, including Standards, Recommended Practices, and Engineering Guidelines, are prepared by SMPTEs Technology Committees. Participation in these Committees is open to all
6、 with a bona fide interest in their work. SMPTE cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted in accordance with the rules given in its Standards Operations Manual. SMPTE ST 429-14 was prepared by Technology Comm
7、ittee 21DC. Intellectual Property At the time of publication no notice had been received by SMPTE claiming patent rights essential to the implementation of this Standard. However, attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. SM
8、PTE shall not be held responsible for identifying any or all such patent rights. Introduction This section is entirely informative and does not form an integral part of this Engineering Document. This document specifies a method for carrying data essence in the MXF Generic Container for use in a D-C
9、inema Package. This specification is intended to place minimal constraints on the type of data to be carried or how it is used. In order to decode data packaged using the specification, additional information will be needed. While the specification is written to allow synchronization of the data tra
10、ck with picture or sound, the synchronization mechanism is outside the scope of this document. The abbreviation “aux” is used in place of the word “auxiliary” throughout the document, but the terms are interchangeable. The term “aux” is preferred. SMPTE ST 429-14:2014 Page 3 of 10 pages 1 Scope This
11、 standard specifies the mapping of unspecified data into the Data Element of the MXF Generic Container for use within a Digital Cinema Package. The MXF Generic Container (GC) is described in SMPTE ST 379. This standard specifies the Key, the Length and the Value fields of the Aux Data Element. This
12、standard also defines the Essence Container and the Essence Descriptor. This standard defines the SMPTE ST 429-7 Composition Playlist asset type extension required for inclusion of an Aux Data track. 2 Conformance Notation Normative text is text that describes elements of the design that are indispe
13、nsable or contains the conformance language keywords: “shall“, “should“, or “may“. Informative text is text that is potentially helpful to the user, but not indispensable, and can be removed, changed, or added editorially without affecting interoperability. Informative text does not contain any conf
14、ormance keywords. All text in this document is, by default, normative, except: the Introduction, 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
15、the document and from which no deviation is permitted. The keywords, “should“ and “should not“ indicate that, among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required
16、; or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. The keywords “may“ and “need not“ indicate courses of action permissible within the limits of the document. The keyword “reserved” indicates a provision that is not defined at this time, shal
17、l not be used, and may be defined in the future. The keyword “forbidden” indicates “reserved” and in addition indicates that the provision will never be defined in the future. A conformant implementation according to this document is one that includes all mandatory provisions (“shall“) and, if imple
18、mented, all recommended provisions (“should“) as described. A conformant implementation need not implement optional provisions (“may“) and need not implement them as described. Unless otherwise specified, the order of precedence of the types of normative information in this document shall be as foll
19、ows: Normative prose shall be the authoritative definition; Tables shall be next; followed by formal languages; then figures; and then any other language forms. 3 Normative References Note: All references in this document to other SMPTE documents use the current numbering style (e.g. SMPTE ST 377:20
20、04) although, during a transitional phase, the document as published (printed or PDF) may bear an older designation (such as SMPTE 377M-2004). Documents with the same root number (e.g. 377) and publication year (e.g. 2004) are functionally identical. The following standards contain provisions which,
21、 through reference in this text, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent ed
22、ition of the standards indicated below. SMPTE ST 429-14:2014 Page 4 of 10 pages SMPTE ST 377 SMPTE ST 377:20041, Television Material Exchange Format (MXF) File Format Specification SMPTE ST 379 SMPTE ST 379:2004, Television Material Exchange Format (MXF) MXF Generic Container SMPTE ST 400 SMPTE ST 4
23、00:2012, SMPTE Labels Structure SMPTE ST 429-3 SMPTE ST 429-3:2007, D-Cinema Packaging Sound and Picture Track File SMPTE ST 429-7 SMPTE ST 429-7:2006, D-Cinema Packaging Composition Play List SMPTE ST 2029 SMPTE ST 2029:2009, Uniform Resource Names for SMPTE Resources XML World Wide Web Consortium
24、(W3C) (2004 February 4). Extensible Markup Language (XML) 1.0 (Third Edition) XML Schema Part1: Structures World Wide Web Consortium (W3C) (2004, October 28). XML Schema Part 1: Structures (Second Edition) XML Schema Part 2: Datatypes World Wide Web Consortium (W3C) (2004, October 28). XML Schema Pa
25、rt 2: Datatypes (Second Edition) RFC 2396 Internet Engineering Task Force (IETF) (1996, November). RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax 4 Glossary of Acronyms, Terms and Data Types The general glossary of acronyms, terms and data types used in the MXF specification is given in
26、 SMPTE ST 377 and is supplemented in SMPTE ST 379. These glossaries are not repeated here to avoid any divergence of meaning. The reader is also directed to the glossary terms defined in SMPTE ST 429-7. 5 Carrying Data in the MXF Generic Container 5.1 Frame Wrapping The “Frame Wrapping“ method for d
27、ata essence is illustrated in Figure 1. Frame wrapping shall be used for the Aux Data track file. Figure 1 shows a series of data elements, each wrapped in a single Content Package Data Element with no other Generic Container Elements in the Container. Each Content Package has the duration of one ed
28、it unit. 1The reference to SMPTE ST 377:2004 and SMPTE ST 379:2004 are intentional. SMPTE ST 377-1:2011 and SMPTE ST 379-1:2009 or future versions are not appropriate for use with this document. SMPTE ST 429-14:2014 Page 5 of 10 pages 1 fr am e 1 fr am e 1 fr am e 1 fr am e 1 fr am e K L V K L V K L
29、 V K L V K L V Da ta E le m e n t Da ta E le m e n t Da ta E le m e n t Da ta E le m e n t Da ta E le m e n t Figure 1 Simple Representation of Frame Wrapping (Informative) The Frame Wrapping method enables frame by frame access by MXF applications which process at the KLV level. Sufficient Informat
30、ion is provided to allow individual frames to be identified at the KLV level without an MXF decoder having to parse or decode the Essence Data. Each data frame shall be KLV wrapped using a GC Data Element Key. 5.2 Clip Wrapping Clip wrapping shall not be used in an Aux Data track file. 5.3 Custom Wr
31、apping Custom wrapping shall not be used in an Aux Data track file. 5.4 Element and Item Constraints Only Data Elements shall be carried in an Aux Data track file. Each Data Item shall contain only a single Data Element. 6 KLV Coding of Aux Data Elements 6.1 Data Element Key The values of the first
32、12 bytes of the essence element key are defined in SMPTE ST 379, Table 2. The other bytes are defined below: Table 1 Essence Key Bytes 13-16 Byte No. Description Value (hex) Meaning 13 Item Type Identifier 17h GC Data Item 14 Essence Element Count Xx Count of Data Elements in this Generic Container
33、15 Essence Element Type 0Dh Aux Data Frame-wrapped Element 16 Essence Element Number Yy The number (used as an index) of this Data Element in this Generic Container SMPTE ST 429-14:2014 Page 6 of 10 pages 6.2 Length The length field and its application shall comply with SMPTE ST 377. 6.3 Value 6.3.1
34、 Frame Wrapped The value field shall comprise data intended to have a decoded duration of one edit unit. Data wrapped this way should be decodable as an individual edit unit. 7 Constraints The Aux Data Track file shall be constrained to comply with SMPTE ST 429-3, Sound and Picture Track file with r
35、espect to pattern, header metadata, and asset identity constraints. 8 Label for Aux Data Essence Container Identification The value for the Essence Container UL shall be as given in Table 2. Table 2 Specification of the Essence Container Label Byte No. Description Value (hex) Meaning 1-12 Defined by
36、 Generic Container 13 Essence Container Kind 02h MXF Generic Container 14 Mapping Kind 13h Aux Data 15 Content Kind 02h Aux Data Frame-wrapped Element 16 Reserved 01h The Essence Container UL is used within a batch of ULs in Partition Packs and the Preface set and on its own in the Essence Descripto
37、r. This UL value is listed in the SMPTE Label Registry. 9 Aux Data Essence Descriptor The File Descriptor sets are those structural metadata sets in the Header Metadata that describe the essence and metadata elements defined in this document. The Aux Data Essence Descriptor shall be a sub-class of t
38、he Generic Data Essence Descriptor SMPTE ST 377. File Descriptor sets shall be present in the Header Metadata for each Essence Element. Implementations that carry specific data types may extend the Aux Data Essence Descriptor using a sub-descriptor. Implementations complying with this specification
39、shall ignore unrecognized sub-descriptors. SMPTE ST 429-14:2014 Page 7 of 10 pages Table 3 Aux Data Essence Descriptor Item Name Type Len Local Tag UL Designator Req ? Meaning Default Aux Data Essence Descriptor Set UL 16 dyn 06.0E.2B.34.02.7F.01.01.0D.01.01.01.01.01.73.00 Req Defines the Data Essen
40、ce Descriptor Set (a collection of Parametric metadata) Length BER Length var Req Set length All items from the Generic Data Essence Descriptor in SMPTE ST 377 (File Format Specification Annex D.4) to be included. Data Essence Coding usage is modified as specified below. The DataEssenceCoding item s
41、hall be present in in the Aux Data Essence Descriptor. All other items use the default value as specified in SMPTE ST 377, Annex D.4. 10 Composition Playlist Extensions 10.1 Extension Elements To reference the Auxiliary Data essence in a Composition, the extension elements defined in this section sh
42、all be used to extend the Reel element of a Composition Playlist, as specified in SMPTE ST 429-7. 10.2 Namespace The AuxData extension element defined in this specification shall be associated with a unique XML namespace name that shall be the string value “http:/www.smpte-ra.org/schemas/429-14/2014
43、/Aux-Data“. This namespace name conveys both structural and semantic version information, and serves the purpose of a traditional version number field. XML namespace names used in this standard are identified in Table 4. Namespace names are represented as Uniform Resource Identifier (URI) values RFC
44、 23962. Table 4 XML Namespaces Qualifier URI cpl http:/www.smpte-ra.org/schemas/429-7/2006/CPL axd http:/www.smpte-ra.org/schemas/429-14/2014/Aux-Data URIs listed in Table 4 are normative, whereas the namespace qualifier values themselves (used in Table 4 and elsewhere in this standard) are not norm
45、ative. Thus, namespace qualifier values may be replaced in instance documents by any arbitrary XML-compliant namespace qualifier, meaning that conformant implementations shall expect any XML-compliant namespace qualifier value that is associated with a URI from Datatypes from other schemas that are
46、used in this document will be prefixed with the appropriate namespace qualifier (e.g. xs:dateTime). See XMLSchema Part 2: Datatypes for further information about these types. 2 Readers unfamiliar with URI values as XML namespace names should be aware that although a URI value begins with a “scheme“
47、element (“http“ in this case), the value is designed primarily to be a unique string and does not necessarily correspond to an actual on-line resource. Applications implementing this standard should not attempt to resolve URI values on-line. SMPTE ST 429-14:2014 Page 8 of 10 pages 10.3 AuxData The A
48、uxData extension element defines the Auxiliary Data asset intended for use with the composition. The actual data essence is contained in an external Track File. The AuxData element shall be an instance of the DataTrackFileAssetType element, which is derived from the TrackFileAssetType whose structur
49、e is defined in SMPTE ST 429-7. The element defined below replicate values contained in the underlying track file and shall remain consistent with the content of the underlying track file at all times. It is included in the Composition Playlist to alleviate the need for theater management software to access and parse individual track files when scheduling content. In the event an inconsistency exists, the values contained in the underlying tra
