SolutionsProduction crews
A gallery that can see every camera, then send one program
This page is for the production room, not a fan application. Vasl takes contribution from the truck, lets the gallery monitor returns, and publishes the program onward.
Publish
Encoders, cameras, browsers and mobile apps open the session.
Vasl
One server you run transcodes, records, authorizes and fans the stream out.
Play
Interactive viewers stay on WebRTC. Broader audiences take HLS from the same publish.
Workflows
What the gallery is doing
Truck contribution
Encoders send RTMP or SRT from the venue. Long or lossy paths are what SRT is for.
Returns on the monitors
The gallery watches incoming cameras in the browser instead of a special player on every screen.
Program publish
The switched output is a separate publish. Receivers can be a private link, a partner, or your own app.
Several venues
Each match or show is a stream you start and stop from the API, so a busy weekend is a list, not a pile of accounts.
Iso recordings
Keep selected returns, not only the program, when the edit happens later.
Cue data
Score, sponsor, or segment markers can travel with the picture for the system that displays them.
On this workload
How Vasl is tuned here
Built for the truck, not the living room
Crews need to see sources and send a program. Audience apps, if you have one, are a separate playback of that program.
- RTMP, SRT, and RTSP in
- WebRTC for monitoring returns
- HLS when a partner just needs the program
- Transcoding when the receive format demands it
A cost you can put on the show budget
The license does not change because the match went long. Size the machine for the number of returns, then run the show.
- Self-hosted beside the gallery or in your cloud
- API control of each publish
- Logs and metrics for the engineer on comms
- Recordings for the post show
Why teams choose Vasl for Live Events
- Returns and a program from one install
- SRT from the venue
- Recordings of the feeds you choose
- A fixed license for the show
Same server
