Nimbus puts SCTE-35 markers into your channel's outputs, from the schedule or the API. Dynamic ad insertion happens downstream, for example in AWS Elemental MediaTailor, and the channel and its ad revenue stay yours.
Ad breaks come from the schedule, or are triggered through the REST API or MCP.
Nimbus writes SCTE‑35 markers into the TS‑based outputs.
Your ad insertion service, for example AWS Elemental MediaTailor, swaps the break for targeted ads.
Veset doesn't sell ads or share revenue. You own the channel and what it earns.
SCTE-35 in the transport stream over SRT caller or listener.
SCTE-35 in transport stream outputs over UDP, RTP and RTP-FEC.
SCTE-35 in HLS and ABR HLS, for OTT and FAST platforms.
SCTE-35 in outputs sent through MediaConnect.
RTMP has no standard ad-marker format, so there are no SCTE-35 markers on RTMP outputs.
V-Chip content advisory signalling, alongside the ad markers.
Ad-supported linear channels for FAST platforms, launched within an hour.
HLS and ABR HLS with SCTE-35 for your own apps and CDN.
Markers in transport stream outputs to your distribution partners.
An operator triggers pre-configured ad breaks over a live feed, for example during live sports.
No. Nimbus provides the SCTE-35 markers, and dynamic ad insertion happens downstream, for example in AWS Elemental MediaTailor.
TS-based outputs over SRT, UDP/RTP and MediaConnect, and HLS. Not RTMP, which has no standard ad-marker format.
Yes. Markers come from the schedule or the REST API, and an AI assistant can use the same functions through the Nimbus MCP server.
No. Veset is a technical partner. You own the channel and its revenue.
Yes, with AdWise. An operator triggers pre-configured ad breaks over the live feed.
Tell us how your channel is delivered and which ad insertion service you use or plan to use.
Or email sales@veset.tv.
We'll reply to . Sales requests get an answer within five business days.