SMPTE ST 312M-2001 Television - Splice Points for MPEG-2 Transport Streams.pdf

《SMPTE ST 312M-2001 Television - Splice Points for MPEG-2 Transport Streams.pdf》由会员分享，可在线阅读，更多相关《SMPTE ST 312M-2001 Television - Splice Points for MPEG-2 Transport Streams.pdf（20页珍藏版）》请在麦多课文档分享上搜索。

1、SMPTE STANDARD for Television - Splice Points for MPEG-2 Transport Streams SMPTE 31 2M-2001 Revision of SMPTE 312M-1999 1 Scope This standard defines constraints on the encoding of and syntax for MPEG-2 transport streams such that they may be spliced without modifying the PES packet payload. Generic

2、 MPEG-2 transport streams, which do not comply with the constraints in this standard, may require more sophisticated techniques for splicing. The constraints specified here are applied individually to programs within transport streams. A program is a collection of video, audio, and data streams whic

3、h share a common time base. The presence of a video component is not assumed. The standard enables splicing of programs within a multiprogram transport stream either simultaneously or independently. Splice Points in different programs may be presentation- timecoincident, but do not have to be. The s

4、tandard may also be used with single-program transport st reams. The document specifies constraints for both seamless and nonseamless Splice Points. Seamless Splice Points must adhere to all the constraints. Nonseam- less Splice Points must adhere to all constraints ex- cept those prefaced with the

5、clause “to enable seamless splicing.“ A bit stream which is compliant with this standard shall conform to the constraints defined in clauses 5 and 6. Such a bit stream may contain any number of seamless, nonseamless, or both types of Splice Points. If a bit stream does not contain splice event comma

6、nd and control informa- tion, the constraints in clause 7 do not apply to the bit stream. Mechanisms for transmission of time code in MPEG-2 transporVelernentary bit streams shall be addressed by other standards. Page 1 of 20 pages In addition to constraints for creating spliceable bit streams, this

7、 standard specifies the technique for carrying notification of upcoming Splice Points in the transport stream. A splice information table is defined for notifying downstream devices of splice events, such as a network break or return from a network break. The splice information table which pertains

8、to a given program is carried in a separate PID stream referred to by that programs program map table. In this way, splice event notification can pass through transport stream remultiplexers without need for spe- cial processing. A bit stream which is compliant with this standard and which carnes sp

9、lice event command and control information shall conform to the con- straints in clauses 5, 6, and 7. The standard does not address constraints on splicing devices. Annex A outlines several issues that should be considered in the design of such devices. NOTE - Numbers given in brackets are subject t

10、o confirma- tion. 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 valid. All standards are subject to revision, and parties to agreements based on

11、this standard are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. ATSC N53, Digital Television SMPTE 12M-1999, Television, Audio and Film - Time and Control Code Copyright 8 2001 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS

12、 595 W. Hartsdaie Ave., White Plains. NY 10607 (914) 761-1100 Approved June 25,2001 SMPTE 312M-2001 ITU-T H.222.0 (OUOO) / ISO/IEC 1381 8-1, Information Technology - Generic Coding of Moving Pictures and Associated Audio Information: Systems ITU-T H.262 (OUOO) / ISO/IEC 13818-2, Information Technolo

13、gy - Generic Coding of Moving Pictures and Associated Audio Information: Video 3 Introduction 3.1 Buffer issues Splicing of MPEG bit streams requires managing buff er fullness of the decoders buff ers. When MPEG bit streams are encoded, there is an inherent buffer occupancy at every point in time (s

14、ee figure 1). The buff er fullness corresponds to a delay, the amount of time that a byte spends in the buffer. When splicing two separately encoded bit streams, the delay at the Splice Point will not usually match. This mismatch in delay can cause the buffer to overflow or underflow at some time in

15、 the future (see figure 2). To avoid unpredictable underflows and overflows, two splicing techniques have been defined. The seamless splicing method requires that the MPEG encoder match the delay at splicing points to a given value. The nonseamless method does not require the en- coder to match the

16、delay. Instead, the splicing device is responsible for matching the delay of the new material and the old material as well as it can. In some cases, this will result in a controlled decoder buff er underflow. This underflow can be masked in the de- coder by holding the last frame of the outgoing vid

17、eo and muting the audio until the first access unit of the new stream has been decoded. In the worst case, this underflow may lastforafewframetimes. Bothsplicing methods may cause an underflow of the audio buffer, and consequently a gap in the presentation of audio at the receiver. The perceived qua

18、lity of the splice in both cases will benefit from audio decoders that can handle a gap in audio data gracefully. 3.2 Splice Points To enable the splicing of compressed bit streams, this standard defines Splice Points. Splice Points in an MPEG-2 transport stream provide opportunities to switch from

