Convert DeckLink / SDI to WebRTC

Stream Bridge captures video from anything running through compatible Blackmagic hardware and Blackmagic Desktop Video - capture cards, HDMI and SDI are all supported, covering cameras, vision mixers, routers and replay outputs.

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

Stream Bridge can capture up to 16 audio channels embedded in the source, the same as it does for NDI, delivered to the browser as individually controllable tracks.

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

A supported NVIDIA GPU encodes through NVENC with barely any CPU impact - normally the best fit beside live production software. CPU encoding is the fallback when there's no compatible hardware, or it's 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.

Runtime checks and clear in-use errors help spot hardware conflicts before a production starts. Every viewer is a separate connection, and your configured bitrate applies to each one - two viewers at 5Mbps needs roughly 10Mbps upload.

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, media travels directly 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.