Multi-site live production streaming

Stream Bridge works with an NDI, OMT, desktop or DeckLink/SDI source available to a paired device - programme outputs, multiviews, camera feeds, clean feeds and graphics returns are typical picks.

Only sources visible to a given desktop device can be selected there. Allow discovery time after connecting, and use local-sources-only filtering on a busy production LAN.

Programme audio can travel with the source, and up to 16 channels are available where the source supports it. Additional tracks and return communication can be configured separately.

Where an audience needs more than the source mix, add separate audio feeds to that link and let them control the level themselves. Return communication is an independent per-link choice.

Encoding can run on NVIDIA NVENC or the CPU. NVENC generally gives the lowest latency and CPU use; CPU mode is useful on systems without compatible hardware or where GPU capacity is already committed.

Each device starts with limits of four GPU and two CPU encodes. Treat these as safety limits rather than performance targets, and watch the live CPU/GPU meters before raising them.

A single active stream can serve browser viewers and multiple receiving devices at once, with bandwidth planned per connection. Every browser viewer and receiving-device bridge is its own connection - plan sender upload for the bitrate multiplied by the number of simultaneous routes.

You can change bitrate live without rebuilding the stream. Most 1080p30 pictures sit comfortably around 3-5Mbps; fast motion or 60fps usually wants 5-10Mbps and a stronger connection.

ICE negotiation finds a usable route without asking either end to open an inbound port. Where the networks allow it, video goes straight between the production device and its viewer or receiver.

Restrictive NAT and firewall policy can force the connection through TURN instead. That reaches more networks, though the extra hop may add delay, so stick to stable wired bandwidth where you can.

Create a different link for each role rather than exposing one universal player - each can have its own URL, password, appearance, audio choices and communication controls while using the same stream.

Anyone with a viewer link can access its feed, so distribute it deliberately and add a password where appropriate. Device connection keys should stay private to whoever manages that machine.