SCTE 35 Part 1
splice_command_type
Enumerated values
Clause citations
| Value | Dec | Name | Description | History | Related |
|---|---|---|---|---|---|
| 0x00 | 0 | splice_null | A heartbeat or descriptor-only message. It carries no splice timing itself and is often used to keep a link alive or to deliver a segmentation descriptor on its own. | ||
| 0x04 | 4 | splice_schedule | Announces one or more future splice events well ahead of time. Each scheduled event is later confirmed by a matching splice_insert closer to air. | ||
| 0x05 | 5 | splice_insert | The classic splice_insert message: signals a specific splice in or out of the network feed at a given time, optionally with a break duration. | ||
| 0x06 | 6 | time_signal | Marks a point in time without directly commanding a splice. It carries meaning through the segmentation (or, in SCTE 35 Part 2, event) descriptors attached to it. It is widely used for modern segmentation and event signaling, though splice_insert remains in common use; the choice depends on the downstream contract and carriage (for example HLS EXT-X-DATERANGE maps both). | added 2011 | |
| 0x07 | 7 | bandwidth_reservation | Reserves a consistent amount of transport-stream bandwidth in a multiplex by keeping its PID's packets present at the intended repetition rate, rather than holding room for one specific later message. It signals no splice. | added 2011 (Reserved in the 2001 edition; defined from 2011.) | |
| 0xff | 255 | private_command | A vendor-specific command identified by a registered format identifier. Its body is defined by the owner, not by SCTE 35. | added 2011 (Reserved in the 2001 edition; defined from 2011.) |