没有合适的资源?快使用搜索试试~ 我知道了~
资源详情
资源评论
资源推荐
1 Scope
1.1 This standard specifies the basic formatting
structure of the ancillary data space in the digital
video data stream in the form of 10-bit words.
Application of this standard includes 525-line,
625-line, component or composite, and high-
definition digital television interfaces which
provide 8- or 10-bit data ancillary data space.
1.2 Space available for ancillary data packets is
defined in the document specifying the connecting
interface.
1.3 Ancillary data packet formatting for a
specific application may be according to a
SMPTE standard or recommended practice. In
such a case, the format is considered a regis-
tered format, which is identified by a registered
data identification word.
2 Overview
2.1 The serial digital interface (ANSI/SMPTE
259M) and component parallel digital interface
(ANSI/SMPTE 125M) are capable of passing 10-
bit words (Data 9 -- Data 0), but some of the
existing equipment is only capable of processing
8-bit data words (carried on the interface as Data
9 -- Data 2). The passage of 10-bit words through
such equipment will therefore result in truncation
of the last two LSBs (Data 1 and Data 0) of the
ancillary data word. Upon serializing an 8-bit
word (Data 9 -- Data 2) for a 10-bit word trans-
mission, the two LSBs (Data 1 and Data 0) are
usually replaced by zeros in such equipment.
For these reasons, the original ancillary data
would be corrupted to 6 bits and an 8-bit applica-
tion without restrictions would not be possible.
By reserving specific data identification, 8-bit
words having the two LSBs set to zero for such
an 8-bit data application, operation through a
10-bit interface is possible. These DID words
therefore will not be corrupted either by trunca-
tion or by setting the two LSBs to zero.
2.2 Ancillary data packets are divided into type
1 and type 2, where type 1 uses a single ID word
and type 2 uses two ID words. Using this method
allows for a wider range of identification values
within the limited ID word space. In addition,
a total of 189 data identification values are
reserved for 8-bit applications, whereas up to
approximately 29,000 values are provided for
10-bit applications.
2.3 The basic formats of the ancillary data packets
are similar for both type 1 and type 2, but they
differ in the use of a data block number. The
definitions of the individual parts that make up
the ancillary data packet, such as ancillary data
flags (ADF), data identification (DID), secondary
data identification (SDID), data block numbers
(DBN), data count (DC), data validity checksum
(CS), together with the restrictions on used data,
are contained in this standard.
3 Ancillary data packet format
3.1 Ancillary data packet
3.1.1 The two types of ancillary data packets in
a data stream may be formatted into type 1 and
type 2, which depend upon the data identifica-
tion word. These two types are shown in figures
1a and 1b.
for Television ----
Ancillary Data Packet
and Space Formatting
Revision of
ANSI/SMPTE 291M-1996
SMPTE 291M-1998
SMPTE STANDARD
Page 1 of 14 pages
Approved
October 1, 1998
Copyright © 1998 by THE SOCIETY OF
MOTION PICTURE AND TELEVISION ENGINEERS
595 W. Hartsdale Ave., White Plains, NY 10607
(914) 761-1100
3.1.2 The two types of data identification in the
ancillary data packet format are specified below:
Type 1: Uses a single-word data ID; defined as
data ID (DID) which is followed by data block
number (DBN) and data count (DC).
Type 2: Uses a two-word data identification; defined
as a combination of data ID (DID) and secondary
data ID (SDID) which is followed by data count
(DC).
3.1.3 Ancillary data is defined as 10-bit words.
This is required by the structure of the signal
format and its interface.
3.1.4 Ancillary data packets of type 1 are com-
prised of:
a) an ancillary data flag (ADF) which marks the
beginning of the ancillary packet;
b) a data identification word (DID) which defines
the use of the user data format carried in the ancil-
lary packet’s user data words;
c) a data block number (DBN) word for type 1 only
which distinguishes successive ancillary packets
with common data ID;
d) a data count number word (DC) which defines
the quantity of user data words in the ancillary
packet;
e) the user data words (UDW) of up to 255 words
in each ancillary packet where the user data format
is defined in a specific application document;
f) a checksum word (CS).
3.1.5 Ancillary data packets of type 2 are com-
prised of the same elements as type 1 ancillary
packets, except the data block number (DBN) is
replaced by a secondary data identification word
(SDID).
3.1.6 The length of the ancillary data flag (ADF)
is specified in the document defining the inter-
connecting interface. Unless otherwise noted in
this standard, there are three words for compo-
nent data and one word for composite data.
3.1.7 Either of the two data identification types
may be used with component or composite an-
cillary data packet formatting while maintaining
the same meaning.
ANC Data Packet ANC Data Packet
Data ID
(Type 1) Data Block Number
Data ID
(Type 2) Secondary Data ID
User Data
Words
(max 255)
User Data
Words
(max 255)
Ancillary
Data Flag
Data Count
Checksum Ancillary
Data Flag
Data Count
Checksum
(a) Type 1 (b) Type 2
Figure 1 -- Ancillary data types (component data packets shown)
SMPTE 291M-1998
Page 2 of 14 pages
3.2 Component ancillary data packet format
3.2.1 The format of the component ancillary data
packet is shown in figure 2.
3.2.2 The ancillary data flag for the component
ancillary data packet format is:
000
h
3FF
h
3FF
h
NOTE -- To maximize compatibility between 8- and
10-bit equipment, equipment designers are advised to
process data values of 000
h
-- 003
h
identically. Data
values of 3FC
h
-- 3FF
h
should be processed identically
as well. References in this standard to specific data values
in either of those two ranges should apply to all data values
within the same range.
3.2.3 Definitions of other nonuser data are
specified in 3.4 through 3.11.
3.3 Composite ancillary data packet format
3.3.1 The format of the composite ancillary data
packet is shown in figure 3.
3.3.2 The ancillary data flag for composite ancil-
lary data packet format is 3FC
h
.
NOTE -- Equipment designers should be aware that the
value of composite ancillary data flag 3FC
h
is processed
as referenced in the note of 3.2.2.
3.3.3 Definitions of other nonuser data are
specified in 3.4 through 3.11.
ANC Data Packet ‘‘N’’ ANC Data Packet ‘‘N+1"
Data ID
Secondary Data ID/
Data Block Number Data ID
Secondary Data ID/
Data Block Number
User Data
Words
(max 255)
User Data
Words
(max 255)
Ancillary
Data Flag
Data Count
Checksum Ancillary
Data Flag
Data Count
Checksum
Figure 2 -- Component ancillary data packet format
ANC Data Packet ‘‘N’’ ANC Data Packet ‘‘N+1"
Data ID
Secondary Data ID/
Data Block Number Data ID
Secondary Data ID/
Data Block Number
User Data Words
(max 255)
User Data Words
(max 255)
Ancillary
Data Flag
Data Count Checksum
Ancillary
Data Flag
Data Count Checksum
Figure 3 -- Composite ancillary data packet format
SMPTE 291M-1998
Page 3 of 14 pages
剩余13页未读,继续阅读
jackertja
- 粉丝: 1
- 资源: 22
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 877668389368492摩托车队经理.apk
- IDM下载器官网免安装包,注册CMD文件,突破30天的限制
- qud.win.1.1-installer-10053.9.zip
- adb-r-linux.zip adb-r-linux.zip
- 对光伏出力预测的优化设计,实现了部分功能(注释完全,可直接运行)(文档加Matlab源码)
- 70-android.rules
- 可用于光伏出力预测,引入气象影响因子,效果良好(注释完全,可直接运行)(文档加Matlab源码)
- 利用白噪声特性和ARMR模型,通过求解模型参数生成随机风速(注释完全,可直接运行)(文档加Matlab源码)
- 51-android.rules
- RecationTest.zip
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
评论2