31.12.2014 Views

ANSI/SCTE 30 2009

ANSI/SCTE 30 2009

ANSI/SCTE 30 2009

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 7-7 Splice_Response_Data<br />

Syntax Bytes Type<br />

Splice_Response_Data {<br />

Splice_Offset 2 tcimsbf<br />

}<br />

Splice_Offset – This shall be set to zero unless used to send delay information. The offset<br />

information is in milliseconds. A negative value is a request for the insertion channel content<br />

to be delivered earlier; a positive value is a request for the insertion channel content to be<br />

delivered later.<br />

The Splice_Offset field is expected to be used by Splicing devices which achieve seamless<br />

operation by altering the Primary Channel propagation delay through the Splicer. When such<br />

a device is commanded to splice in the absence of <strong>SCTE</strong> 35 cue messages, the Splicer does<br />

not have the opportunity to advance or retard the Ad Server’s ad timing via alteration of the<br />

equation in converting pts_time to UTC time (because there are no <strong>SCTE</strong> 35 cue messages<br />

and hence no conversion and no Cue Request Messages). In such a case, a Splicer may<br />

utilize the new Splice_Offset field to advance or retard the Ad Server to match the Splicer’s<br />

output service timing following each Splice_Request message.<br />

7.5.3. SpliceComplete_Response Message<br />

The SpliceComplete_Response message is sent when the insertion starts and finishes. This is<br />

true for Back-To-Back Insertions as well. For example, if two pieces of content play, four<br />

SpliceComplete_Response messages are returned, one at the start of the first piece of<br />

content, one upon completion of the first piece of content, one upon the start of the second<br />

piece of content and one upon completion of the second piece of content. The result code in<br />

the header shall properly indicate the failure reason if the splice failed so that the Server can<br />

take appropriate action. The splice-in and splice-out are separate events and shall be treated as<br />

such. If a splice between two pieces of content fails, the splice-out should indicate good status<br />

if the current piece of content played in its entirety. The SpliceComplete_Response message<br />

shall be sent immediately upon failure of any splice event and shall not wait until the expected<br />

duration of the inserted content.<br />

The data( ) field for this message contains the SpliceComplete_Response_Data structure<br />

outlined below.<br />

Table 7-8 SpliceComplete_Response_Data<br />

19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!