SMPTE ST 375M-2003 SMPTE STANDARD for Television - Mapping of Vertical Ancillary Data Packets (VANC) into VAUX DIF Blocks of DV-Based 100 Mb s DIF Stream Format.pdf

《SMPTE ST 375M-2003 SMPTE STANDARD for Television - Mapping of Vertical Ancillary Data Packets (VANC) into VAUX DIF Blocks of DV-Based 100 Mb s DIF Stream Format.pdf》由会员分享，可在线阅读，更多相关《SMPTE ST 375M-2003 SMPTE STANDARD for Television - Mapping of Vertical Ancillary Data Packets (VANC) into VAUX DIF Blocks of DV-Based 100 Mb s DIF Stream Format.pdf（14页珍藏版）》请在麦多课文档分享上搜索。

1、 Table of contents 1 Scope 2 Normative references 3 General description and payload capacity of the VAUX DIF space 4 VAUX DIF block space organization and payload format 5 VANC conversion/transform process into DANC and formatting 6 Mapping DANC (VANC) into VAUX DIF block space 7 Mapping in a DIF fr

2、ame Annex A Abbreviations Annex B Bits from SDI VANC Annex C Structure of the mapping process 1 Scope This standard specifies the mapping of vertical ancillary data packets (VANC) into the payload area of the DV-based 100 Mb/s digital interface format (DIF) structure VAUX DIF blocks as defined in SM

3、PTE 370M. Metadata and data essence may be contained in VANC packets present in vertical blanking interval (VBI) of the uncompressed high-definition serial digital interface (HD-SDI). The purpose of this standard is to define how such data is mapped into the video auxiliary (VAUX) DIF blocks of the

4、100 Mb/s DV-based compressed signal stream format. This mapping is applicable to the 1080/60i, 1080/50i, and 720/60p signal formats present on the HD-SDI. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this standard.

5、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 editions of the standards indicated below. SMPTE 291M-1997, Television Anci

6、llary Data Packet and Space Formatting SMPTE 292M-1998, Television Bit-Serial Digital Interface for High-Definition Television Systems SMPTE 370M-2002, Television Data Structure for DV Based Audio, Data and Compressed Video at 100 Mb/s 1080/60i, 1080/50i, 720/60p SMPTE RP 168-2002, Definition of Ver

7、tical Switching Point for Synchronous Video Switching Page 1 of 14 pages SMPTE 375M-2003 Copyright 2002 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 595 W. Hartsdale Ave., White Plains, NY 10607 (914) 761-1100 Approved March 17, 2003 SMPTE STANDARD for Television Mapping of Vertical Anc

8、illary Data Packets (VANC) into VAUX DIF Blocks of DV-Based 100 Mb/s DIF Stream Format SMPTE 375M-2003 Page 2 of 14 pages 3 General description Metadata and Data Essence can be carried in the Ancillary space of the HD-SDI stream structure. These data that are formatted according SMPTE 291M as VANC p

9、ackets are located in a VBI space. The VANC packets can be converted/transformed and subsequently mapped into an available data space of the 100 Mb/s DV-based DIF stream. The space that is used for the mapping of these VANC packets is located in multiple VAUX DIF blocks of a DIF frame. Multiple DIF

10、blocks (each 80 bytes long) form a DIF Sequence. Several DIF Sequences form a DIF frame, all defined in the SMPTE 370M (see figure 1). The conversion process converts VANC packets into DIF ancillary data packet (DANC). Every VANC packet is converted into a DANC packet of an identical length, as is t

11、he originating VANC packet. The resulting DANC packets are then assembled into a string of DANC packets and this string is then mapped into the available space of the VAUX DIF blocks. Due to the limited total VAUX DIF block space, and to achieve maximum benefit of the available space for the user, m

12、anagement of the data space by the user should be established (see note 1). A specific data management method is beyond the scope of this standard. NOTE 1: Designers should be aware that the size of VANC data can exceed the capacity of the VAUX packs. It is the responsibility of the application to m

