1、 The attached document is a Registered Disclosure Document prepared by the proponent identified below. It has been examined by the appropriate SMPTE Technology Committee and is believed to contain adequate information to satisfy the objectives defined in the Scope, and to be technically consistent.
2、This document is NOT a Standard, Recommended Practice or Engineering Guideline, and does NOT imply a finding or representation of the Society. Errors in this document should be reported to the proponent identified below, with a copy to engsmpte.org. All other inquiries in respect of this document, i
3、ncluding inquiries as to intellectual property requirements that may be attached to use of the disclosed technology, should be addressed to the proponent identified below. This document is intended to support the development of applications that read and process XAVC MXF files. It is not intended to
4、 support the development of hardware or software applications that create XAVC MXF files, and creation of such files is reserved to individuals and organizations that have entered into agreements with the proponent identified below for such file creation. Proponent contact information: Satoshi Katsu
5、o Sony Corporation 4-14-1 Asahi-cho, Atsugi Kanagawa, 243-0014 Japan Email: Satoshi.K Page 1 of 33 pages SMPTE RDD 32:2014 Copyright 2014 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved November 24, 2014 SMPTE REGISTERED DISCL
6、OSURE DOCUMENT XAVCTM MXF Mapping and Operating Points SMPTE RDD 32:2014 Page 2 of 33 pages Table of Contents Page 1 Scope 4 2 Related Documents 4 3 Introduction . 5 4 Outline of MXF File Structure for this Mapping 5 4.1 General 5 4.2 Single Essence Location Style 6 4.3 Multiple Essence Location Sty
7、le 6 5 AVC Picture Data and AES3 Data Mapping . 7 5.1 General . 7 5.2 Edit Unit Structure 7 5.3 System Item Mapping . 7 5.3.1 General 7 5.3.2 Overview of System Item. 7 5.3.3 System Metadata Pack 8 5.3.4 Package Metadata Set 8 5.4 Picture Item Mapping 9 5.4.1 General . 9 5.4.2 MPEG Picture Element K
8、ey 9 5.4.3 MPEG Picture Element Length . 9 5.4.4 MPEG Picture Element Value . 9 5.5 AES3 Sound Item Mapping 10 5.5.1 General . 10 5.5.2 AES3 Sound Element Key 10 5.5.3 AES3 Sound Element Length . 10 5.5.4 AES3 Sound Element Value . 10 5.6 Data Item Mapping . 10 5.6.1 General . 10 5.6.2 Acquisition M
9、etadata Set 11 6 SMPTE Labels 11 6.1 XAVC Intra Picture Essence . 11 6.2 XAVC Long GOP Picture Essence . 12 6.3 Sound Essence 12 7 Application Issues . 12 7.1 Partition Pack 12 7.2 Application of the KLV Fill Item . 13 7.3 Application of MXF structure and indexing style 13 7.3.1 Single Essence Locat
10、ion Style 14 7.3.2 Multiple Essence Location Style 15 7.4 Application of Index Table for Frame Wrapped MPEG-4 AVC Picture and AES Sound Essence 16 7.4.1 Index Table structure . 16 7.4.2 Implementation of the Set 16 Annex A UL Code List 18 Annex B Constraints of a Conformant Implementation . 20 B.1 S
11、tructure . 20 B.2 Header and BodyPartition Pack Values . 20 B.3 Essence Descriptors 20 SMPTE RDD 32:2014 Page 3 of 33 pages B.4 Identification Set Value 22 B.5 Timecode Representation in MXF Header and an Essence Container. 22 B.6 Index Table Segments . 22 B.7 Random Index Pack 22 B.8 Essence . 22 B
12、.8.1 System Item 22 B.8.2 Picture Item. 22 B.8.3 Sound Item . 23 B.8.4 Data Item 23 Annex C Operating Points. 24 C.1 XAVC Intra . 24 C.1.1 General Characteristics 24 C.1.2 XAVC HD Intra Profile 25 C.1.3 XAVC 4K Intra Profile . 26 C.2 XAVC Long GOP . 26 C.2.1 General Characteristics 26 C.2.2 XAVC HD
13、Profile 27 C.2.3 XAVC 4K Profile . 27 Annex D Property Values of the Essence Descriptors . 28 SMPTE RDD 32:2014 Page 4 of 33 pages 1 Scope This RDD specifies the MXF mapping of XAVC, i.e. MPEG-4 AVC picture, AES3 audio and ANC packets into the MXF Generic Container or MXF Constrained Generic Contain
14、er, and two types of essence location style which are compliant with the OP-1a Frame Wrapping. This document also provides the XAVC specification to support the development of applications that read and process XAVC MXF files at the specified operating points. 2 Related Documents Note: All reference
15、s in this document to other SMPTE documents use the current numbering style (e.g. SMPTE ST 326:2000) although, during a transitional phase, the document as published (printed or PDF) may bear an older designation (such as SMPTE 326M-2000). Documents with the same root number (e.g. 326) and publicati
16、on year (e.g. 2000) are functionally identical. The following standards contain provisions which, through reference in this text, constitute provisions of this document. At the time of publication, the editions indicated were valid. All documents are subject to revision, and parties to agreements ba
17、sed on this document are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. SMPTE ST 326:2000, Television SDTI Content Package Format (SDTI-CP) SMPTE ST 331:2011, Element and Metadata Definitions for the SDTI-CP SMPTE ST 377-1:2011, Materi
18、al Exchange Format (MXF) File Format Specification Amendment 2:2012 to SMPTE ST 377-1:2011 SMPTE ST 378:2004, Television Material Exchange Format (MXF) Operational pattern 1A (Single Item, Single Package) SMPTE ST 379-1:2009, Material Exchange Format (MXF) MXF Generic Container SMPTE ST 379-2:2010,
19、Television Material Exchange Format (MXF) MXF Constrained Generic Container SMPTE ST 381-2:2011, Material Exchange Format (MXF) Mapping MPEG Streams into the MXF Constrained Generic Container SMPTE ST 381-3:2013, Material Exchange Format (MXF) Mapping AVC Streams into the MXF Generic Container SMPTE
20、 ST 382:2007, Material Exchange Format Mapping AES3 and Broadcast Wave Audio into the MXF Generic Container SMPTE ST 385:2012, Material Exchange Format (MXF) Mapping SDTI-CP Essence and Metadata into the MXF Generic Container SMPTE ST 400:2012, SMPTE Labels Structure SMPTE ST 436-1:2013, MXF Mapping
21、s for VI Lines and Ancillary Data Packets SMPTE RP 210, Metadata Element Dictionary SMPTE RP 224, SMPTE Labels Register SMPTE RDD 32:2014 Page 5 of 33 pages SMPTE RP 2027:2012, AVC Intra-Frame Coding Specification for SSM Card Applications SMPTE RDD 18:2012, Acquisition Metadata Sets for Video Camer
22、a Parameters Recommendation ITU-R BT.709-5 (04/02), Parameter Values for the HDTV Standards for Production and International Programme Exchange 3 Introduction The MXF Generic Container is a streamable Essence Container that can be placed on any suitable transport and stored. SMPTE ST 379-1 defines t
23、he MXF Generic Container as the native Essence Container in MXF files. Also, SMPTE ST 379-2 defines the MXF Constrained Generic Container. SMPTE ST 381-3 defines how AVC streams, as defined in ISO/IEC 14496-10 | Rec. ITU-T H.264, can be mapped in the MXF Generic Container and MXF Constrained Generic
24、 Container. SMPTE ST 382 defines how AES3 Audio can be mapped in the MXF Generic Container. SMPTE ST 385 defines the System Item that is compatible with SMPTE ST 326 (SDTI-CP) and also defines how SDTI-CP essence and metadata can be used in the MXF Generic Container. This document specifies the MXF
25、mapping of XAVC, i.e. MPEG-4 AVC picture, AES3 audio and ANC packets into the MXF Generic Container or MXF Constrained Generic Container. This document also specifies the MXF file format which includes unique identifiers, Operation Pattern, Partitions, Index Table Segments and RIP. The common basic
26、structure is described in this document. 4 Outline of MXF File Structure for this Mapping 4.1 General XAVC MXF files specified by this document shall have one of the two structures illustrated in Figure 1 and Figure 2 respectively. Figure 1 Single Essence Location Style Figure 2 Multiple Essence Loc
27、ation Style HPP: Header Partition Pack, BPP: Body Partition Pack, FPP: Footer Partition Pack RIP: Random Index Pack Fil e He a d e r Fil e Bod y Fil e F o o terHeaderMetadataHPPIndexT ableEdi tUnitEdi tUnitEdi tUnitEdi tUnitEdi tUnitEdi tUnitEdi tUnit Edi tUnitEdi tUnitEdi tUnitEdi tUnitEdi tUnitFPP
28、RIPHead er Partit io n Fo ot er Partit io nFile Hea de r File Bod y File F oo terHeaderMetadataHPPEdi tUnit Edi tUnitFPPRIPHead er Partit io n Fo ot er Par tit ionBPPBPPIndexT ableEdi tUnitEdi tUnitBPPIndexT ableEdi tUnitEdi tUnitIndexT ableBod y Par tit ionBPPIndexT ableSMPTE RDD 32:2014 Page 6 of
29、33 pages A list of major constraints common to these file structures is given in Table 1. Table 1 Constraints for SMPTE RDD 32 Stream Products Item Constraints Operational Pattern 1a - Origin and Duration1 are used to express GOP Pre-Charge and Roll-Out in the case of Long GOP. Wrapping (Interleavin
30、g) Frame by Frame (coded order) KAG size 512 System Item Compliant to SMPTE ST 326 and SMPTE ST 385, includes the Frame by Frame Timecode and UMID Video mapping Compliant to SMPTE ST 381-3, AVC byte stream GOP structure (in the case of Long GOP) 0.5 second (e.g. 24 frames for 50p), M=3 (display orde
31、r: BBIBBPBBPBBP) Audio sampling 48 kHz locked to Video Audio mapping Compliant to SMPTE ST 382, AES3, 1ch/Element (min 2 to max 16 channels2) Data Item Compliant to SMPTE ST 436-1, used for Ancillary packet Timecode System Item and Header Metadata Detailed constraints are listed in Annex B. 4.2 Sing
32、le Essence Location Style As shown in Figure 1, this style consists of a Header Partition, a Footer Partition, and a Random Index Pack. The Index Table is placed prior to the Essence Container. Some of the aspects of this style are shown below. It is easy to handle because of a simple structure. It
33、is easy to edit while file transferring. It is easy to pick extract a “Partial file”. It is recommended to have the following Index Layout Properties defined in Amendment 2 to SMPTE ST 377-1. Index Table Segment:Single Index Location TRUE (Single Location) Index Table Segment:Single Location TRUE (S
34、ingle Location) Index Table Segment:Forward Index Direction TRUE (Forward) Preface: is RIP present TRUE 4.3 Multiple Essence Location Style As shown in Figure 2, this style consists of a Header Partition, segmented Body Partition(s), a Footer Partition, and a Random Index Pack. Every Partition excep
35、t Header and the first Body Partitions has one Index Table Segment which carries the Index Entries indexing the Edit Units. 1 The duration of the top level file package contains the Pre-Charge but does not contain Roll-Out as defined in SMPTE ST 377-1. 2 Even number only SMPTE RDD 32:2014 Page 7 of
36、33 pages The purpose of this essence location style is to place the Index Table Segment just after the corresponding essence data. All Index Table Segments follow Essence Container Segments that they index. Thus, when receiving a streamed file, decoders can use Index Table Segments for indexing with
37、out a long delay. Some of the aspects of this style are shown below. It is only necessary to include one Index Table Segment for each Body Partition period on the sender side. It is easy to perform the function “Play while receiving file” on the receiver side. It is easy to pick extract a “Partial f
38、ile”. It is recommended to have the following Index Layout Properties. Index Table Segment:Single Index Location FALSE (Distributed Location) Index Table Segment:Single Essence Location FALSE (Distributed Location) Index Table Segment:Forward Index Direction FALSE (Backward) Preface: is RIP present
39、TRUE Essence Container Data: Following Index Table TRUE (A Complete Index Table follows all Essence) 5 AVC Picture Data and AES3 Data Mapping 5.1 General The mapping of XAVC, i.e. MPEG-4 AVC Picture data, is as defined in SMPTE ST 381-3. The mapping of AES3 digital audio data is defined by SMPTE ST
40、382. This specification uses Frame Wrapping as defined by SMPTE ST 379-2. The System Item is defined by SMPTE ST 326, and mapped into the MXF by SMPTE ST 385. The order of Items in each Edit Unit is System, Picture, Sound and Data. 5.2 Edit Unit Structure The XAVC MXF Mapping shall make use of Frame
41、 Wrapping as defined by SMPTE ST 379-2 Section 8.4.1. An arrangement of System, Picture, Sound, and Data Items in a Frame Wrapping, i.e. the structure of Edit Unit is shown in Figure 3. Figure 3 Structure of Generic Edit Unit 5.3 System Item Mapping 5.3.1 General The System Item in each Edit Unit co
42、nsists of System Metadata Pack, a Package Metadata set and Picture Metadata Set. 5.3.2 Overview of System Item The System Item is placed at the beginning of every Edit Unit and contains information on the essence item and the metadata attached to the frames, and it shall comply with SMPTE ST 385. S
43、o u n d(A E S )c h . 1G C P i c t u re I t e m(E l e m e n t a ry S t re a m )CPS y s t e mI t e m D a t aI t e m F i l lK LK LK L F i l lK L K L F i l lK L K L F i l lK LS o u n d(A E S )c h . 2K L F i l lK LS o u n d(A E S )c h . nK L F i l lK L. . . . . . .SMPTE RDD 32:2014 Page 8 of 33 pages Typ
44、ical System Item consists of the following two KLV packets and a fill item, and its size is the same as one KAG size (200h). System Metadata Pack contains Package Rate, Multiple EC UL, LTC Package Metadata Set contains Body UMID Fill Item Figure 4 shows the outline of System Item. Figure 4 Typical S
45、ystem Item structure 5.3.3 System Metadata Pack The Pack Key is 06.0E.2B.34.02.05.01.01.0D.01.03.01.04.01.01.00, in accordance with SMPTE ST 385. The Length of this pack shall be fixed, i.e. 57-byte payload. Also, each property shall be described in the provided field without tag and length. The seq
46、uence and values shall comply with SMPTE ST 326. System Metadata Bitmap (“SMB“ in the figure) indicates the presence of metadata in the Pack, and of essence data within the Edit Unit, should be set to 0101_1100b, when Data Item is not recorded or 0101_1110b when Data Item is recorded. The value of C
47、ontinuity Count (“CC“ in the figure) shall be monotonically increasing within a file. It does not have to start from 0, and reverts to 0000h following full count FFFFh. SMPTE Universal Label (“GC EC label“ in the figure) shall be set to the same label as the Essence Container Property of Multiple De
48、scriptor Set. Package Creation Date should be blank. Tag (“T“ in the figure) and the remains are filled with 00h. LTC shall be described in the User Date column. Since it complies with SMPTE ST 331, it starts with CP-Tag 81h and digits of Frame, Second, Minute, and Hour are placed with flags such as
49、 DF, and then Binary Group data (4 bytes) is placed, and remaining 8 bytes are filled with 0. In the 50p/59.94p system, the LTC is handled in half the rate of the Main-Stream video, and the field mark flag in the Time Code is used to identify the first or second frame of a frame pair. 5.3.4 Package Metadata Set The Set Key is 06.0E.2B.34.02.43.01.01.0D.01.03.01.04
