1、 Table of contents 1 Scope 2 Normative references 3 Glossary of acronyms, terms and data types 4 Introduction 5 Type D-11 data structure and mapping to the generic container 6 Application issues Annex A Descriptor set values for the essence elements defined in this standard Annex B Bibliography 1 Sc
2、ope This standard defines the mapping of compressed picture data according to the type D-11 data stream and up to 8 channels of AES3 data into the material exchange format generic container (MXF-GC). This mapping is given the acronym: MXF-GC(D-11). The MXF specification is written in several parts.
3、This is one of a set of documents that define the contents of the MXF file body. The MXF file format specification includes operation pattern specifications that may define restrictions to be placed on the way in which this essence container type can be implemented. The reader is advised to carefull
4、y study the appropriate operational pattern document for compliance to the defined implementation. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this standard. At the time of publication, the editions indicated were
5、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 editions of the standards indicated below. SMPTE 331M-2004, Television Element and Metadata Definitions for SDTI-CP SMPTE 367M-2002,
6、 Television Type D-11 Picture Compression and Data Stream Format SMPTE 369M-2002, Television Type D-11 Data Stream and AES3 Data Mapping over SDTI SMPTE 377M-2004, Television Material Exchange Format (MXF) File Format Specification SMPTE 379M-2004, Television Material Exchange Format (MXF) MXF Gener
7、ic Container. Page 1 of 19 pages SMPTE 387M-2004 Copyright 2004 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 595 W. Hartsdale Ave., White Plains, NY 10607 (914) 761-1100 ApprovedSeptember 22, 2004SMPTE STANDARD for Television Material Exchange Format (MXF) Mapping Type D-11 Essence Data
8、 to the MXF Generic Container SMPTE 387M-2004 Page 2 of 19 pages SMPTE 385M-2004, Television Material Exchange Format (MXF) Mapping SDTI-CP Essence and Metadata into the MXF Generic Container 3 Glossary of acronyms, terms and data types The general glossary of acronyms, terms and data types used in
9、the MXF specification is given in SMPTE 377M. Supplementary glossaries of acronyms and terms are defined in SMPTE 379M and SMPTE 385M. They are not repeated here to avoid any divergence of meaning. 3.1 Acronyms and terms used in this standard ECC: Error Correction Code H-ANC: Horizontal ANCillary da
10、ta (per SMPTE 291M) VITC: Vertical Interval Time Code PsF: Progressive segmented Frame 4 Introduction (informative) This standard specifies the mapping of type D-11 data from an SDTI data port specified by SMPTE 369M to the MXF generic container (SMPTE 379M). The type D-11 data comprises packets of
11、type D-11 basic blocks containing compressed picture data and auxiliary picture data as specified in SMPTE 367M (type D-11 picture compression and data stream format). Four channels of 24-bit AES3 data are optionally mapped into the H-ANC space of the SDTI according to SMPTE 272M. In addition, VITC
12、may also be mapped into the H-ANC space according to SMPTE 369M. This specification also covers the mapping of the audio and VITC data from the SDTI into the MXF generic container. Figure 1 also includes the optional four channels of 24-bit AES3 data mapped into the H-ANC space. VITC data (shown as
13、auxiliary data in figure 1) may also be mapped into the H-ANC space. SMPTE 387M-2004 Page 3 of 19 pages AuxiliaryDataSAVEAVVideo Data,Segments 02SwitchingLinesPayloadstart:0Payloadend:1439EAV:14401443HeaderData:14441496End of HBlanking:1712 (525)1724 (625)Audio data:14971553(525)14971567(625)First f
14、ieldAuxiliaryDataSAVEAVVideo Data,Segments 35SwitchingLinesSecond fieldCompressed picture dataCompressed picture dataFigure 1 SDTI mapping The type D-11 data stream packets are grouped into six equal data segments of which the first three data segments are mapped onto the first field of the SDTI and
15、 the last three data segments are mapped onto the second field of the SDTI, as shown in figure 1. Note that because the type D-11 format operates at 24-Hz and 241.001-Hz frame rates as well as the conventional television rates of 25-Hz and 301.001-Hz, the SDTI must operate at all frame rates to supp
16、ort synchronous stream transfers based on one frame of compressed HD picture data together with the associated audio data and VITC data packed into one frame of the SDTI. Table 1 shows the core parameters of the SDTI at all the frame rates used by SMPTE 367M. SMPTE 387M-2004 Page 4 of 19 pages Table
17、 1 Total number of lines and samples per line for each frame rate of the interface Frame rate of the Interface 241.001Hz 24Hz 25Hz 301.001Hz Total number of Lines 525 625 625 525 Total number of samples per Line 2145 1800 1728 1716 This standard defines the mapping of type D-11 data into the generic
18、 container as an MXF-compliant body. In effect, this standard defines the generic container with a system item, a type D-11 compressed picture data element, a 4-channel AES3 data element and optional auxiliary data elements in the auxiliary item. The MXF-GC (D-11) mapping conforming to this standard
19、 complies with the requirements for MXF body files defined in the MXF format document. 5 Type D-11 data structure and mapping to the generic container For each frame of the type D-11 SDTI payload, the data shall be divided into four components as follows: 1. A metadata pack element followed by optio
20、nal metadata elements whose values are extracted from ancillary data packets. These ancillary data packets are extracted from the H-ANC space as specified in SMPTE 369M. 2. A mandatory picture element whose value comprises all six concatenated segments of the type D-11 compressed picture information
21、 (see SMPTE 367M). This component is mapped into a type D-11 element in the generic container picture item. 3. An optional AES3 sound element whose value comprises all the AES3 data packets extracted from the H-ANC space of the SDTI as defined in SMPTE 369M. This AES3 data is mapped into an 8-channe
22、l AES3 Element as defined in SMPTE 331M. Only 4 channels of the 8-channel element are used. 4. Optional H-ANC data packet elements for the carriage of ANC data packets not carried by the system item. This specification shall use frame-based mapping as defined by SMPTE 379M. The order of items in thi
23、s mapping shall be system, picture, sound and data (if present). 5.1 KLV coding The resulting KLV coded packets for each frame are represented in sequence as shown in figure 2. SMPTE 387M-2004 Page 5 of 19 pages 4-byte Length System Item Pack Value System Item Data Pack (see SMPTE 385M) 16-byte Key
24、4-byte Length Value = Ancillary Data as Metadata Blocks System Item of 0 or 1 Package Metadata Element 16-byte Key 4-byte Length Value = 8-channel AES3 data Sound Item of 0 or 1 Element Note: Element sizes are not to scale Data Item of 0 or more Elements 16-byte Key 16-byte Key 4-byte Length Value =
25、 Ancillary Data 16-byte Key 4-byte Length Value = Ancillary Data 16-byte Key 4-byte Length Value = Type D-11 data Picture Item of 1 Element Figure 2 Sequence of KLV coded GC elements in the type D-11 mapping 5.1.1 Ancillary data packet mapping The SDTI payload as defined by SMPTE 369M may include “a
26、uxiliary data” coded as H-ANC packets according to SMPTE 291M. These H-ANC packets contain data that can be mapped into either the GC system item or the GC data item depending on the value of the H-ANC data ID word and the secondary data ID word (where applicable). Only those auxiliary data H-ANC pa
27、ckets carrying 8-bit data are supported in this mapping. Any auxiliary data H-ANC packets which contain data ID and secondary data ID values identifying user data words of 9-bits per word are not supported. Figure 3 illustrates the “auxiliary data” H-ANC packet structure. SMPTE 387M-2004 Page 6 of 1
28、9 pages 3-word ADF Data ID Active 8 bits, b0b7 CRC User Data Secondary Data ID or Data Block No. Data Count b9 b0 b9 = odd parity b8 = even parity Packet Payload Figure 3 Ancillary data packet structure If the H-ANC packet data ID word identifies a user data type which is metadata, then the packet p
29、ayload shall be mapped into the system item as one or more package metadata sets. Package metadata sets contain metadata items which describe the whole content package of which they are a part. The H-ANC packet mapped to any GC (D-11) element shall remove the 3-word ancillary data flag (ADF) as this
30、 is specifically related to synchronization of the H-ANC packet in the SDTI. The GC (D-11) element mapping shall include the CRC word to provide some level of error protection. Each element value shall be defined as the least significant 8 bits of each word from the following parts of an H-ANC data
31、packet: the data ID word; the secondary data ID (or data block number) word; the data count word; the user data words; and the CRC word. On reconstruction of an H-ANC packet from the GC (D-11) element value, the 3-word ADF shall be added. Since bits b8 and b9 of all 10-bit input words are discarded
32、at the point of mapping the SDTI input into the file, these bit values shall be re-calculated to reconstruct the complete H-ANC packet. NOTES 1 The mapping of an ANC data packet payload into the value field of a system or essence element is identical to the mapping into a CP auxiliary element (defin
33、ed in SMPTE 331M). The data type value for the metadata block is 21h as per SMPTE 331M. 2 Users are cautioned that any change to the user data words will require a re-calculation of the CRC check word according to SMPTE 291M. 5.2 System item mapping The contents of the system item shall comply with
34、that defined in SMPTE 385M. The system metadata pack and the package metadata set are required. The presence of the picture item, sound item, data item and control element depends on the setting of the system metadata bitmap as defined in SMPTE 385M. 5.2.1 SMPTE universal label The universal label u
35、sed in the MXF GC(D-11) system item and in the MXF header metadata shall have the following value: SMPTE 387M-2004 Page 7 of 19 pages Table 2 Specification of the MXF-GC(D-11) essence container UL Byte No. Description Value (hex) Meaning 113 See SMPTE 379M Defined in Table 3 of the MXF generic conta
36、iner specification 14 Mapping Kind 03h Type D-11: SMPTE 367M compression and SMPTE 369M SDTI transport 15 Type D-11 Source Coding (1920*1080 picture size) 01h 06h 01h = 23.98 PsF 02h = 24 PsF 03h = 25 PsF 04h = 29.97 PsF 05h = 50 I 06h = 59.94 I 16 Type: Template Extension 01h or 02h01h = template d
37、efined in this document 02h = extended template The label value as described above shall be used as the essence container label in the preface set and the appropriate file descriptor set of the header metadata and in the partition pack. 5.2.2 Package metadata set 5.2.2.1 Metadata element key The pac
38、kage metadata element key value shall be as follows: Table 3 Key value for the type D-11 package metadata element Byte No. Description Value (hex) Meaning 112 See SMPTE 385M Defined in Table 2 of SMPTE 385M 13 Item Type Identifier 04h CP-compatible system item 14 System Scheme Identifier 01h SDTI-CP
39、, version 1 15 Metadata Element Identifier 02h Package metadata set 16 Metadata Block Count xxh Number of H-ANC packets 5.2.2.2 Metadata element length The length field of the KLV coded element shall be 4 bytes BER long-form encoded (i.e., 83h.xx.yy.zz). The value of the length field shall correctly
40、 define the length of the element value. 5.2.2.3 Metadata element value Where present this shall contain the 8-bit payloads of all auxiliary data H-ANC packets present on the SDTI that are identified as carrying metadata. The 8-bit payload of each auxiliary data H-ANC packet shall be mapped into a s
41、equence of metadata items as defined in figure 4 of SMPTE 385M. Each metadata item shall comprise a local tag with a value of 21h as SMPTE 387M-2004 Page 8 of 19 pages defined in SMPTE 331M, a 2-byte length as defined in SMPTE 385M, followed by the 8-bit payload of the H-ANC data packet (as defined
42、by 5.1.1) mapped into the value field. Where more than one auxiliary data H-ANC packet is present in the frame period, they shall be mapped to the metadata items in the sequence as they appear in the frame. Metadata items mapped from field 1 of the SDTI shall be followed immediately by metadata item
43、s mapped from field 2 of the SDTI. Because the package metadata set applies to the whole content package, there is no requirement for the metadata link item described in SMPTE 385M. NOTE The package metadata set will typically comprise two metadata items mapped from the payloads of two auxiliary dat
44、a H-ANC packets, one in the first field of the SDTI and one in the second field. These typically contain only VITC data. 5.3 Picture item mapping The picture item value shall comprise a single element which contains the compressed picture and embedded auxiliary data as defined by SMPTE 367M. The map
45、ping of the compressed picture and embedded auxiliary data onto the SDTI is defined by SMPTE 369M. 5.3.1 Essence element key The essence element key value shall be as follows: Table 4 Key value for the type D-11 picture element Byte No. Description Value (hex) Meaning 112 See SMPTE 379M Defined in T
46、able 2 of SMPTE 379M 13 Item Type Identifier 15h GC picture item 14 Essence Element Count 01h One essence element present 15 Essence Element Type 01h Type D-11 video as defined by SMPTE 367M 16 Essence Element Number 01h Normative value 5.3.2 Essence element length The length field of the KLV coded
47、element shall be 4 bytes BER long-form encoded (i.e., 83h.xx.yy.zz). The value of the length field shall correctly define the length of the element value. 5.3.3 Essence element value 5.3.3.1 Segment mapping Each compressed picture data stream is divided into six equal segments, numbered 0 to 5, as d
48、efined in SMPTE 367M. Each segment has an even channel and an odd channel as defined in SMPTE 367M. All the packets from both channels of segments 0 to 2 are mapped into 212 lines of the first field of the SDTI and all the packets from both channels of segments 3 to 5 are mapped into 212 lines of th
49、e second field of the SDTI, as defined in SMPTE 369M and illustrated in figure 1. NOTE The last of the 212 lines in each field is not fully occupied. SMPTE 387M-2004 Page 9 of 19 pages 5.3.3.2 SDTI payload line mapping The transfer of the data from SDTI to the type D-11 element value in the picture item shall include all the basic block data (see details below), but shall specifically exclude the first two words and the last two words of each SDTI payload line. The first two words of each SDTI payload line cont
