Engineering6 min read

SRT & RIST: reliable contribution over the public internet

The public internet loses packets; broadcast can’t. SRT and RIST are how you carry a contribution feed over ordinary internet without it falling apart — and why they matter for a leaner headend.

Getting a feed into your headend used to mean satellite or an expensive leased line. SRT and RIST changed that: they make the public internet reliable enough for contribution-grade video, which quietly lowers the cost of sourcing channels.

The problem they solve

Raw UDP over the internet is fast but lossy — a dropped packet is a glitch you can’t get back. TCP recovers loss but adds latency and stalls. Contribution needs both low latency and recovery. SRT and RIST add exactly that: selective retransmission and error handling on top of UDP, tuned for live video.

SRT vs RIST

Why it matters for your headend

SRT/RIST mean a channel can arrive over a normal internet link instead of a satellite dish or a leased line — cheaper to source, faster to add, and one less piece of physical plant to maintain.

How it fits

Once the feed lands, it enters the normal signal chain — packaged, protected, delivered. SRT/RIST is purely about getting it in cleanly. For an operator adding channels, it’s the difference between a procurement project and a config change.

Lessons

This is the kind of problem HySky is built around.

Talk to a team that runs a live operator, not just sells software.

WhatsApp us