13、anage the mapping of VANC data into VAUX packs such that only complete VANC packets are mapped into VAUX DIF blocks. Where the VAUX capacity is exceeded, it is the responsibility of the application to manage this mapping in such a way as to minimize the effect on system performance, of not mapping a

14、ll of the VANC data The ancillary packet conversion to DANC packet is a direct conversion technique, fully transparent for the data content, and is defined in this standard. 3.1 Data capacity of the mapped space (VAUX DIF block space) and its structure Figure 1 shows the typical organization of a DI

15、F frame and DIF Sequence for a DV-based 100 Mb/s stream structure as described in SMPTE 370M. The basic VAUX DIF block space that is used for mapped VANC packets consists of three VAUX DIF blocks VA 0,i; VA 1,i; and VA 2,i located in multiple DIF sequences. These DIF sequences form a DIF frame. The

16、payload space of these three VAUX DIF blocks is subdivided into smaller entities called VAUX packs. These VAUX packs exist in 5-byte, 45-byte, and 75-byte long form (see figure 3a, 3b, and 3c). i) 5-byte long VAUX pack The 5-byte long VAUX pack is defined in the SMPTE 370M. These 5-byte long VAUX pa

17、cks (see figure 3a) may be used in any of the VAUX DIF blocks, regardless of odd or even DIF sequence. ii) 45-byte or 75-byte long VAUX pack Additionally, this standard defines a different payload structure of the VAUX DIF block that is not defined in SMPTE 370M (see figures 3b and 3c). These new st

18、ructures are based on a 45-byte or 75-byte long VAUX pack. The reason for these additional structures is to increase payload efficiency. However, the structure of a used VAUX pack is determined by the actual structure of a VAUX DIF block and if this block is located in an odd or even DIF sequence (s

19、ee figure 2). The user available payload capacity of all VAUX DIF blocks in a single DIF frame using different VAUX pack structures is shown below: In the case of a VAUX DIF block that uses the 5-byte VAUX pack structure: 1080/60i system: 4 bytes x (15 + 15 + 9) packs x 40 DIF sequences = 6240 bytes

20、/frame 1080/50i system: 4 bytes x (15 + 15 + 9) packs x 48 DIF sequences = 7488 bytes/frame 720/60p system: 4 bytes x (15 + 15 + 9) packs x 40 DIF sequences = 6240 bytes/2frames SMPTE 375M-2003 Page 3 of 14 pages In the case of a VAUX DIF block that uses the 45-byte or 75-byte VAUX pack structure: 1

21、080/60i system: (72 x 2+ 42) bytes x 40 DIF sequences = 7440 bytes/frame 1080/50i system: (72 x 2 + 42) bytes x 48 DIF sequences = 8928 bytes/frame 720/60p system: (72 x 2+ 42) bytes x 40 DIF sequences = 7440 bytes/2frames 4 VAUX DIF block space structure and payload format (VAUX packs) The format o

22、f the VAUX DIF block space available for data mapping is shown in figure 2. Each DIF sequence of a DIF frame contains 3 VAUX DIF blocks, but depending on if the VAUX DIF block is located in the odd or even DIF sequence, the formatting of the data payload is slightly different for one of the three VA

23、UX DIF blocks (see figure 2). The differently formatted VAUX DIF block in a DIF sequence contains control information called VS (VAUX source pack) and VSC (VAUX source control pack) which contains essential information for identification of the DIF frame signal parameters. The control information is

24、 carried in the 5-byte long VAUX packs form and is defined SMPTE 370M. The size of the available mapping space in 3 VAUX DIF blocks is identical for both DIF sequences, odd or even. Figure 1 Structure of a DIF frame for DV-based 100 Mb/s stream Structure of a DIF Sequence DIF blocks DIF Sequences DI

25、F sequence number DIF channel number Data in one frame of 1080i system or two frames of 720p system First channel Second channel Third channel Fourth channel DIF Sequence 0,0 DIF Sequence 1,0 DIF Sequence n-1,0 DIF Sequence 0,1 DIF Sequence n-1,3 Header section Subcode section VAUX section Audio B1;

