![](http://datasheet.mmic.net.cn/Analog-Devices-Inc/ADV611JSTZ_datasheet_96339/ADV611JSTZ_28.png)
ADV611/ADV612
–28–
REV. 0
Table XV. ADV611/ADV612 Field and Block Delimiters (Codes)
Code Name
Code
Description (Align all #Delimiter Codes to 32-Bit Boundaries)
#SOF1
0xffffffff40000000
Start of Field delimiter identifies Field1 data. #SOF1 resets the Huffman decoder and is
sufficient on its own to reset the processing of the chip during decode. Please note that this
code or #SOF2 are the only delimiters necessary between adjacent fields. #SOF1 operates
identically to #SOF2 except that during decode it can be used to differentiate between
Field1 and Field2 in the generation of the Field signal (master mode) and/or SAV/EAV
codes for CCIR-656 modes.
#SOF2
0xffffffff41000000
Start of Field delimiter identifies Field2 data. #SOF resets the Huffman decoder and is
sufficient on its own to reset the processing of the chip during decode. Please note that this
code or #SOF1 are the only delimiters necessary between adjacent fields. #SOF2 operates
identically to #SOF1 except that during decode it can be used to differentiate between
Field2 and Field1 in the generation of the Field signal (master mode) and/or SAV/EAV
codes for CCIR-656 modes.
<VITC>
(96 bits)
This is a 12-byte string of data extracted by the video interface during encode operations
and inserted by the video interface into the video data during decode operations. The data
content is 90 bits in length. For a complete description of VITC format, see pages 175-178
of Video Demystified: A Handbook For The Digital Engineer (listed in References section).
<TYPE1>
0x81
This is an 8-bit delimiter-less type code for the first subband block of wavelet data. (Model
1 Chroma)
<TYPE2>
0x82
This is an 8-bit delimiter-less type code for the first subband block of wavelet data. (Model
1 Luma)
<TYPE3>
0x83
This is an 8-bit delimiter-less type code for the first subband block of wavelet data. (Model
2 Chroma)
<TYPE4>
0x84
This is an 8-bit delimiter-less type code for the first subband block of wavelet data. (Model
2 Luma)
#SOB1
0xffffffff81
Start of Block delimiter identifies the start of Huffman coded subband data. This
#SOB2
0xffffffff82
delimiter will reset the Huffman decoder if a system ever experiences bit errors or gets
#SOB3
0xffffffff83
out of sync. The order of blocks in the frame is fixed and therefore implied in the bit
#SOB4
0xffffffff84
stream and no unique #SOB delimiters are needed per block. There are 41 #SOB
#SOB5
0xffffffff8f
delimiters and associated BW and Huffman data within a field. #SOB1 is differentiated
from #SOB2, #SOB3 and #SOB4 in that they indicate which model and Huffman table
was used in the Run Length Coder for the particular block:
#SOB1 Model 1 Chroma
#SOB2 Model 1 Luma
#SOB3 Model 2 Chroma
#SOB4 Model 2 Luma
#SOB5 Zero data block. All data after this delimiter and before the next start of block
delimiter is ignored (if present at all) and assumed zero including the BW value.
<BW>
(16 bits, 8.8)
This data code is not entropy coded, is always 16 bits in length and defines the Bin Width
Quantizer control used on all data in the block subband. During decode, this value is used
by the Quantizer. If this value is set to zero during decode, all Huffman data is presumed to
be zero and is ignored, but must be included. During encode, this value is calculated by
the external Host and is inserted into the bitstream by the ADV611/ADV612 (this value
is not used by the quantizer). Another value calculated by the Host, 1/BW is actually used
by the Quantizer during encode.
<HUFF_DATA>
(Modulo 32)
This data is the quantized and entropy coded block subband data. The data’s length is
dependent on block size and entropy coding so it is therefore variable in length. This field is
filled with 1s making it Modulo 32 bits in length. Any Huffman decode process can be
interrupted and reset by any unexpectedly received # delimiter following a bit error or
synchronization problem.
#EOS
0xffffffffc0ffffff
The host sends the #EOS (End of Sequence) to the ADV611/ADV612 during decode after
the last field in a sequence to indicate that the field sequence is complete. The ADV611/
ADV612 does not append this code to the end of encoded field sequences; it must be added
by the host.