Skip to content
Testaroo
xml472 B

SCTE-35: Splice Insert (Break End / Return to Network)

The matching return cue for the break-start splice_insert in this group: the same spliceEventId with outOfNetworkIndicator false, signalling the feed is coming back from the ad break. It carries no BreakDuration because the return is explicit rather than automatic. Pairing start and end cues by event id is exactly what an ad-insertion implementation has to get right, and this is the pair to test it on.

Ad insertionStreaming manifestsVideo QA
Preview, first 9 linesxml
<?xml version="1.0" encoding="UTF-8"?>
<SpliceInfoSection xmlns="http://www.scte.org/schemas/35" protocolVersion="0" ptsAdjustment="0"
                   tier="4095" sapType="3">
  <SpliceInsert spliceEventId="1001" spliceEventCancelIndicator="false" outOfNetworkIndicator="false"
                spliceImmediateFlag="false" uniqueProgramId="1" availNum="1" availsExpected="1">
    <Program><SpliceTime ptsTime="3420000"/></Program>
  </SpliceInsert>
</SpliceInfoSection>

Specifications

Standard
SCTE-35
Command
splice_insert
Splice Event Id
1001: matches the break-start cue
Out Of Network
false: returning to the network feed
Pts Time
3420000 (38.0s at 90 kHz)
Break Duration
absent: an explicit return, not an auto-return
Alt Text
The matching return cue for the break-start splice_insert in this group: the same spliceEventId with outOfNetworkIndicator false
Alt Text Source
description

Testing contract

Expected to pass
Scenario
Parse the message and match it against the break-start signal in this group.
Expected result
A `splice_insert` with `outOfNetwork` false at PTS time 3420000 (38.0s at 90 kHz), carrying splice event ID 1001 - the same ID as the break-start fixture, which is how the two are paired. There is deliberately no break duration: this is an explicit return to the network feed rather than an auto-return, so a parser that expects every splice to carry a duration fails here.

What is a .xml file?

XML (Extensible Markup Language) is a verbose, self-describing markup language using nested tags, attributes, and namespaces to represent structured, hierarchical data. It supports schemas, entities, and validation and underlies many document and data formats. It remains common in enterprise, publishing, and interchange contexts.

How to use this file

Use an example XML file to test parsers, namespace and schema validation, XPath queries, and protection against entity-expansion and external-entity attacks.

How to use this file for testing

“SCTE-35: Splice Insert (Break End / Return to Network)” is a deterministic Testaroo fixture for Ad insertion, Streaming manifests, Video QA. VAST ad responses and SCTE-35 splice descriptors covering linear break signalling, wrappers, and companion creatives, for testing ad-decision integration and manifest-manipulation logic without calling a real ad server.

Documented properties for this file: XML · 472 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Media fixtures are short and synthetic by design. Prefer waveform or transcript ground truth in the same group when measuring ASR, trim, upscale, or sync tools; do not assume broadcast-quality masters.

Code examples

import xml.etree.ElementTree as ET

tree = ET.parse("scte35-break-end.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])

Generated by generation/video_timedtext.py. Free for any use, no attribution required, license.

Related files