Need stream distribution and receiver automation for your event? Get in touch at info@streamcontrol.co
What Stream Control does
The control layer for a live event. It provisions the outbound feeds, publishes the players, watches every SRT link, and runs the AWS servers those feeds sit on.
SRT egress automation
Approve a registration and the outbound feeds are created for that contributor. Primary and backup SRT outputs are set up as caller or listener, with RTMP pull when the event uses it, and provisioned on the streaming servers. Automatic creation can be turned off per contributor type, and feeds can still be added by hand.
Event player management
Each stage has a public player you choose: Video.js, THEOplayer, or SLDP. Set the player size, put the live item on the stage, and give viewers a single page for that stage.
Feed distribution
A stage feed is assigned as SRT primary and backup, with transcoder and RTMP variants and extra languages where the event needs them. Those feeds are then sent to every approved destination.
SRT stats for receivers and senders
SRT health is collected from every server, for inputs and outputs: round-trip time, jitter, and packet loss, with live graphs and a stats page per feed. Event stats can be shared with a link, so someone outside the dashboard can watch the same numbers.
AWS server management
Streaming and production servers are created in your organisation's own AWS account. Activate a region, choose the VPC, subnet, and instance size, then start, stop, and place servers into pools from one screen.