26、 B2. Table 1 VAUX pack type 1 MSB LSB PC0 1 1 1 0 0 0 0 1 PC1 Res Res Res Res Res Res Res Res PC2 B0 PC3 B1 PC4 B2 Pack Header PC0 PC1 PC2 PC3 PC4 5 bytes Pack Header PC0 PC1 PC2 PC3 PC42 PC43 PC 44 45 bytes Pack Header PC0 PC1 PC2 PC3 PC72 PC73 PC74 75 bytes SMPTE 375M-2003 Page 6 of 14 pages 4.1.1

27、.2 Type 2 VAUX pack definitions (see table 2) The VAUX pack header (PC0) for type 2 is set to E2h. The subsequent bytes of the VAUX pack type 2 are used for mapping of the DANC string data B j, B j+1; B j+2; B j+3 and are in a same order as bytes of the DANC packet. The unused bytes of the last VAUX

28、 pack type 2 containing mapped data of a DANC packet, shall be filed with FFh (see figure 4). Table 2 VAUX pack type 2 MSB LSB PC0 1 1 1 0 0 0 1 0 PC1 B jPC2 B j+1 PC3 B j+2 PC4 B j+3 Figure 4 Mapping a DANC packet into type 1 and type 2 VAUX packs 4.1.2 45-byte and 75-byte long VAUX packs type 3a a

29、nd 3b These VAUX packs are used for greater payload efficiency. Both packs use the same pack header, which is set to E3h. During the mapping process these packs are selected such that a chosen specific pack length depends on the payload size of the VAUX DIF block from either the odd or even DIF sequ

30、ence. 4.1.2.1 Type 3a VAUX pack definition This type of a VAUX pack is 45 bytes long. The type 3a VAUX pack is used with VAUX DIF block VA 2,i from the even DIF sequence and VAUX DIF block VA 0,i from the odd DIF sequence (see figure 2). The VAUX pack header (PC0) for type 3a is set to E3h. The seco

31、nd byte (PC1) contains “Reserved” bits with the exception of the LSB bit. The LSB bit is called the END bit, and if this bit is set to 0, it indicates that the particular VAUX pack contains the last byte of the mapped DANC string (see figure 5). The third byte (PC2) of the VAUX pack type 3a contains

32、 only “Reserved” bits for future applications. The “Reserved” bits default value is set to 1. The remaining bytes PC3 thru PC44 shall contain the mapped data of a DANC string (see table 3a). DANC packet B0, B1, B2, B3, B4, B5, B6, B7, B8, B9, B10, unused space Bm type 1 type 2 type 2 type 2 type 2 V

33、AUX packs (FFh) 3 bytes 4 bytes 4 bytes 4 bytes B0,B1,B2 B3,B4,B5,B6 B7,B8,B9,B10 E1h E2h E2h Bm E2h E2h FFh SMPTE 375M-2003 Page 7 of 14 pages Table 3a VAUX pack type 3a MSB LSB PC0 1 1 1 0 0 0 1 1 PC1 Res Res Res Res Res Res Res END PC2 Res Res Res Res Res Res Res Res PC3 B k PC4 B k+1 PC5 B k+2 :

34、 : PC44 B k+41 4.1.2.2 Type 3b VAUX pack definition This type of a VAUX pack is 75 bytes long. The type 3b VAUX pack is used with VAUX DIF blocks VA 0,i; VA 1,i from the even DIF sequence and VAUX DIF blocks VA 1,i; VA 2,i from the odd DIF sequence (see figure 2). The definition of the VAUX pack typ

35、e 3b is the same as the definition of a VAUX pack type 3a (section 4.1.2.1) with the exception that the mapped data of the DANC string is loaded into bytes PC3 through PC74 due to its longer length (see table 3b). The unused space of the last VAUX pack type 3a or 3b shall be filled with FFh (see fig

36、ure 5). Table 3b VAUX pack type 3b MSB LSB PC0 1 1 1 0 0 0 1 1 PC1 Res Res Res Res Res Res Res END PC2 Res Res Res Res Res Res Res Res PC3 B kPC4 B k+1 PC5 B k+2 : : PC74 B k+71 If END = 0 then the VAUX pack and the used VAUX DIF block contains the last byte of the DANC string If END = 1 then the VA

