The short version
| Name | Defined by | What it says | Where it travels | Who reads it |
|---|---|---|---|---|
| SCTE-35 | SCTE (ANSI/SCTE 35, digital program insertion cueing messages) | A splice point: where a break starts or ends, often with a duration | Inside the stream, or translated into the manifest (MPEG-TS, HLS, DASH) | Packagers, server-side ad insertion and ad decision systems |
| HLS markers (EXT-X-DATERANGE, EXT-X-CUE-OUT and EXT-X-CUE-IN) | Apple’s HLS specification (DATERANGE); CUE tags are a widely used packager convention | The same break, written into the HLS playlist | The HLS media playlist | HLS players and ad insertion servers |
| VMAP | IAB Tech Lab | A playlist of breaks: when each one plays, what type it is, where its ads come from | A separate XML document the player requests | Client-side ad players and SDKs |
| VAST | IAB Tech Lab | One ad response: creative files, tracking, click-through | XML returned by an ad server | Players and server-side ad insertion |
SCTE-35: a signal about the stream
SCTE-35 is a cueing message standard from SCTE. A message carries a command and a time. The common commands are splice_insert, which marks leaving the program and returning to it, and time_signal, which is paired with a segmentation descriptor that says what the time stands for, such as the start or end of a program, a chapter or a placement opportunity.
In broadcast, the messages travel as their own data stream next to the video in an MPEG transport stream. For HLS and DASH they are translated into manifest tags or events. What they never carry is the ad. SCTE-35 tells a downstream system where a break is and, optionally, how long it lasts. What plays in that gap is decided somewhere else.
A splice point only works if the stream can be cut there cleanly. For video that means a frame the decoder can start from, which is why break times for SCTE-35 are best placed on or snapped to a keyframe.
HLS cue markers: the same break in a playlist
Inside an HLS playlist a break appears either as an EXT-X-DATERANGE tag carrying SCTE35-OUT, SCTE35-IN or SCTE35-CMD attributes, which the HLS specification defines, or as the older EXT-X-CUE-OUT and EXT-X-CUE-IN tags that many packagers and ad insertion servers still use. Which one your setup expects depends on your packager or ad insertion vendor, so ask before you generate anything. The tag below is the CUE form, shown with a 60-second break.
#EXTINF:6.000,
segment_0123.ts
#EXT-X-CUE-OUT:DURATION=60
#EXTINF:6.000,
segment_0124.ts
...
#EXT-X-CUE-IN
#EXTINF:6.000,
segment_0134.tsVMAP: a playlist of breaks for a player
VMAP is an XML document that tells a player where the breaks in a piece of content are. Each AdBreak has a timeOffset, which can be start, end, a time such as 00:12:30.000, a percentage or a position number, plus a breakType (linear, nonlinear or display) and an AdSource that carries or points to the ad response. Because VMAP lives outside the video, it suits players that request their own ads. It says nothing about the frames at the offset, so the time still has to be a good place to cut.
<vmap:VMAP xmlns:vmap="http://www.iab.net/vmap-1.0" version="1.0">
<vmap:AdBreak timeOffset="00:12:30.000" breakType="linear" breakId="mid-1">
<vmap:AdSource id="mid-1-source" allowMultipleAds="false" followRedirects="true">
<vmap:AdTagURI templateType="vast3"><![CDATA[https://ads.example.com/vast?break=mid-1]]></vmap:AdTagURI>
</vmap:AdSource>
</vmap:AdBreak>
</vmap:VMAP>VAST: the ad inside the break
VAST, from the same IAB Tech Lab family, is what an ad server returns for one request: which creative files to play, which tracking URLs to call and where a click goes. It has no idea where in your programme the break is. That is why a VMAP AdBreak points at a VAST response, and why a server-side ad insertion system takes its break position from SCTE-35 or manifest markers and its ad from VAST.
Which one does your video need?
- Server-side ad insertion, FAST channel playout or a packager: ask which marker it ingests. It is usually SCTE-35 or HLS markers, and the vendor’s documentation names the exact form.
- Your own player with client-side ads: a VMAP playlist is the usual way to hand the player the break positions, and many client-side ad SDKs accept it.
- A mix of platforms: one set of break times can be written in all three forms, because each is just a different place to put the same times.
Decide the times first and the format second. Choosing good break positions is the hard part; the formats are packaging.
Where AdBreak fits
AdBreak reads a finished video file and returns the break times with the kind of pause, a reason, a confidence between 0 and 1 and the distance to speech. The same times can leave as SCTE-35, an HLS cue or VMAP, and SCTE-35 points snap to a keyframe unless that is turned off. AdBreak does not insert the ad and does not prepare the stream: your ad server supplies the VAST response and your player or packager does the insertion. See how it works and the integrations page.