Playout software turns a channel's schedule and media into a continuous on-air signal, with graphics, subtitles and ad markers, encoded for a satellite uplink, a distributor or a streaming platform. Veset Nimbus does this for 24/7 TV, FAST and OTT channels.
It imports your playlists, switches live sources, and runs from a browser, the REST API or an AI assistant through MCP.
Import BXF, XML, XLSX, CSV or JSON from the console, the API or an S3/SFTP watch folder. Custom formats get a parser during onboarding. An XMLTV EPG is generated from the schedule.
MPEG-2, H.264, HEVC, XDCAM HD, ProRes, XAVC and JPEG XS files in MXF, MOV, MP4 and other containers, ingested from any S3-compatible storage or SFTP.
SRT, HLS, RTMP, RTP-FEC 2D and JPEG XS natively, Zixi and RIST through AWS MediaConnect. Automatic fallback to a backup input or the emergency playlist.
HTML5 rendered in the playout (your own pages with live RSS/JSON work as-is), After Effects import, L-shape and squeeze DVE.
SCTE-35 from the schedule or the API on TS-based outputs.
CEA-608/708, DVB bitmap, WebVTT, burn-in and ARIB B24/B40.
H.264, HEVC or MPEG-2, SD to 4K UHD, AAC, AC-3 and E-AC-3 audio, several outputs per playout.
The browser console, the full REST API, and the public MCP server.
Most broadcasters run more than one channel. In Nimbus, channels in the same account share what they can and differ where they need to.
Channels in one account use the same content library and schedules.
The same operators run all channels in the account, without switching accounts through SSO.
Create a channel for another time zone, or a time-delayed version, by transposing the main channel's playlists.
Run a channel where most content matches the main channel, but the ad breaks, compliance edits or graphics differ.
Each channel's playout runs on an instance sized to it. No licence limits on inputs, outputs or resolution.
One MCP connector can manage the playouts of all organisations under a service provider, such as a reseller.
Software that plays a channel's schedule out as a continuous signal. It runs files and live feeds in order, adds graphics, subtitles and ad markers, and encodes the result for delivery. Veset Nimbus does this in the cloud, on AWS or Hetzner.
The part of playout software that runs the schedule and produces the outputs. In Nimbus each channel's playout runs on an instance sized to the channel, and two synchronised playouts can run as a 1+1 pair.
Yes. Channels in one account share the content library and schedules, the same operators run all of them, and a channel can be based on a main channel, for example a time-shifted version or a variant with different ad breaks.
BXF, XML, XLSX, CSV and JSON. If your scheduling system uses its own format, Veset builds a parser for it during onboarding.
Yes. Nimbus imports its playlists through the console, the API or an S3/SFTP watch folder, and your system stays the source of truth.
UDP, RTP, RTP-FEC, SRT, HLS, RTMP and HTTP natively, plus Zixi and RIST through AWS MediaConnect. Each playout can have several outputs with their own encoder settings.
Yes, 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.
Yes. The REST API covers the full platform, and the same functions are available to AI assistants through the Nimbus MCP server.
How many channels you run, how they're delivered, and which ones share content.
Or email sales@veset.tv.
We'll reply to . Sales requests get an answer within five business days.