Integrations
SCTE-35 markers, HLS, and VMAP from a finished video.
AdBreak turns each ad break it keeps into a marker your systems already understand: SCTE-35, an HLS marker, or VMAP. Subtitles leave as SRT and WebVTT. Originals, including IMF packages, are pulled from S3, FTP, or HTTP or sent through the HTTP API, and results are uploaded back the same way. AdBreak does not insert the ad.
Delivery formats
| Format | What it carries | Typical receiver |
|---|---|---|
| SCTE-35 | The break time, placed on a frame the player can cut cleanly unless that alignment is turned off. | Playout, server-side ad insertion, packaging you already run |
| HLS marker | The break time as a marker in the HLS playlist your workflow prepares. | HLS players and ad insertion services |
| VMAP | Pre-roll, mid-roll, and post-roll positions for the title. | Client-side players and ad servers |
| Break record | Every break with time, kind of pause, reason, confidence, and distance to speech. | Ad operations, editors, your own systems |
| SRT and WebVTT | Subtitles from the same reading of the speech, translated into 22 languages. | Players, localization teams |
| Credits and lower-thirds | Times of opening and closing credits and of lower-thirds on screen. | Editors, ad operations |
How files and results move
One file at a time
A single title can be sent by hand. The reply explains how the markers will reach you.
HTTP API
Send a file, choose a preset of break rules, and collect the results through the HTTP API.
Originals from S3, FTP, or HTTP
AdBreak pulls each original from your S3, FTP, or HTTP location as it arrives, so nobody uploads titles one by one.
Results back to S3, FTP, or HTTP
The break record, the markers, and the subtitle files are uploaded back to S3, FTP, or HTTP.
Input formats
MP4, MOV, and ProRes files, and IMF packages.
Adding SCTE-35 markers to a library that has none
Many archive episodes were finished before ads were inserted into streams, so they carry no SCTE-35 markers at all. AdBreak reads the finished file, keeps the breaks that pass the checks, and writes an SCTE-35 marker for each one. Your playout or ad insertion system receives the marker and places the ad.
Your systems keep their job
- Your ad server or player inserts and plays the ad.
- Your packaging prepares HLS or DASH. AdBreak does not.
- Your brand-safety tools keep certification and blocking.
Questions about this page
Yes. AdBreak has an HTTP API to send files and collect results, and it can pull originals from S3, FTP, or HTTP and upload results back. For a media asset management system, tell us how files move today and we will explain how it connects.
Related pages
- How it worksHow AdBreak finds ad insertion points in a finished video: picture, speech, silence, and loudness, with a reason and confidence for every break.Read more
- EnterpriseAd break detection for large libraries: originals from S3, FTP, or HTTP, results uploaded back, an HTTP API, and files deleted after processing.Read more
- GlossaryPlain definitions of ad break terms: SCTE-35, HLS markers, VMAP, VAST, SSAI, FAST, AVOD, BVOD, IMF, lower-thirds, presets, and mid-rolls.Read more
Request a pilot on your own files.
Send a few titles you have the rights to mark. Tell us whether you need pre-rolls, mid-rolls, or both, and how markers should reach you. For a large library, say so, and we will explain how files can be processed as they arrive. Pricing starts at $0.70 / €0.70 per hour of video and goes down as your monthly volume grows.