Stream OMT to a web browser

Stream Bridge picks up OMT audio and video sources that the paired device can see. That covers OBS OMT outputs and most other OMT-compatible systems on your local production network.

Only sources the desktop device can actually see will show up, so give it a moment after connecting. On busy networks you can switch on local-sources-only to cut the list down to what's relevant.

Stream Bridge can capture up to 16 audio channels from an OMT source, the same as it does for NDI. These are delivered to the browser as individually controllable tracks, so viewers can select programme audio, clean feeds, commentary or other production channels.

If an audience needs more than the source mix gives them, add separate audio feeds to that link and let them control the level themselves. Return communication is its own setting per link.

Use NVENC on a supported NVIDIA GPU if you have one - it keeps latency and CPU use down. CPU encoding is the fallback for machines without compatible hardware, or when the GPU's already busy with something else.

Each device starts at four GPU encodes and two CPU encodes as a limit. Treat that as a safety net rather than a target, and keep an eye on the CPU/GPU meters before pushing it higher.

OMT itself stays on the local network at the sending end - Stream Bridge only handles the internet-facing WebRTC side. Every viewer gets their own connection, and the bitrate you set applies per viewer, so two people watching at 5Mbps needs about 10Mbps of 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 to match.

The system looks for a direct route first, without asking either end to open a port. Where the networks allow it, video goes straight between the production device and the viewer or receiver.

Strict NAT or firewall rules can force the connection through TURN instead. That gets you connected in more places, but the extra hop can add a bit of delay, so stick to wired connections where possible.

Rather than sharing one link with everyone, create a different one for each role - client, director, operator. Each can have its own URL, password, look, audio choices and communication controls, all from the same stream.

Anyone with the link can access the feed, so share it deliberately and add a password for anything sensitive. Keep device connection keys private to whoever manages that machine.