19、one program to another. They indicate a safe place to switch, a place in the bit stream where a switch can be made, and result in good visual and audio quality. In this way, they are analogous to the vertical interval used to switch uncompressed video. Unlike uncompressed video, frame boundaries in

20、an MPEG-2 bit stream are not evenly spaced. Therefore, the syntax of the transport packet itself is used to convey where these Splice Points occur. Transport streams are created by multiplexing PID streams. In this standard, two types of Splice Points for PID streams are defined: Out Points and In P

21、oints. In Points are places in the bit streams where it is safe to enter and start decoding the bit stream. Out Points are places where it is safe to exit the bit stream. Ways to group In Points of individual PID streams into Program In Points in order to enable the switching of entire programs (vid

22、eo with audio) are defined. Program Out Points for exiting a program are also defined. Out Points and In Points are imaginary points in the bit stream located between two transport stream packets. An Out Point and an In Point may be co-located; that is, a single packet boundary may serve as both a s

23、afe place to leave a bit stream and a safe place to enter it (see figure 3). The output of a switching operation (see figure 4) will begin with packets from one stream up until its Out Point followed by packets from another stream start- ing with the first packet following an In Point. 3.3 Program S

24、plice Points Part of this standard describes requirements for grouping In Points of a set of PID streams into Pro- gram In Points and for grouping Out Points of a set of PID streams into Program Out Points. Program In Points and Program Out Points are sets of PID stream In Points or Out Points which

25、 correspond in presen- tation time to the underlying data. In MPEG, audio is typically organized into audio frames. Because video and audio frames have different durations and their presentation times do not necessarily align, this standard defines exactly what it means for PID stream Splice Points

26、to correspond in time. Figure 5 shows a splice between two programs, one called the old stream and one called the new stream. Each program contains a video PID and an audio PID. The output of the splice is shown below the two input streams. In the old stream, the position of PID stream Out Points wh

27、ich create a program Out Point is shown. In the new stream, the position of PID stream In Points which create a Program In Point is shown. Page 2 of 20 pages SMPTE 3121111-2001 Buffer Fullness Splice Point I c I 4 t 1 Time - Start-up Delay Splice Decoding Delay Figure 1 - Fullness of a theoretical d

28、ecoders buffer model (as described in ISOAEC 13818-2 annex C) Here is an example of an old stream and a new seam that results in a spiice ovdow. Old Stream I Splice Point At the time of the splice bits hm the old stream stop entering the buffer and bits hm the new stream begin entering. When spliced

29、 the two streams overflow the bder. Spliced Stream Figure 2 - Example of decoder buffer overflow as a result of an unconstrained splice Page 3 of 20 pages SMPTE 31 2M-2001 Out Point Out Point out Point stream r) Tc 3 + 2 In Point In Point Figure 3 - In Points and Out Points in a PID stream OR Pant I

30、n Point bom the sam t ? t videoPID Thelcst byteof Point Packet thepcylcdis theicst byteof a CCddPorI pi dure Pdd Figure 4 - Example of a co-located Out Point and In Point in a video PID stream Old Stream Video Frames Program Out Point 5 161 61 71 Audio Frames ;A ,I Audio Frames Figure 5 - Presentati

31、on time representation of a Program Out Point and a Program In Point Page 4 of 20 pages CMPTE 312M-2001 Although Splice Points in a Program Splice Point correspond in presentation time, they do not usually appear near each other in the transport stream. Because compressed video takes much longer to

32、decode than audio, the audio Splice Points may lag the video Splice Points by as much as hundreds of milli- seconds and by an amount that can vary from moment to moment (this relationship is shown infigure6). This standard defines the relationship of Splice Points in bit stream order as well as in p

33、resentation time. 3.4 Splice events This standard provides a method for in-band signal- ling of schedule, preroll, and execute splice event messages to downstream splicing equipment. A splice event identifies which Splice Point to use for a splice. A splice information table carries splice events. E

34、ach splice event is analogous to a cue tone. The splice information table incorporates the functionality of cue tones and extends it to enable the scheduling of splice events in advance. This standard establishes that the splice information table be carried on a per-program basis in a PID stream wit

35、h a designated stream-type. The programs splice information PID is designated in the programs program map table. In this way, the splice information table is switched with the program as it goes through remultiplexing operations. A common stream-type identifies all PID streams which carry splice inf

36、orma- tion tables. Remultiplexers may use this stream-type field to drop splice information prior to sending the transport stream to the end-user device. 4 Definition of terms Throughout this standard the terms below have given specific meanings. Because some of the terms which are defined in ISO/IE

