How a SCTE-35 cue is structured
A SCTE-35 splice_info_section is a binary message that starts with a table_id of 0xFC followed by length, optional encrypted fields, the pts_adjustment, a splice_command_type, the command body, and finally a descriptor loop. Each segmentation_descriptor in that loop carries the meaning of the event - is this a provider ad start, a network ad end, a content break, a chapter, a placement opportunity?
Common splice_command_type values
| Hex | Name | Body | When used |
|---|---|---|---|
0x00 | splice_null | None | Heartbeat / spec test |
0x04 | splice_schedule | One or more events at a UTC wall-clock time | Splices scheduled ahead of time |
0x05 | splice_insert | splice_event_id, out-of-network flag, duration, splice_time | Legacy explicit splice point |
0x06 | time_signal | splice_time | Modern marker - meaning carried by descriptors |
0x07 | bandwidth_reservation | None | Reserve bandwidth for an event |
0xFF | private_command | Vendor-defined | Operator-specific signaling |
Common segmentation_type_id values
| Hex | Name | Meaning |
|---|---|---|
0x10 | Program Start | Program begins at this PTS |
0x11 | Program End | Program ends |
0x20 | Chapter Start | Chapter boundary - skip target |
0x21 | Chapter End | Chapter boundary - end |
0x30 | Provider Advertisement Start | National / provider ad break begins |
0x31 | Provider Advertisement End | National / provider ad break ends |
0x32 | Distributor Advertisement Start | Local / distributor ad break begins |
0x33 | Distributor Advertisement End | Local / distributor ad break ends |
0x34 | Provider Placement Opportunity Start | SSAI insertion point begins |
0x35 | Provider Placement Opportunity End | SSAI insertion point ends |
0x36 | Distributor Placement Opportunity Start | Distributor insertion point begins |
0x37 | Distributor Placement Opportunity End | Distributor insertion point ends |
0x40 | Unscheduled Event Start | Network start |
0x41 | Unscheduled Event End | Network end |
Splice descriptors in the descriptor loop
| Tag | Name | What it carries |
|---|---|---|
0x00 | avail_descriptor | A provider_avail_id that identifies the avail (the break) |
0x01 | DTMF_descriptor | A DTMF tone sequence (0-9, * and #) and a preroll, for splicers that still listen for tones |
0x02 | segmentation_descriptor | What the event is, its duration and a content identifier (UPID) |
0x03 | time_descriptor | Wall-clock time in TAI seconds and nanoseconds, with the UTC offset |
0x04 | audio_descriptor | Audio component information |
SCTE-35 and cue tones
Before digital cues, networks signaled local ad breaks with cue tones: audio tones, often DTMF or subaudible, that told the automation equipment at a station or cable headend when to roll a local commercial. In digital and IP delivery those tones became digital messages carried in the stream, and in North America that message is typically SCTE-35 (background on cue tones).
The standard kept a bridge to the old equipment. The DTMF_descriptor carries the tone sequence itself, plus a preroll in tenths of a second that says how long before the splice point the tones should finish (Comcast's SCTE-35 library documents the fields). When engineers talk about a cue-out and a cue-in today, they mean the SCTE-35 cue that leaves the network feed for a break and the one that returns to it.
How SCTE-35 appears in an HLS playlist
In HLS the binary cue rides in a playlist tag. Paste any of these lines into the decoder as they are; it pulls the payload out of the tag.
| Tag | Defined by | What it carries |
|---|---|---|
#EXT-X-DATERANGE with SCTE35-OUT, SCTE35-IN or SCTE35-CMD | The HLS specification (RFC 8216) | The whole splice_info_section, as hex |
#EXT-X-CUE-OUT, #EXT-X-CUE-OUT-CONT, #EXT-X-CUE-IN | A widely supported convention, not the HLS specification | The start of a break with its duration, progress through it, and its end |
#EXT-OATCLS-SCTE35 | A convention, usually on the same segment as EXT-X-CUE-OUT | The splice_info_section, as base64 |
Ad insertion services read all three styles; AWS Elemental MediaTailor's list of supported HLS ad markers is a good reference. The 24/7 channels OTTEngine runs mark their ad breaks with EXT-X-DATERANGE and SCTE35-OUT.
Worked examples
Three sample messages from the SCTE 35 standard, decoded field by field. Each one passes its CRC-32 check, and each button loads it into the decoder above.
| Field | Example 1 | Example 2 | Example 3 |
|---|---|---|---|
| Command | splice_insert | time_signal | time_signal |
| Event | splice_event_id 1207959695, out of network | segmentation_event_id 1207959694 | segmentation_event_id 1207959694 |
| Splice time (PTS) | 1,936,310,318 ticks (05:58:34.559) | 1,924,989,008 ticks (05:56:28.767) | 1,952,616,608 ticks (06:01:35.740) |
| Duration | 5,426,421 ticks (60.294 s), auto-return | 27,630,000 ticks (307.000 s) | None |
| Descriptor | avail_descriptor, provider_avail_id 309 | segmentation_descriptor 0x34 Provider Placement Opportunity Start | segmentation_descriptor 0x35 Provider Placement Opportunity End |
| UPID | None | type 0x08, 000000002CA0A18A | type 0x08, 000000002CA0A18A |
| CRC32 | 0x62DBA30A, valid | 0x9AC9D17E, valid | 0xA9CC6758, valid |
Example 1 is a classic cue-out: leave the network at the given PTS for 60.3 seconds, then return automatically. Examples 2 and 3 are a pair. The start opens a 307-second placement opportunity, and the end carries the same event ID and UPID, which is how a downstream system matches the two. Their PTS values are 306.973 seconds apart, within 27 milliseconds of the duration the start announced, which is exactly the kind of cross-check to run on your own cues.
Frequently Asked Questions
What is SCTE-35?
SCTE-35 is the standard signaling format that tells downstream systems where ad breaks, program boundaries, and content metadata occur in a video stream. It is delivered as a binary splice_info_section in MPEG-2 Transport Streams or referenced by HLS EXT-X-DATERANGE and DASH EventStream entries.
How do I decode a SCTE-35 cue?
Decode the base64 or hex payload to bytes, then parse the splice_info_section: table_id, length, splice_command_type, command body, then a descriptor loop of segmentation_descriptors. Each segmentation_descriptor has a segmentation_type_id that names the event (for example 0x30 = Provider Advertisement Start).
What is the difference between splice_insert and time_signal?
splice_insert is older and explicitly directs a downstream splicer to switch at a given PTS. time_signal carries the splice point as a single PTS and relies on segmentation_descriptors for what the event is. Modern workflows favor time_signal + segmentation_descriptors.
How do PTS values map to seconds?
PTS ticks at 90,000 per second, so seconds = pts_ticks / 90000. A 30-second ad break covers 30 × 90,000 = 2,700,000 ticks.
What are SCTE-35 cue tones?
Cue tones were audio signals, often DTMF or subaudible tones, that told a station or cable headend when to insert a local ad. SCTE-35 replaced them with digital cue messages carried in the stream, and its DTMF_descriptor can still carry the tone sequence for older equipment.
How does SCTE-35 appear in an HLS playlist?
The HLS specification carries the whole message in hex in an EXT-X-DATERANGE tag, as SCTE35-OUT, SCTE35-IN or SCTE35-CMD. The widely used EXT-X-CUE-OUT and EXT-X-CUE-IN tags mark a break's start and end instead, often with the base64 cue in an EXT-OATCLS-SCTE35 tag. You can paste any of those lines into the decoder.
Why does a decoder say the CRC does not match?
Every splice_info_section ends with a CRC-32 computed over the whole message. A mismatch means the cue was truncated, re-encoded or altered after it was created, so treat the decoded values with suspicion and check the source.