Supported Sources
Enable Audio Return independently on any viewer link.
Stream Bridge Audio Return sends a remote viewer's microphone back to the production as a named NDI or OMT source - useful for talkback, commentary or cueing talent, straight from the browser they're already watching in.
Send the link to the person who needs to talk back, such as a director.
Switch it on per link and they get a microphone control in their player.
They pick a mic and speak from the browser they're already watching in.
Their voice arrives on your paired device as a named NDI or OMT source.
Audio Return adds a live path from the viewer back to the paired device. Switch it on for a viewer link and they get a microphone control right in their player - no second app needed for a director to talk to the control room, or a commentator to contribute clean audio.
It's set per viewer link, so only the people who need a microphone get one. They pick a mic, can mute locally, and reconnect from the same browser player they're already watching from.
We handle the real-time connection automatically and create a named output on your paired device, which you then route through your normal mixer, intercom or recording workflow.
Because the return path is part of Stream Bridge, it uses the same direct-first connection and cloud fallback as the video - one joined-up experience for the viewer, independent control for you.
To get started straight away, join our beta, download the application, and get streaming. We also have a host of documentation available that goes through all of the features of Stream Bridge, troubleshooting issues, and our support team are ready to help if needed.
A closer look at browser microphone capture, return quality, production outputs, latency, connection handling and access control.
Enable Audio Return independently on any viewer link.
Browser audio returned as a named NDI or OMT source.
Each return path runs as its own session.
Low-latency voice built for talkback and cues, not delayed messaging.
Direct connection first, cloud fallback if that's blocked.
Return access is set per viewer link.
Practical answers about browser microphones, production outputs, routing, permissions and live talkback.
When the viewer activates their microphone, Stream Bridge creates a named audio source through whatever output formats are enabled for that device - selectable in compatible NDI or OMT software and routable like any other live input.
Yes, it's set per viewer link, so a director or commentator can get a microphone path while client and public links stay view-only.
No. The control is built into the Stream Bridge browser player - they just grant mic permission, choose their input, and enter the name used for the returned source.
Yes. They can mute from the control, switch inputs in player settings, and disconnect the return without leaving the live video.
Yes - route it to a mixer, commentary workflow, comms path or talent cue. The final result still depends on their microphone, connection and your audio routing.
We fall back to cloud relay automatically when NAT or firewall policy blocks the direct route. The viewer doesn't need a VPN or any port configuration.