SCTE-35 vs SCTE-301: clear visual demo

Same stream · same ad opportunity · different level of technology

AdminSingle playerSales playbook

The difference in one sentence

SCTE-35 is the precise ad-break cue. It says “an ad opportunity starts here and ends there.” SCTE-301 is the next-generation linear / FAST channel assembly workflow. It explains how a platform uses cues together with channel assembly, ad policy, session behavior, manifest manipulation, delivery, and as-run reporting.

SCTE-35 = signal

Marker-level technology. Cue-out, duration, SCTE payload, cue-in. It is the “when” of ad insertion.

VS

SCTE-301 = workflow

System-level recommended practice. Channel assembly, ad policy, sessions, delivery, and reporting. It is the “how this becomes a FAST business.”

Demo rule: left shows cue behavior
Demo rule: right shows orchestration behavior
Best visual: upload 2+ ads so each side can choose differently
Important: SCTE-301 complements SCTE-35; it does not replace it
As-run CSVReady. Add channels and ads in /admin first.

Six examples that make the difference obvious

Click any card. The explanations under both players, the comparison table, and the talk track update to show what SCTE-35 can express versus what SCTE-301 adds around the same cue.

SCTE-35 Player

The cue-level view: detect the ad opportunity, insert an ad, return to content.

CUE / MARKER LEVEL
What SCTE-35 provesA cue-out tells the player/proxy an ad opportunity is open.
waiting
Next break--
Ad selected--
Decision basiscue only
Start both players to see SCTE-35 cue markers.

SCTE-301 Player

The workflow-level view: use the same opportunity in a FAST/linear assembly system.

CHANNEL ASSEMBLY / POLICY LEVEL
What SCTE-301 provesThe platform chooses, explains, and reports the outcome.
waiting
Next break--
Ad selected--
Decision basispolicy + session
Start both players to see SCTE-301 workflow context.

What the left side can show

  • There is an ad placement opportunity.
  • The expected duration is known.
  • The system can switch to an ad at cue-out.
  • The system can return to content at cue-in.
  • The evidence lives mainly in markers and timing.

What the right side adds

  • Which assembled channel this belongs to.
  • Which viewer session is being served.
  • Which ad policy was applied.
  • Which creative was eligible and selected.
  • How the event is reported as an as-run record.
When vs WhySCTE-35 answers when the break starts. SCTE-301 explains why this channel/session/ad decision happened.
Marker vs ModelSCTE-35 is a marker signal. SCTE-301 is a model for scalable channel assembly and distribution.
Single break vs portfolioSCTE-35 handles a break. SCTE-301 helps operate many channels, platforms, and business rules.
Playback vs operationsSCTE-35 drives insertion timing. SCTE-301 gives sales/ops a story about monetization and reporting.

Animated workflow: how the same opportunity becomes a FAST business event

1
Source HLSremote stream
2
SCTE-35 cuebreak starts
3
SCTE-301 contextchannel + policy
4
Ad decisioneligible creative
5
Manifest actionreplace/insert
6
Viewer sessionper-session state
7
As-runproof/report

Booth line #1

“The left side sees a cue. The right side sees a business event.”

Booth line #2

“SCTE-35 is necessary, but it is not the whole FAST operating model.”

Booth line #3

“SCTE-301 turns cueing, content, ad inventory, delivery, and reporting into a scalable channel assembly workflow.”

Accuracy note for sales people: this demo uses a custom EXT-X-TULIX-SCTE301-DEMO tag/event to visualize SCTE-301-style workflow context. SCTE-301 should not be described as a replacement HLS marker for SCTE-35. It is a recommended practice for next-generation linear/FAST channel assembly that uses SCTE standards together.