Nimbus plays the channel out from the schedule, file and live events alike, with graphics, DVE and SCTE-35 markers triggered by the schedule or the API. When a live input drops, the playout falls back on its own and alerts you. Operators can take over at any point.
HTML5 templates take their data from the schedule or the API.
Graphics driven by playlist or asset metadata, from XML or other sidecar files.
L-shape, credit squeeze and picture-in-picture, triggered from the schedule or the API.
Ad markers from the schedule or the API on TS-based outputs (SRT, UDP/RTP, HLS, MediaConnect). Not on RTMP, which has no standard ad-marker format.
V-Chip content advisory signalling.
XMLTV generated from the same schedule.
The playout detects that the live signal has stopped.
It switches to a backup input, or to the emergency playlist or slate.
You get an alert by email or webhook, for example in Slack.
When the signal returns, the playout goes back to the live input.
Automation runs the channel, and an operator can take over at any point from the console, the REST API or MCP.
Take a chosen event or skip the current one, after a short delay or at a set time.
Apply the emergency playlist by hand, not only when a live input drops.
Live events sit in the schedule alongside file events.
Fire graphics or SCTE-35 markers over a live source, immediately or at an offset from the start or end of the live event.
The full platform, for scripts and integrations with your own systems.
The full Nimbus API for AI assistants, at https://mcp.veset.tv/mcp.
Playlists dropped into an S3 or SFTP folder are imported automatically.
Alerts delivered to the tools your team already watches.
Live preview, playout status and output status in the console.
A record of what actually went to air.
Uptime reports for your playouts, in the console.
By email and webhooks, for example to a Slack channel.
Every user and API action, including changes made by an AI agent.
The playout falls back to a backup input or the emergency playlist or slate, sends an alert, and returns to live when the signal comes back.
No. With 1+1 hot backup you receive two identical feeds, and your receiver or MCR chooses which one goes on air. See redundancy.
Yes. Take a chosen event, skip the current one or apply the emergency playlist, from the console, the REST API or MCP.
By email and webhooks, for example to Slack.
Yes. The REST API covers the full platform, and the Nimbus MCP server gives AI assistants the same functions.
Yes. The console has as-run logs and uptime reports, and an audit log of user and API actions.
Typical latency from live input to output is 2-5 s with SRT in and SRT or TS out, which suits 24/7 linear channels, news and most live events.
Tell us how your channel runs today and what your operators do by hand, and we'll show what Nimbus automates.
Or email sales@veset.tv.
We'll reply to . Sales requests get an answer within five business days.