1、 Copyright 2012 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved October 7, 2012 Table of Contents Page Foreword . 2 1 Scope 3 2 Descriptive vs Application Plugin Metadata 3 3 Application Plugin Schema Publication Requirements
2、. 3 4 AFD . 4 5 Picture Essence Coding Word Ordering for v210 . 5 6 VBEByteCount Semantics 6 7 Cleanup of References to SMPTE RP 210 . 7 8 Number of Picture/Sound/Data Track Sets . 7 9 Color Siting for IEC 61834 4:2:0 Essence 8 10 Index Table Layout 9 11 Header and Body Partition Pack Values . 11 12
3、 Timecode Values in Source and Material Package 12 13 Node Leaf Conformance . 12 14 Section 5 Cleanup . 13 15 Correct Orphaned References to New Versions of 379 . 13 16 AMP Scheme vs Generic Stream ID . 13 Page 1 of 13 pages Amendment 2:2012 to SMPTE ST 377-1:2011 SMPTE STANDARD Material Exchange Fo
4、rmat (MXF) File Format Specification Amendment 2 Amendment 2:2012 to SMPTE ST 377-1:2011 Page 2 of 13 pages Foreword SMPTE (the Society of Motion Picture and Television Engineers) is an internationally-recognized standards developing organization. Headquartered and incorporated in the United States
5、of America, SMPTE has members in over 80 countries on six continents. SMPTEs Engineering Documents, including Standards, Recommended Practices, Engineering Guidelines and Registered Disclosure Documents, are prepared by SMPTEs Technology Committees. Participation in these Committees is open to all w
6、ith 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 Part XIII of its Operations Manual. SMPTE Amendment 2 to SMPTE 377-1:2011 was prep
7、ared by Technology Committee 31FS. Amendment 2:2012 to SMPTE ST 377-1:2011 Page 3 of 13 pages 1 Scope The purpose of this amendment is to address various issues identified since the publication of SMPTE ST 377-1:2011. 2 Descriptive vs Application Plugin Metadata Change Section 9 (Header Metadata) fr
8、om: The Header Metadata contains Metadata Sets that define the contents of the file as a whole, including any Essence Containers. It may also describe Essence that is stored external of the file. The Header Metadata is broadly split into two categories: Structural Metadata (see Sections 9.5 and 9.6)
9、 and Descriptive Metadata (see Section 9.8). Application-Specific Metadata (see Section 9.7) can be used to extend either of the two categories. All three categories shall be encoded as a single sequence of KLV coded packets. This specification defines Structural Metadata as a single extensible sche
10、me. There shall be no other Structural Metadata schemes in MXF; i.e., there shall be no other scheme of similar or identical functionality that replaces the scheme that is defined in Section 9.5. To: (redline shows difference) The Header Metadata contains Metadata Sets which defines the contents of
11、the file as a whole, including any Essence Containers. It may also describe Essence that is stored external of the file. The Header Metadata is broadly split into two categories: Structural Metadata (see Sections 9.5 and 9.6) and Descriptive Metadata (see Section 9.8). Note: Application-Specific Met
12、adata (see Section 9.7) can be used to extend either of the two categories. However, extending Descriptive Metadata is not recommended unless the application that defines the Application Scheme is the same as the application that defines the Descriptive Metadata Scheme. All three categories shall be
13、 encoded as a single sequence of KLV coded packets. This specification defines Structural Metadata as a single extensible scheme. There shall be no other Structural Metadata schemes in MXF, i.e. there shall be no other scheme of similar or identical functionality that replaces the scheme that is def
14、ined in Section 9.5. 3 Application Plugin Schema Publication Requirements Change Section 9.7.2 (Application Metadata Scheme Specification) from: For each Application Metadata Scheme, there shall be an Application Plug-in Scheme specification. For MXF Application Metadata Schemes, the Application Plu
15、g-in Scheme specification should be an SMPTE Engineering Document. In addition to the Application Metadata Plug-In payload elements and semantics, Application Metadata Scheme specifications shall define the Application Scheme Label. For further requirements on Application Metadata Scheme specificati
16、ons, see Annex C. Amendment 2:2012 to SMPTE ST 377-1:2011 Page 4 of 13 pages To: (redline shows change) For each Application Metadata Scheme, there shall be an Application Plug-in Scheme specification. For An MXF Application Metadata Schemes, the Application Plug-in Scheme specification should be a
17、an SMPTE Engineering Documenpublic standard from an internationally accredited standards body. This is to ensure that all Application Plug-in Schemes can be used for interchange. In addition to the Application Metadata Plug-In payload elements and semantics, Application Metadata Scheme specification
18、s shall define the Application Scheme Label. For further requirements on Application Metadata Scheme specifications, see Annex C. 4 AFD Replace Annex G.2.5 with the following: Active Format Description, as defined by SMPTE ST 2016-1, describes a video picture in terms of the aspect ratio and other c
19、haracteristics of the active image within the coded frame. In general, Active Format Description can vary within a video stream, reflecting changes to the formatting of the video picture within the coded frame over time. In particular cases, Active Format Description might be constant for an individ
20、ual video clip or stream. Note 1: The SMPTE RP 210 name for the element used here in the Picture Descriptor is Active Format Descriptor, in contrast to the SMPTE ST 2016-1 term Active Format Description. For cases where the Active Format Description is constant for the duration of the essence contai
21、ner (whether encoded as MXF essence elements or embedded in the essence), then the Active Format Descriptor element may be encoded in the Picture Descriptor. For cases where the Active Format Description varies with time, the Active Format Descriptor element shall not be encoded in the Picture Descr
22、iptor. If the Active Format Description is encoded in the Picture Descriptor, then it shall be encoded if and only if it is constant in the essence container (whether encoded as MXF essence elements or embedded in the essence). If the Active Format Description is time-varying, then it should be enco
23、ded as VANC data according to SMPTE ST 2016-3 and embedded in an MXF essence container according to SMPTE ST 436. For decoders of MXF files: if the Active Format Descriptor value is encoded in the Picture Descriptor, the essence track shall be assumed to have a constant Active Format Description val
24、ue in the essence container. If the Active Format Description value is not encoded in the picture descriptor, no assumptions can be made about whether a per-frame Active Format Description value is encoded in the essence container, or whether it is constant or not. The Active Format Descriptor eleme
25、nt in the Picture Descriptor is expressed as an 8-bit unsigned integer (b7-b0) with characteristics as follows: Encoders Encoders compliant with SMPTE 377-1 shall encode b7-b0 as defined in SMPTE ST 2016-1 Table 4, where b7, b1, b0 are each 0 (reserved), b6-b3 are the AFD code data bits a3-a0, and b
26、2 is an aspect ratio bit. Note: AFD code data bits a3-a0 are defined in SMPTE ST 2016-1 Table 1. The aspect ratio (AR) bit uses value 1 to indicate 16:9 and 0 to indicate 4:3. Amendment 2:2012 to SMPTE ST 377-1:2011 Page 5 of 13 pages Decoders For decoders compliant with SMPTE 377-1: If the MXF file
27、 being read has the Version property of the Preface Set equal to 1.3 or higher: decoders shall ignore b7, decoders shall interpret b6-b3 as AFD a3a2a1a0, decoders shall interpret b2 as AR, and decoders shall ignore b1-b0. If the MXF file being read has the Version property of the Preface Set lower t
28、han 1.3 and both b6 and b5 equal 0: decoders should ignore b7, decoders should interpret b3-b0 as AFD a3a2a1a0, and decoders may interpret b4 as AR. If the MXF file being read has the Version property of the Preface Set lower than 1.3 and either b6 equals 1 or b5 equals 1: decoders should ignore b7,
29、 decoders should interpret b6-b3 as AFD a3a2a1a0, decoders should interpret b2 as AR, and decoders should ignore b1-b0. AFD code data bits a3-a0 are defined in SMPTE ST 2016-1 Table 1. The aspect ratio (AR) bit uses value 1 to indicate 16:9 and 0 to indicate 4:3. In all cases for decoders, if the As
30、pect Ratio property of the GenericPictureEssenceDescriptor Set is specified in the file being read, it shall take precedence over the AR bit. Note: It is possible that decoders compliant with SMPTE 377-1, when reading MXF files with the Version property of the Preface Set lower than 1.3, will not co
31、rrectly decode AFD codes 0000, 0010, and 0011 carried in the byte defined in SMPTE ST 2016-1 Table 4. 5 Picture Essence Coding Word Ordering for v210 For compatibility with industry practices, change the 5throw of the second table in Section G.2.25 (Picture Essence Coding) from: 06.0E.2B.34 04.01.01
32、.0A 04.01.02.01 01.02.02.01 Interleaved, 4:2:2, 10-bit component. A pattern of 10-bit components Cb, Y, Cr, Y with a 2-bit pad inserted at the start of every 32 bits. This results in a rotating pattern of three components for every 32-bits. A full rotation occurs every 6 Pixels, so the full pattern
33、is repeated (W/2)H)/3 times. The value of the Pad bits is unspecified. This layout is sometimes referred to as v210. No equivalency, although ComponentDepth=10, HorizontalSubsampling=2, VerticalSubsampling=1 may be specified. Stored Width shall be a multiple of 6. 32 bits10 bitsCr10 bits10 bitsCb Y2
34、bPadYY CbPadCbCr YPadYY CrPadAmendment 2:2012 to SMPTE ST 377-1:2011 Page 6 of 13 pages To: (graphic not redlined) 06.0E.2B.34 04.01.01.0A 04.01.02.01 01.02.02.01 Interleaved, 4:2:2, 10-bit component. A pattern of 10-bit components Cr, Y, Cb, Y with a 2-bit pad inserted at the start of every 32 bits
35、. This results in a rotating pattern of three components for every 32-bits. A full rotation occurs every 6 pixels, so the full pattern is repeated (WH)/6 times. The value of the Pad bits is unspecified. This layout is sometimes referred to as v210. No equivalency, although ComponentDepth=10, Horizon
36、talSubsampling=2, VerticalSubsampling=1 may be specified. Stored Width shall be a multiple of 48. 6 VBEByteCount Semantics Change Section 11.2.3, Table 26, VBEByteCount row, right column from: The number of bytes of Essence data in an external Essence file. To: The count of bytes of the last essence
37、 element in the last Edit Unit indexed by the Index Table Segment. Change Section 11.2.3 from: 12. In a VBE Essence Container, the value of VBEByteCount shall equal the count of bytes in the last Edit Unit indexed by the Index Table Segment starting at the first byte after the last indexed byte of E
38、ssence data until the last byte in the Edit Unit of stored Essence. The same definition shall apply when indexing an external Essence file containing VBE Essence. To: 12. If present, the value of VBEByteCount shall equal the count of bytes of the last essence element in the last Edit Unit indexed by
39、 the Index Table Segment. This definition shall apply when indexing an internal Essence Stream or an external Essence file containing VBE Essence. Replace Section 11.5.2.2 with: The format of the Essence byte stream in the external file shall be such that it could be the value of a clip-wrapped MXF
40、Essence Container. The MXF encoder shall index the Essence byte stream as if indexing the equivalent single Essence Element clip wrapped MXF Essence Container that holds the identical byte stream. If the Edit Unit Byte Count Property of an Index Table Segment is non-zero and if the Essence byte stre
41、am in the external file begins at an offset greater than zero, the ExtStartOffset shall be present and its value shall equal the offset of the beginning of the Essence byte stream in the external file. The absolute byte offset of an Edit Unit of stored Essence within the external file shall be compu
42、ted as the sum of the value of ExtStartOffset and the product of the Edit Unit Byte Count and the edit unit number. If the Edit Unit Byte Count Property of an Index Table Segment is absent or zero and if the Essence byte stream in the external file begins at an offset greater than zero, the value of
43、 ExtStartOffset shall be set to equal the offset of the beginning of the Essence byte stream in the external file. The absolute byte offset of an 32 bits10 bitsCb10 bits10 bitsCr Y2bPadYY CbPadCrCb YPadYY CrPadAmendment 2:2012 to SMPTE ST 377-1:2011 Page 7 of 13 pages Edit Unit of stored Essence wit
44、hin the external file shall be computed as the sum of the value of ExtStartOffset and the value of Stream Offset of the corresponding Index Array entry. 7 Cleanup of references to SMPTE RP 210 7.1 General Except as listed below, replace all occurrences of: “SMPTE RP 210 “ With: “Note: SMPTE RP 210 d
45、efinition “. 7.2 Specific instances that do *not* change 1. P10, “Dictionary: A list of values with defined meanings (e.g. SMPTE RP 210 metadata dictionary)“. 2. P14, “RP 210 text: The definition of a term copied from the SMPTE Dictionary RP 210 at the time of balloting this specification. This text
46、 is Informative in this document. SMPTE RP 210 remains the defining document. This text is provided where the specific text in the MXF document constrains the RP 210 definition such that the wording might appear different between the two documents.“ 3. P19, “Item UL: The UL Designator and Item Desig
47、nator portions of the UL as defined in SMPTE 336M. It defines the SMPTE Metadata Dictionary entry. The normative definition of all 16 bytes of the ULs is given by SMPTE 335M (SMPTE RP 210).“ 4. P33: “The KLV Fill item is defined in the SMPTE Metadata Dictionary (SMPTE RP 210) as 06.0e.2b.34.01.01.01
48、.02.03.01.02.10.01.00.00.00.“ 5. P134, Table at top of page, col 5: “Appropriate value from SMPTE 335M (SMPTE RP 210) or UUID defined according to the Application Metadata Scheme“ 6. P135, C.3 Row 4 Meaning column: “Appropriate value from SMPTE 335M (SMPTE RP 210) or UUID defined according to the Ap
49、plication Metadata Scheme“ 7. P136, ditto for Meaning column entries in Tables D1 and D2 8. P137, ditto for Tables E1 and E2. 9. P139 onwards., ditto for all uses in Tables F2, F3, F4.1, F4.2, F4.3, F5 and F6. 10. P181: in the Bibliography 8 Number of Picture/Sound/Data Track Sets In Annex B.18 Picture Track Sets, change the note from: Note: The number of Picture Track sets is determined by the number of editable picture tracks in the Essence Container. Amendment 2:2012 to SMPTE ST 377-1:2011 Page 8 of 13 pages To (redline show
