Send OMT over WAN

Stream Bridge works with OMT audio and video sources the paired device can see - OBS OMT outputs and most other OMT-compatible systems on the local production network.

The source needs to stay active and reachable. Discovery can take around 30 seconds, and local-sources-only filtering helps simplify busy networks.

Stream Bridge can capture up to 16 audio channels from an OMT source, delivered as individually controllable tracks at the destination.

Viewer links can include additional audio sources with independent level controls. Audio Return and Group Audio can be switched on separately when the remote person needs to speak back to the production.

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.

Default limits are four simultaneous GPU encodes and two CPU encodes per device. Use the meters to raise those cautiously and spot overload before it becomes dropped frames.

Bridge status shows whether the route is connected, connecting, pending, or waiting for the source. Every browser viewer and receiving-device bridge is its own connection - plan sender upload for the bitrate multiplied by the number of simultaneous routes.

Bitrate changes apply live. A practical starting point is 3-5Mbps for most 1080p30 feeds and 5-10Mbps for high-motion or 60fps content, depending on the weakest connection in the path.

No VPN or inbound port forwarding is required. Stream Bridge uses ICE to find a workable path between the sending device and each receiver, preferring a direct connection.

If strict NAT or firewall rules prevent that, the session uses our TURN network instead. It improves reachability, but the extra hop can add latency, so wired internet and sensible bitrate headroom still matter for production-critical feeds.

Viewer links can use readable custom URLs, optional passwords and player customisation, so a client, director, operator and internal team can each receive different controls from the same stream.

Treat device connection keys and viewer links as credentials. Keep connection keys private, password sensitive feeds, and remove links or bridges once an audience no longer needs access.