37、C 13818 have very spe- cific technical meanings, the reader is referred to the original source for their definition. For terms defined by this standard, brief definitions are given below. More extensive descriptions of some terms are given in 3.2. Constraints in clause 5 provide the specific technic

38、al definition. 4.1 ATSC: Advanced Television Systems Com- mittee. 4.2 bslbf: Bit string, left bit first, where left is the order in which bit strings are written. 4.3 decoding delay: The time from when a packet enters the decoder buffer until it is removed. 4.4 DTS: Decoding time stamp (see ITU-T H.

39、222.0 / ISO/IEC 13818-1). 4.5 DTS-nea-AU: DTS value of the next access unit (see ITU-T H.222.0 / ISO/IEC 13818-1). 4.6 first presentation unit (FPU): In regard to an In Point, the presentation unit which follows the given In Point that has the earliest presentation time. 4.7 4:2:2PML: 422 Profile at

40、 Main Level (see ITU-T H.262 / ISO/IEC 13818-2). Corresponding Splice Points Transport Stream Video 1 Audio I - Audio appears Figure 6 - Bit stream order representation of a Program Out Point Page 5 of 20 pages SMPTE 31 2M-2001 4.8 In Point: A point in a PID stream where a splicing device may enter.

41、 4.9 In Point packet (IPP): The first packet after an In Point in a PID stream. 4.10 last presentation unit (LPU): In regard to an Out Point, the presentation unit which precedes the given Out Point that has the latest presenta- tion time. 4.11 max-splice-rate: (see ITU-T H.222.0 / I SOA EC 1 381 8-

42、1 ) . 4.12 MPBHL: Main Profile at High Level (see ITU-T H.262 / ISO/IEC 13818-2). 4.13 MP8ML: Main Profile at Main Level (see ITU-T H.262/ ISO/IEC 13818-2). 4.14 Out Point: A point in a PID stream where a splicing device may exit. 4.15 Out Point packet (OPP): The last packet prior to an Out Point in

43、 a PID stream. 4.16 PCR: Program clock reference (see ITU-T H.222.0 / ISO/IEC 13818-1). 4.17 PCR-flag: (see ITU-T H.2220 / ISO/IEC 1381 8-1). 4.18 PCR-PID: Identifier carried in the program map table. The PID contained in a program that has been selected to carry the PCR (see ITU-T H.222.O / ISO/IEC

44、 13818-1). 4.19 PES: Packetized elementary stream (see ITU-T H.222.0 / ISO/IEC 13818-1). 4.20 picture-structure: (s e e IT U -T H .2 62 / ISO/IEC 13818-2). 4.21 PID: Packet identifier; a unique 13-bit value used to identify the type of data stored in the packet payload (see ITU-T H.222.0 / ISO/IEC 1

45、381 8-1). 4.22 PID stream: All the packets with the same PID within a transport stream. 4.23 PMT: Program map table (see ITU-T H.222.O / ISO/IEC 13818-1). 4.24 Profile8Level: Designation of the subset of the MPEG-2 video coding specification (see ITU-T H.262 / ISO/IEC 13818-2). 4.25 program: A colle

46、ction of video, audio, and data PID streams which share a common time base. 4.26 Program In Point (PIP): A group of P ID stream in Points which correspond in presenta- tion time. This standard defines correspon- dence. PID streams with In Points contained in a Program In Point may be a subset of all

47、 PID streams contained within a program as defined by the PMT. 4.27 Program Out Point (POP): A group of PID stream Out Points which correspond in presen- tation time. This standard defines correspon- dence. PID streams with Out Points contained in a Program Out Point may be a subset of all PID strea

48、ms contained within a program as defined by the PMT. 4.28 program splice point (PSP): Either a Pro- gram Out Point or a Program In Point. 429 progressive-frame: (see ITU-T H.262 / ISO/IEC 13818-2). 4.30 progressive-sequence: (see ITU-T H.262 / ISO/IEC 13818-2). 4.31 PTS: Presentation time stamp (see

49、 ITU-T H.222.0 / ISO/IEC 13818-1). 4.32 repeat-first-field: (s e e I TU - T H .2 6 2 / ISO/IEC 13818-2). 4.33 rpchof: Remainder polynomial coeffi- cients, highest order first. 4.34 seamless-splice-flag: (see ITU-T H.222.0 / ISO/IEC 13818-1). 4.35 sequence-end-code: (see ITU-T H.262 ISO/I EC 1381 8-2). 4.36 splice-countdown: (see ITU-T H.222.0 / ISO/IEC 13818-1). 4.37 splice-decoding_delay: (see ITU-T H.222.0 / ISO/I EC 1381 8-1). Page 6 of 20 pages SMPTE 312M-2001 4.38 spliceevent: A splice of one or more PID streams. 4.39 Splice Point: A point in a PID stream that is either an Out