Live video gateway

SRT encoding explained

SRT is widely used by broadcasters for contribution over the internet. Encoding for SRT combines codec choice, latency tuning, and careful network configuration.

What is SRT encoder software?

SRT (Secure Reliable Transport) is an open protocol for low-latency video transport over unreliable networks. An SRT encoder takes a live video source, such as SDI, NDI, or ST2110, encodes it with H.264 or HEVC, and pushes it as SRT to a listener, caller, or rendezvous endpoint.

The encoder does more than compress the video. It paces packets, handles ARQ retransmission requests from the receiver, manages AES-128 or AES-256 encryption, and tunes latency to the link characteristics. If any of these is set wrongly, the link can drop under load.

Why it matters for broadcast

Contribution over the public internet once relied on RTMP and a good deal of luck. SRT adds retransmission, encryption, and tunable latency, which make it workable on links that broadcasters previously refused to use.

Software SRT encoders on GPU servers also scale more easily than hardware boxes. A single server can run many SRT encodes in parallel, all managed from the same operator interface.

GPU-accelerated SRT encoding in BridgeWIZ

BridgeWIZ encodes SRT from SDI, NDI, ST2110, RTMP, HLS, or screen-capture inputs, with NVIDIA NVENC encoding, configurable latency, ARQ retransmission, and AES-128/256 encryption. One server can run multiple simultaneous SRT encodes, all from the same UI.

What to get right

Latency budget

Set SRT latency to 2-4x the measured round-trip time. If it is too short, packets are lost; if it is too long, it adds visible delay.

Bitrate to link

Match encoded bitrate to the worst-case link bandwidth, not the average. Heavy ARQ overhead can saturate marginal links.

Encryption discipline

AES encryption on SRT adds very little processing load. Enable it by default for contribution and rotate keys for each session.

Frequently asked questions

What latency should I configure?

Set it to 2-4x the measured round-trip time. A link with a 50 ms RTT runs comfortably at 100-200 ms SRT latency. Measure under realistic load.

H.264 or HEVC?

Use H.264 for compatibility with older receivers and HEVC for bitrate efficiency on bandwidth-constrained links. NVENC accelerates both on the GPU.

What is the practical SRT latency floor?

Around 80 ms end to end on a local LAN. Real-world internet contribution typically runs at 200-500 ms.

Can I run AES-256 without performance impact?

Yes. SRT crypto is light enough that even AES-256 has negligible cost on modern hardware.

Listener, caller, or rendezvous?

Caller mode, with the encoder pushing out, is the default. Listener mode is for one-to-many distribution, and rendezvous mode is for NAT traversal.

Get started

See BridgeWIZ working with your sources

Book a demo and our broadcast engineers will demonstrate BridgeWIZ using your sources, destinations, and channel requirements.