The 20-second opener
“The left side is the cue. The right side is the workflow that turns the cue into a scalable FAST monetization event.”
Then point at the two-player page: same source channel, same opportunity, different layer of technology.
Make the difference obvious.
Use this page to explain SCTE-301 correctly during the show. SCTE-35 is the cue signal. SCTE-301 is the next-generation linear/FAST channel assembly workflow. The easiest sales phrase: “SCTE-35 tells us when. SCTE-301 explains how the channel business operates around that when.”
SCTE-35: the ad-break signal
Cue-out, duration, cue-in, SCTE payload. It identifies the placement opportunity.
VS
SCTE-301: the assembly workflow
Channel assembly, ad policy, session behavior, manifest manipulation, delivery, and as-run reporting.
Open /compare for the visual demo
Upload 2+ MP4 ads for different-ad proof
Say SCTE-301, not SCTE-30
Never say SCTE-301 replaces SCTE-35
Show-floor run of show
0:00
Open /admin
Add a remote HLS source. Upload two short MP4 ads. Assign both ads to the same channel.
0:45
Open /compare
Start both players. Click the scenario cards at the top.
1:15
Point left
“This is SCTE-35. Cue-out, duration, cue-in. It tells us when.”
1:45
Point right
“This is SCTE-301-style workflow context: channel, policy, session, ad selection, and as-run.”
2:15
Show different ads
Left uses basic cue-driven insertion. Right uses policy-selected ad from the channel pool.
3:00
Close
“SCTE-35 is necessary. SCTE-301 makes it operational for FAST and modern linear streaming.”
Six examples sales people can use
Simple break
Same ad opportunity, two explanations.
SCTE-35Break starts now.
SCTE-301This channel/session now needs a policy decision.
Different ads
Two MP4 ads make the value visible.
SCTE-35Insert at cue.
SCTE-301Select eligible creative from the channel ad pool.
Per-session proof
Open two browsers to show independent sessions.
SCTE-35Marker happened.
SCTE-301This session received this decision.
Many FAST channels
One cue standard, many channel workflows.
SCTE-35Break inside one feed.
SCTE-301Scalable assembled channel portfolio.
As-run reporting
What happened after the cue?
SCTE-35Cue-in/cue-out evidence.
SCTE-301Open, select, play, close, report.
Platform delivery
Modern channels go to many endpoints.
SCTE-35Signal can be represented in manifests.
SCTE-301Consistent channel experience across platforms.
Say this / do not say this
Say this
- SCTE-301 complements SCTE-35.
- SCTE-35 remains the precise cue.
- SCTE-301 is the channel assembly and workflow story.
- FAST needs policy, sessions, inventory, manifests, and reporting.
Do not say this
- SCTE-301 replaces SCTE-35.
- SCTE-301 is just another ad marker.
- SCTE-35 alone defines the whole FAST business workflow.
- Every real deployment must use the exact custom demo tag.
Objection handling
Do we still need SCTE-35?
Yes. SCTE-35 is still the cue language. SCTE-301 organizes how a modern platform uses it.
Yes. SCTE-35 is still the cue language. SCTE-301 organizes how a modern platform uses it.
Why not just SCTE-35?
Because markers tell you when. FAST operations also need channel assembly, policy, inventory, sessions, delivery, and reporting.
Because markers tell you when. FAST operations also need channel assembly, policy, inventory, sessions, delivery, and reporting.
Why are the ads different?
That is the point. The left side is cue-driven; the right side demonstrates policy-based selection from assigned ad inventory.
That is the point. The left side is cue-driven; the right side demonstrates policy-based selection from assigned ad inventory.
Is the SCTE-301 tag official HLS syntax?
No. The demo uses a custom visualization tag/event so the audience can see the workflow context. SCTE-301 is not a replacement HLS cue tag.
No. The demo uses a custom visualization tag/event so the audience can see the workflow context. SCTE-301 is not a replacement HLS cue tag.
One table to memorize
Topic
SCTE-35
SCTE-301
Simple explanation
The signal
The workflow
Question answered
When is the ad break?
How does the channel use the opportunity?
Demo proof
Cue-out, cue-in, marker preview
Channel, policy, session, ad decision, as-run
Buyer value
Interoperable timing
Scalable FAST/linear monetization operations
Accuracy note: this demo visualizes SCTE-301-style workflow context with a custom event tag. Present it as a teaching aid, not as formal SCTE-301 HLS syntax.
Final closer
SCTE-35 is the precise ad-break signal. SCTE-301 is the modern FAST/linear operating model that uses that signal to assemble, monetize, deliver, and report channels at scale.
Open the impressive comparisonOpen admin setup