37、UX pack and the used VAUX DIF block does not contain the last byte of the DANC string Figure 5 Mapping of a DANC string into VAUX packs type 3a or 3b B0, B1, B2, ,Bs-1 1st DANC packet DANC (VAUX) packs FFh 42 or 72 bytes 2nd DANC packet “n” DANC packet END =1 END =1 END =1 END =1 END =0 42 or 72 byt

38、es 42 or 72 bytes 42 or 72 bytes E3h E3h E3h E3h E3h DANC string unused area type 3a or 3b type 3a or 3b type 3a or 3b type 3a or 3b type 3a or 3b SMPTE 375M-2003 Page 8 of 14 pages 5 Conversion and mapping process of VANC data packets SMPTE 291M VANC data packets present on the 10-bit HD-SDI interf

39、ace (SMPTE 292M) are converted into DIF ancillary data packets, DANC packets. Figure 6 shows the relationship between a VANC and a DANC packet. A converted DANC packet is of identical length as the originating VANC packet (figure 6.) Of the DID, SDID/(DBN), DC, UDW, and CS, only the lower 8 bits of

40、the 10-bit SMPTE 291M ancillary data packet words are processed. For definitions of ADF, DID, SDID, DBN, UDW, and CS of an ancillary packet see SMPTE 291M. During the conversion process, the three ADF data bytes are replaced by new information consisting of one LE bit (line enable flag), 11 LN bits

41、(line number), FI bit (frame indication flag), YCF bit (YC flag) and “Res” bits. “Res” bits are reserved for future use and default value is set to 1. The LE bit defines validity of the present LN bits, and these LN bits indicate the HD-SDI line number on which the originating VANC packet resides at

42、 the start of the conversion process. The FI flag is used to identify either one of the two frames in the 720/60p system. The YCF flag is used to identify where the originating VANC ancillary packet was located on the Y signal or C signal in the VBI. The ADF bytes are discarded during this process.

43、All of the VANC packets present in the VBI of the HD-SDI interface are converted into the DANC packets and these are assembled to form a string of DANC packets of total length S bytes. This string of DANC packets is then mapped into multiple VAUX DIF blocks shown in figure 2. The LN bits, the FI bit

44、 and the YCF bit are used to identify the location of the originating VANC packet on the HD-SDI interface and are used during a reverse mapping process. During that process, the DANC packets are converted back into VANC packets and relocated back into the VBI space of the HD-SDI interface. Use of th

45、e LN bits and FI flag bit assures that a temporal skew of the VANC packets (based on field/frame location) is not possible. When the data from a DANC packet are converted back to a VANC packet, the upper 2 bits are generated from the lower 8 bits. This conversion process is applied only to VANC data

46、 located in a single frame of the relevant high-definition television signal and the available space for the VANC packets is indicated in 3.1. SMPTE 375M-2003 Page 9 of 14 pages SMPTE 291M ancillary data packet (VANC packet) Conversion process VANC to DANC and reverse DIF ancillary data packet (DANC

47、 packet) Figure 6 - SMPTE 291M ancillary data packet (VANC) & DIF ancillary data packet (DANC) LE: Line number enable flag (see note 2) LE = 0 then LN bits are invalid LE = 1 then LN bits are valid NOTE 2 In the case of originally generated information to be placed in a DANC packet (e.g., ancillary

48、time code or UMID), LE may be set to 0 or 1, depending if any specific line is preferred for the mapped data location on the interface LN: Line number a line number identifying where the originating VANC ancillary packet was located in the VBI. This number is equal to the binary code of the line num

49、ber provided by the HD-SDI interface defined in SMPTE 292M 1080/60i and 1080/50i system LN0 - LN10 = 1, , 1125 720/60p system LN0 - LN10 = 1, , 750 FI: Frame indication flag identification of the two frames present in the 720/60p system 1080/60i and 1080/50i system FI = 1 720/60p system FI = 1: video frame 1 (refer to SMPTE 370M) FI = 0: video frame 2 YCF: YC flag identifies where the originating VANC ancillary packet was located on the HD-SDI interface in the