search

Dash-Industry-Forum / AdInsertion

3 stars 0 forks source link

Support SCTE-35 time signal #64

Open RufaelDev opened 4 years ago

RufaelDev commented 4 years ago

SCTE-35 2019 recommends usage of time_signal command. time signal introduces a higher level fragmentation content. Ad insertion needs to be more clear on how workflows using time_signal can be supported

technogeek00 commented 4 years ago

Do you have more specifics on where we should explicitly ad this in? As part of scte examples on IF-3 or general workflow descriptions on IF-0?

haudiobe commented 4 years ago

time_signal: is an arbitrary marker that some things gonna happen. Metadata can be added what this all means. You use the marker gives a notification event to check other source of information. It does not mean that it is conditioned, but it should be conditioned.

The main reason for this brought up is that a Period is not a sufficient marker for the time_signal. You need to signal SCTE-35 as well. The time_signal is not a signal for a sufficiently conditioned content that would allow easily space content. So no action necessary, we progress this with the conditioning signaling with and without Periods.

We may recommend that at a time_signal point, content should be conditioned.

technogeek00 commented 4 years ago

It looks like this could be folded this into #65 for splice condition signalling downstream, this is something we still intend to address but we've determined SCTE alone is not enough. The MPEG ad-hoc on ad insertion is discussing this topic.

RufaelDev commented 4 years ago

a useful reference: https://mediaperspectives.nl/app/uploads/2018/11/2019-01-29-Media-Perspectives-ETDSS.pdf