SMPTE RDD 43-2016 MDA Bitstream Specification.pdf
《SMPTE RDD 43-2016 MDA Bitstream Specification.pdf》由会员分享,可在线阅读,更多相关《SMPTE RDD 43-2016 MDA Bitstream Specification.pdf(32页珍藏版)》请在麦多课文档分享上搜索。
1、 Copyright 2016 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved August 23, 2016 The attached document is a Registered Disclosure Document prepared by the proponent identified below. It has been examined by the appropriate SMPT
2、E Technology Committee and is believed to contain adequate information to satisfy the objectives defined in the Scope, and to be technically consistent. This document is NOT a Standard, Recommended Practice or Engineering Guideline, and does NOT imply a finding or representation of the Society. Ever
3、y attempt has been made to ensure that the information contained in this document is accurate. 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, including inquiries as to intellectual property r
4、equirements that may be attached to use of the disclosed technology, should be addressed to the proponent identified below. Proponent contact information: Scott Smyers DTS, Inc. 130 Knowles Drive, Suite B Los Gatos, CA 95032 Email: Page 1 of 32 pages SMPTE REGISTERED DISCLOSURE DOCUMENT MDA Bitstre
5、am Specification SMPTE RDD 43:2016 SMPTE RDD 41:2016 Page 2 of 32 pages Table of Contents Page Conventions 4 Introduction (Informative) . 4 1 Scope . 6 2 Normative References 6 3 Structures 6 3.1 Bitstream .6 3.2 Frames .7 3.3 Slice 9 3.4 Entity 10 3.5 LFEFragment . 12 3.6 ObjectFragment 12 3.7 Grou
6、p 13 3.8 Switch . 14 3.9 NormalizedGroup . 15 4 Packets . 16 4.1 General . 16 4.2 FrameHeaderPacket . 16 4.3 AssetFramePacket 18 4.4 Frame End Packet . 19 4.5 Slice Header Packet 19 4.6 ObjectFragmentPacket . 20 4.7 LFEFragmentPacket 20 4.8 Group Start Packet . 20 4.9 Group End Packet . 21 4.10 Swit
7、chStartPacket . 21 4.11 SwitchEndPacket 21 4.12 EntityPacket 21 4.13 FragmentPacket . 22 4.14 MonoSourceFragmentPacket . 22 4.15 UnknownPacket . 22 5 Common Data Structures 23 5.1 PacketHeader . 23 5.2 ChannelGain . 23 5.3 RenderingException . 23 5.4 Label . 24 5.5 PackedLength . 25 5.6 Extension 25
8、 SMPTE RDD 41:2016 Page 3 of 32 pages 5.7 FixedArray 26 5.8 Position 26 5.9 ByteArray . 27 5.10 PackedUInt64 . 27 5.11 PackedUInt32 . 27 5.12 OptionalItem 27 5.13 UTF8String 27 6 Common Functions 28 6.1 RadiusQToF 28 6.2 RadiusFToQ 28 6.3 PhiQToF . 28 6.4 PhiFToQ . 28 6.5 ThetaQToF . 28 6.6 ThetaFTo
9、Q . 28 6.7 ApertureQToF 28 6.8 ApertureFToQ 28 6.9 DivergenceQToF 28 6.10 DivergenceFToQ 28 6.11 GainQToF . 28 6.12 GainFToQ . 28 6.13 ChannelGainQToF 29 6.14 ChannelGainFToQ 29 7 Constants . 29 7.1 Packet Kind Labels . 29 7.2 Bitstream Version 29 7.3 Normalized Group Label 29 8 Extensibility 29 9 A
10、uthoring Guidelines 30 10 Structure Specification Language . 30 10.1 Macro . 30 10.2 Structure . 30 10.3 Basic Type . 31 10.4 Type Aliasing . 31 10.5 Control Statements 31 10.6 Fields . 31 10.7 Variables 32 10.8 Constants 32 SMPTE RDD 41:2016 Page 4 of 32 pages Conventions All sections are normative
11、, unless otherwise indicated. Pseudo-code and property names use font style courier new. The expressions MAY, NEED NOT, SHALL, SHALL NOT, SHOULD, and SHOULD NOT indicate normative behavior as specified in ISO/EIC Directives, Part 2. Edition 6.0, 2011-04. VERBAL FORM SEMANTICS MAY It is allowed NEED
12、NOT It is not required that SHALL Is required that SHALL NOT Is required to be not SHOULD It is recommended that SHOULD NOT It is not recommended that Introduction (Informative) The Bitstream consists of an ordered sequence of Packets. As illustrated in Figure 1, each Packet consists of a payload pr
13、eceded by a Label field identifying the nature of the payload and a length field indicating the size of the payload. Packet are byte-aligned, but information within their payloads not necessarily so. Implementations can skip over Packets without knowledge of their payload, enabling straightforward e
14、xtensibility. Figure 1 Packet Packets are logically grouped into hierarchical structures. Specifically, as depicted in Figure 2, a Bitstream consists of a sequence of Frame structures, each containing the metadata and audio samples required to completely reproduce a Program for a specified interval
15、within its timeline. In particular, each Frame structure contains a complete copy of the Program header information, thereby allowing playback to start on any Frame structure boundary without requiring access to prior or future Frames. K indLengthP ayloadP acke tSMPTE RDD 41:2016 Page 5 of 32 pages
16、Figure 2 Mapping Program to Bitstream Frame Structures As illustrated in Figure 3, Frame structures are further segmented, with Program header information followed by Fragment structures, each containing Entity metadata for a specified time interval within the timeline of the Frame. The audio sample
17、s associated with the Frame are contained in a sequence of Asset Frame Packets. Figure 3 Frame Structure The Program object model makes extensive use of URI as unique identifiers. To reduce overhead, this specification defines mappings between common URI values and shorter Label values. F r ame F r
18、ame F r ame F r ameP rogram Entiti e s ( ti me li n e )P rogramHe ad e rFrameHeaderPacketAssetFramePacketAssetFramePacketSliceHeaderPacketFrameEndPacketUnknownPacketSliceHeaderPacketGroupStartPacketGroupEndPacketObjectFragmentObjectFragmentObjectFragmentObjectFragmentframesl ice sl iceSMPTE RDD 41:2
19、016 Page 6 of 32 pages 1 Scope This specification maps the MDA Program specified in the MDA Program Specification, including audio samples, to a single binary structure the Bitstream. The Bitstream is partitioned into Frames such that reproduction can start at any Frame boundary, without knowledge o
20、f earlier or future Frames. 2 Normative References MDA Program Specification 1.03 Internet Engineering Task Force (IETF) (January 2005). RFC 3986 Uniform Resource Identifier (URI): Generic Syntax ISO/EIC Directives, Part 2. Edition 6.0, 2011-04 Internet Engineering Task Force (IETF) (January 2003).
21、RFC 3629 UTF-8, A Transformation Format of ISO 10646 3 Structures The Bitstream syntax is expressed using the operation of a hypothetical parser using the structure specification language described in Section 10. For extensibility, the Bitstream syntax allows the presence of unknown Packets captured
22、 by fields of type UnknownPacket. Implementations MAY ignore these unknown Packets. 3.1 Bitstream A Bitstream consists of an ordered sequence of Frames, as specified in Table 1. Each Frame is an item of the fFrame collection. The number of Frames in an MDA Bitstream for a given MDA Program SHALL be
23、less than or equal to 264. Table 1 Bitstream Structure aligned struct Bitstream var long unsigned int i = 0; while(!eof) peek PacketHeader fUnknownHeader; / Frames if (fUnknownHeader.fKind = FrameHeaderPacket.fKind) Frame fFramei+; / Unknown packets SMPTE RDD 41:2016 Page 7 of 32 pages else UnknownP
24、acket fUnknownPacket; 3.2 Frames A Frame SHALL correspond to an interval within a Program timeline, with the Program uniquely identified by the fFrameHeaderPacket.fProgramURI field. The MDA:Program.header object is specified by the fFrameHeaderPacket field. The audio samples required for the reprodu
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
10000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- SMPTERDD432016MDABITSTREAMSPECIFICATIONPDF
