1、Access to Content for (SMPTE ST 2067-2:2016) (Click here to view the publication) This Page is not part of the original publication: This page has been created by IHS as a convenience to the user in order to provide access to the content as authorized by the Copyright holder of this document. Click
2、the link(s) below to access the content and use normal procedures for downloading or opening the files. SMPTE_Additional Data Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer or that a certain course of action is preferred but not necessarily re
3、quired; 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
4、, shall 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
5、 implemented, 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 a
6、s follows: 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 The following standards contain provisions which, through reference in this text, constitute provisions of thi
7、s 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 edition of the standards indicated below. SMPTE RP 224, SMPTE L
8、abels Registry SMPTE ST 330:2011, Unique Material Identifier (UMID) 1) SMPTE ST 334-1:2007, Vertical Ancillary Data Mapping of Caption Data and Other Related Data SMPTE 2067-2:2016 Page 4 of 41 pages SMPTE ST 377-1:2011, Material Exchange Format (MXF) File Format Specification SMPTE ST 377-4:2011, M
9、XF Multichannel Audio Labeling Framework SMPTE ST 382:2007, Material Exchange Format Mapping AES3 and Broadcast Wave Audio into the MXF Generic Container SMPTE ST 429-5:2009, D-Cinema Packaging Timed Text Track File SMPTE ST 429-6:2006, D-Cinema Packaging MXF Track File Essence Encryption SMPTE ST 4
10、29-8:2007, D-Cinema Packaging Packing List SMPTE ST 429-9:2014, D-Cinema Packaging Asset Mapping and File Segmentation SMPTE ST 430-2:2006, D-Cinema Operations Digital Certificate SMPTE ST 436-1:2013, MXF Mappings for VI Lines and Ancillary Data Packets 1) SMPTE ST 2001-1:2014, XML Representation of
11、 SMPTE Registered Data Mapping Rules SMPTE ST 2029:2009, Uniform Resource Names for SMPTE Resources SMPTE ST 2067-3:2016, Interoperable Master Format Composition Playlist SMPTE ST 2067-5:2013, Interoperable Master Format Essence Component Amendment 1:2016 to SMPTE ST 2067-5:2013 SMPTE ST 2067-8:2013
12、, Interoperable Master Format Common Audio Labels SMPTE ST 2067-100:2014, Interoperable Master Format Output Profile List ISO/IEC 14496-18:2004. Font Compression and Streaming Internet Engineering Task Force (IETF) (November 1996). RFC 2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Medi
13、a Types. Internet Engineering Task Force (IETF) (April 2005). RFC 4051 Additional XML Security Uniform Resource Identifiers (URIs). Internet Engineering Task Force (IETF) (July 2005). RFC 4122 A Universally Unique Identifier (UUID) URN Namespace. Internet Engineering Task Force (IETF) (May 2006). RF
14、C 4539 Media Type Registration for the Society of Motion Picture and Television Engineers (SMPTE) Material Exchange Format (MXF). Internet Engineering Task Force (IETF) (September 2009). RFC 5646 Tags for Identifying Languages. World Wide Web Consortium (W3C) (4 February 2004). Extensible Markup Lan
15、guage (XML) 1.0 (Third Edition). SMPTE 2067-2:2016 Page 5 of 41 pages World Wide Web Consortium (W3C) (21 April 2016), TTML Profiles for Internet Media Subtitles and Captions 1.0 (IMSC1) World Wide Web Consortium (W3C) (28 October 2004). XML Schema Part 1: Structures (Second Edition) World Wide Web
16、Consortium (W3C) (12 February 2002). XML Signature Syntax and Processing. 1) Note: The reference to superseded versions of these standards is intentional. Current versions were not reviewed by the Technical Committee to verify if they are appropriate for use with this document. 4 Overall 4.1 XML Sch
17、ema and Namespace XML elements defined by this specification shall conform to the XML schema definitions (see W3C XML Schema Part 1: Structures) found in this specification. In the event of a conflict between schema definitions and the prose, the prose shall take precedence. The XML schema root elem
18、ent shall be as defined in Table 1. Table 1 XML Schema root element definition 4.2 UUID Generation UUID values used by this specification shall be generated as specified in IETF RFC 4122. Unless specified otherwise, e.g. in Section 7.3.1, UUID values that identify assets or cryptographic information
19、 shall be generated using a truly-random or pseudo-random number source, and shall have a Version field value of 4 (or 0100b). Note: The b suffix on this value indicates a binary encoding, most significant bit (MSB) first. 4.3 XML Character Encoding XML documents shall use UTF-8 encoding, as specifi
20、ed in W3C Extensible Markup Language (XML). SMPTE 2067-2:2016 Page 6 of 41 pages 5 Track Files 5.1 Overall 5.1.1 Format Track Files shall conform to SMPTE ST 2067-5. 5.1.2 Shim Parameters Track Files shall be associated with the shim parameter values (see SMPTE ST 2067-5) specified in Table 2. Table
21、 2 Shim Parameter Values Definitions Shim Parameter Value Notes audio_family ST 2067-2 See Section 5.3.2 audio_file_arrangement ST 382 See Section 5.3.3 data_family CDP (ST334-1), IMSC1 See Sections 5.5 and 5.6 data_file_arrangement ST 436-1, ST429-5 See Section 5.4 and 5.5 sys_item_tc true Metadata
22、 in the System Item can be copied or moved to header metadata. partition_spacing 60s See Section 5.1.3 index_strategy_frame Follow See Section 5.1.4 Index_strategy_clip Follow See Section 5.1.4 track_tag_policy none See Section 5.3.6 ingest_TC none No dominant source of timecode during ingest is spe
23、cified. lead_TC CPL The Composition Playlist (CPL) specified in SMPTE ST 2067-3 defines a synthetic timecode Composition timeline. dropframe_tc none No constraints are specified on timecode tracks in Track File header metadata. Note: The Composition Playlist specified in SMPTE ST 2067-3 provides syn
24、chronization across the Composition timeline and timecode is not used. SMPTE 2067-2:2016 Page 7 of 41 pages The shim parameters listed in Table 3 shall be defined by individual Applications. Table 3 Shim Parameter defined by Applications Shim Parameter shim_id gc_type picture_family picture_bitrate
25、picture_format picture_custom_ANC picture_render_ANC 5.1.3 Body Partition With the exception of the last body partition, the body partitions of a frame-wrapped Track File shall occur every 606s. 5.1.4 Index tables At each partition point in a Track File, the index partition shall follow the essence
26、partition that it indexes. 5.1.5 Identification The Package UID of a given Track File shall be a basic UMID per SMPTE ST 330, having a UUID value in the material number part and a material number generation method of UUID/UL. The Package UID value shall be further constrained as follows: Byte 11 of
27、the UL portion of the UMID shall be 0Fh (unidentified material type). Byte 12 of the UL portion of the UMID shall be 20h (UUID/UL material number generation method and undefined instance number generation method). The three bytes of the instance number shall be 0 (zero). Package UID values generated
28、 in accordance with the normative provisions of this subsection will thus have the following contents in the first 16 bytes: 060a2b34h 01010105h 01010f20h 13000000h. 5.1.6 MIME Type The media type of a Track File shall be application/mxf as specified in IETF RFC 4539. 5.1.7 Origin Property The Origi
29、n Property of all Track items in the top-level File Package shall be zero. Note: When the Origin Property of a Track items in the top-level File Package is zero, the Zero Point, as defined in SMPTE ST 377-1, refers to the first Content Element in the Essence Element. SMPTE 2067-2:2016 Page 8 of 41 p
30、ages 5.1.8 Empty Essence Elements The Structural Components item of the Top-Level File Package shall not reference any Filler component, i.e., the Essence Element of the Essence Container is not empty. 5.2 Image Track Files 5.2.1 General An Image Track File shall conform to Sections 5.1 and 5.2. An
31、Image Track File primarily contains image essence. This specification does not specify the nature of the image essence. 5.2.2 Alternative Center Cut The item defined in Annex G may be present in the Generic Picture Essence Descriptor (see SMPTE ST 377-1). 5.2.3 Active Area Rectangle The items define
32、d in Annex H may be present in the Generic Picture Essence Descriptor (see SMPTE ST 377-1). 5.2.4 Essence Container Integrity The Composition Playlist (SMPTE ST 2067-3) and IMF Packing List (Section 7) allow the integrity of an entire Track File to be checked. To enable the integrity of individual i
33、mage frames to be checked, Image Track Files may conform to SMPTE ST 429-6 with the following constraints: the value of the Cipher Algorithm ID shall be 00000000.00000000.00000000.00000000 (“No cipher algorithm used“). the value of the MIC Algorithm ID shall be 060e2b34.04010107.02090202.01000000 (“
34、HMAC-SHA1 with 128-bit key“). the MIC item shall be present Plaintext Offset shall be equal to Source Length Cryptographic Key ID shall be equal to 42b5ea14-233d-415c-b7d8-8b2dbd95ad39 Cipher Key shall be equal to 0xcdea9b5a9bf00a0d564dd5ff0c19757d 5.3 Audio Track Files 5.3.1 General An Audio Track
35、File shall conform to Sections 5.1 and 5.3. An Audio Track File primarily contains audio essence. SMPTE 2067-2:2016 Page 9 of 41 pages Each Audio Track File is intended to carry a single soundfield group. If the audio that is to be carried consists of more than one soundfield group, then each is car
36、ried in its own Audio Track File(s). For example, 6+2 Music and Effects content consists of 3 Audio Track Files: one containing the “Music and Effects Main“ 5.1 Soundfield Group and two others containing each a single center channel, one for “Music and Effects Optional“ and one for “Dialog Guide“. A
37、nother example is, 6+2 Music and Effects would be carried by 8 Audio Track Files: 6 containing the “Music and Effects Main“ 5.1 Soundfield Group and two others containing each a single center channel, one for “Music and Effects Optional“ and one for “Dialog Guide. 5.3.2 Essence 5.3.2.1 General The a
38、udio essence shall consist of an audio waveform digitally sampled at regular interval into a sequence of audio samples. 5.3.2.2 Sampling Rate The sampling rate of the audio samples shall be either 48000 Hz or 96000 Hz. Note: The sampling rates specified above are absolute and specified independently
39、 of a video signal. The Composition Playlist (SMPTE ST 2067-3) provides the mechanism to synchronize audio and image essence. 5.3.2.3 Quantization Each audio sample shall be uniformly quantized as a 24-bit signed integer in the range -(223) 223 1 . Source audio uniformly quantized using signed integ
40、ers with lower bit depth, e.g. 16- or 20-bit, shall be padded in the least significant bits to create 24-bit audio samples. 5.3.3 Wrapping The audio essence within an Audio Track File shall be: clip-wrapped as a Wave Clip-Wrapped Element, as specified in SMPTE ST 382; and packed bit-by-bit as specif
41、ied by AES31-2, as specified in Section 7.2.1 of SMPTE ST 382. 5.3.4 Wave Audio Essence Descriptor 5.3.4.1 General The Top-Level File Package shall reference a Wave Audio Essence Descriptor as specified in SMPTE ST 382. The constraints specified in Table 4 shall apply. Items labeled “shall be presen
42、t” shall be present in the Wave Audio Essence Descriptor. Items labeled “shall be ignored” shall be ignored if present. SMPTE 2067-2:2016 Page 10 of 41 pages Table 4 Wave Audio Essence Descriptor Constraints Item Constraints Locked/Unlocked Shall be ignored Audio Ref Level Shall be ignored Electro-S
43、patial Formulation Shall be ignored Dial Norm Shall be ignored Channel Assignment See Section 5.3.4.2 5.3.4.2 Channel Assignment The Channel Assignment item shall be present and shall be equal to the UL specified in Table 5. Table 5 Specification of the Channel Assignment Label Byte No. Description
44、Value (hex) Meaning 1-7 Registry Designator See SMPTE ST 400 8 Registry Version Number 0Dh Version of SMPTE RP 224 in which this label first appears 9 Parametric 04h Node used to define parametric data 10 Sound Essence 02h Identifies sound essence coding 11 Sound Coding Characteristics 02h Identifie
45、s sound coding characteristics 12 Sound Channel Labeling 10h Identifies sound channel labeling 13 Sound Channel Labeling SMPTE ST2067-2 04h Identifies sound channel labeling as defined in SMPTE ST2067-2 14 Application of the MXF Multichannel Audio Framework 01h Indicates that the MXF Multichannel Au
46、dio Framework is used 15 Reserved 00h Reserved 16 Reserved 00h Reserved 5.3.5 Additional Generic Sound Essence Descriptor Items The items specified in Annex F shall be subject to the constraints specified in Table 6. SMPTE 2067-2:2016 Page 11 of 41 pages Table 6 Additional Generic Sound Essence Desc
47、riptor Items Constraints Item Constraints Reference Audio Alignment Level Should be present. Reference Image Edit Rate Should be present. See Section 6.4. Note: This is the edit rate of the picture essence to which the sound essence was conformed initially, and does not necessarily reflect the Compo
48、sition Edit Rate. 5.3.6 Multichannel Audio Labeling 5.3.6.1 General An Audio Track File shall conform to SMPTE ST 377-4. 5.3.6.2 AudioChannelLabelSubDescriptor Instances Each audio channel in an Audio Track File shall be associated with exactly one AudioChannelLabelSubDescriptor instance, and each A
49、udioChannelLabelSubDescriptor instance shall be associated with exactly one audio channel. 5.3.6.3 SoundfieldGroupLabelSubDescriptor Instances An Audio Track File shall contain exactly one SoundfieldGroupLabelSubDescriptor instance, which all AudioChannelLabelSubDescriptor instances shall reference. 5.3.6.4 GroupOfSoundfieldGroupsLabelSubDescriptor Instances An Audio Track File shall contain zero or one GroupOfSoundfieldGroupsLabelSubDescriptor. 5.3.6.5 Item Constraints Within a given Audio Track File, the constrai
