Broadcasting

SCTE-35 for Developers: Ingest, Pass-Through, DAI, and Testing

SCTE-35 is small metadata with large consequences

SCTE-35 markers tell downstream systems when to insert ads, switch content, blackout regions, or trigger events.

The payload looks tiny compared with video. The business impact does not. A missed splice point can break monetization. A drifted marker can fire an ad late. A stripped marker can ruin a distribution deal.

Developers should treat SCTE-35 as production data, not decoration.

Where SCTE-35 shows up

You may see SCTE-35 in:

  • MPEG transport streams
  • Live contribution feeds
  • Playout systems
  • Cloud encoders
  • DAI platforms
  • HLS manifests through mapped metadata
  • DASH workflows through event signaling
  • Monitoring and compliance tools

Each handoff can preserve, alter, map, or drop the marker. That creates the real engineering work.

The common jobs

Most applications need one or more SCTE-35 behaviors.

Pass-through:
Receive markers and send them downstream without changing intent.

Inspection:
Parse markers, display fields, log events, and alert on bad data.

Generation:
Create splice insert or time signal messages from automation, UI actions, or scheduling data.

Mapping:
Convert SCTE-35 from transport stream metadata into HLS or DASH signaling.

Validation:
Compare expected ad breaks against actual markers and playback behavior.

Start by naming the job. The code changes by job.

Pass-through is harder than it sounds

Teams often say, "Just pass the markers through."

Then the workflow changes container, segmenter, encoder, timestamp base, output protocol, or cloud service. The marker can drift, duplicate, disappear, or land on the wrong boundary.

Test pass-through with:

  • Program start
  • Short ad break
  • Long ad break
  • Back-to-back breaks
  • Early termination
  • Late marker
  • Missing out marker
  • Multiple audio tracks
  • Frame-rate changes
  • Encoder restart

Do not test one perfect splice and call it done.

Timing rules matter

SCTE-35 lives inside a timed media workflow. That means clock and timestamp handling decide whether the marker works.

Track:

  • PTS alignment
  • Segment boundaries
  • Encoder delay
  • Packager delay
  • Manifest update timing
  • Player buffer
  • Ad server response time

A marker can leave the encoder on time and still fire late for a viewer if the rest of the chain adds delay.

DAI needs clean contracts

Dynamic ad insertion connects media engineering with ad operations. That mix creates bugs when teams do not define ownership.

Define:

  • Who creates the marker
  • Which fields matter
  • Which system can alter the marker
  • How long a break can run
  • What happens when no ad fills
  • How blackout rules work
  • How logs prove delivery

Write this down before launch. Ad tech integrations fail in the gaps between teams.

Developer test cases

Build a test fixture that can generate known marker patterns.

Include:

  • 30-second break
  • 60-second break
  • Break with early return
  • Break with missing return
  • Marker with unexpected duration
  • Two breaks less than 10 seconds apart
  • Marker during encoder reconnect
  • Marker near segment boundary
  • Marker with multiple variants
  • Marker across failover

Log both the raw marker and the interpreted event. Operators need to see what came in and what your system did with it.

Monitoring and alerts

Add SCTE-35 to the operations screen.

Show:

  • Last marker time
  • Next expected break
  • Break duration
  • Event ID
  • Marker type
  • Pass-through status
  • Mapping status
  • Errors and warnings

Alerts should catch missing markers, impossible durations, duplicate IDs, and downstream mapping failures.

Common mistakes

Dropping metadata during transcode:
The video looks fine, so nobody notices until ads fail.

Ignoring variant alignment:
ABR variants need consistent ad behavior. One clean variant does not prove the whole ladder works.

Testing only VOD-like cases:
Live encoders restart. Networks fail. Operators click late. Test ugly cases.

Hiding marker details:
If support cannot inspect the marker, support cannot fix the workflow fast.

Where Medialooks fits

Medialooks Video SDK helps developers build video applications that ingest, process, record, playout, and stream live media across broadcast and IP workflows. For SCTE-35-related products, the SDK can sit inside tools that inspect streams, preserve metadata paths, add overlays, record feeds, or bridge protocols.

SCTE-35 work rewards discipline. Parse the marker. Preserve timing. Prove the downstream result.