SCTE-35
About: SCTE-35 events refer to signaling messages embedded within a video stream, typically used to communicate information about content, such as ad insertion points. These messages contain metadata that indicates specific actions to be taken at designated points in the video, such as the start or end of an advertisement.
In Schedule, the system recognizes SCTE-35 events from TS files seamlessly during the import process. By opening the inspector, users can view these Events ( 1 ) and have the option to move or delete them. SCTE35 events from MPEG-TS live stream inputs are also retained within the video pipeline.
When SCTE35 Triggers are processed, the system displays the actual length of the planned ad-break ( 2 ) in the PGM-Preview window. Users can cancel the ad-break with the cancel button ( 3 ), prompting an immediate write of the SCTE trigger back into the ts output stream for downstream processing.
LTN Schedule Streams re-inserts the SCTE35 triggers from the input signal (live & on-demand) on the configured output stream (PGM). MPEG/TS targets (SRT/TCP) and HLS targets (ts segments) including the SCTE-35 triggers. SCTE35 Events are not available for RTMP Targets.
Make sure that you have also switched on SCTE35 processing on the actual output target!
Info: The HLS targets can also include Cue Out/IN manifest tags and splice point i-frames (new segments at splice points) if the SCTE workflow is activated on the HLS Target.
On the general settings the user can set following optional values:
- Preroll offset in seconds
- The PID (Packet identifier) of the SCTE35 track that is inserted from LTN-Schedule on the output targets.
By default the Sling2 SCTE dialect is used by LTN Schedule. Within the provisioning process we are able to setup other dialects. List of available dialects:
- Sling1
- Sling2
- Youtube
- Amazon
- Comcast
- Hulu
(More / individual dialect adjustment can be done upon request.)
Optional SCTE ad trigger type selection "national" and "local"
You can now differentiate between "national" and "local" ad breaks for SCTE-35. By default Schedule will use "local". With using SCTE35 trigger break type specification, downstream content replacement can be controlled more granularly.
- The SCTE break type options are located under "manage events" section, where you configure your ad-break options.
- SCTE break type are available from Schedule Version 9.7 on.
When the default SCTE-35 dialect is set, "local" breaks are going to be signaled by splice_insert() SCTE-35 messages, while "national" ones will generate time_signal()+insert_segmentation_descriptor( 0x34/0x35 Provider Placement Opportunity Start/End ) messages.
If your target online video platform requires other message formats, please see SCTE-35 options.