Remote guest SDI output is the missing link between an easy browser call and a professional control room. The guest should be able to join without learning broadcast technology, while the production team needs a stable, clean signal that can be routed into an ATEM or another vision mixer like any other source.
This guide explains the complete signal path from a remote browser to a DeckLink SDI output, the decisions that matter before airtime, and how Falcon Live is designed to simplify the operator workflow.
What a remote guest-to-SDI workflow needs to solve
Consumer meeting software is built around a composed meeting window. Broadcast production normally needs something different: a clean guest feed, predictable output routing, a return path, and an operator who stays in control. The goal is not merely to see and hear the guest. The goal is to turn that guest into a production source.
A practical workflow must cover five stages:
- The guest receives a link and joins from a supported browser.
- The operator checks the guest’s camera, microphone and connection in a lobby.
- The guest is assigned to a production output.
- The contribution is converted into a configured SDI signal through a DeckLink device.
- The guest receives the appropriate studio return so the conversation feels natural.
The signal path: browser to WebRTC to DeckLink
The browser captures the remote camera and microphone and sends them through a real-time contribution connection. At the receiving location, Falcon Live presents the guest to the operator before routing the contribution to an output. A Blackmagic Design DeckLink card then provides the physical SDI connection used by the control room.
In simplified form, the path is:
Guest browser → internet contribution → Falcon Live operator → assigned output → DeckLink SDI → vision mixer
This separation is important. The guest never needs to understand SDI, frame formats or switcher routing. Those decisions stay with the production team.
Why DeckLink output fits a traditional control room
DeckLink hardware turns a software contribution into a familiar baseband source. Once the output format matches the switcher, the remote guest can be handled alongside studio cameras, playout channels and graphics. The director can preview, cut, key or route the guest using the production’s existing workflow.
Before a show, confirm:
- Which physical DeckLink connector belongs to each Falcon Live output.
- Whether the connector is configured for capture or playback.
- The resolution and frame rate expected by the vision mixer.
- How embedded audio is routed into the audio workflow.
- Which studio source is sent back to the guest.
The output standard must agree with the receiving device. A format mismatch can appear as a black picture, an unstable image or a signal the switcher refuses to lock to. Treat frame rate and video standard as part of the control-room configuration, not as a setting the remote guest should manage.
SDI versus screen capture workarounds
A common workaround is to maximize a meeting window and capture it with an extra converter or software scene. That can be sufficient for an occasional stream, but it adds operational risks: interface elements can appear on air, scaling may change, notifications can interrupt the feed, and separate guests are harder to route cleanly.
Dedicated SDI outputs create a clearer boundary between the communication interface and the on-air signal. The operator manages the guest in one place, while the switcher receives a purpose-built output.
Keep the return path separate from the contribution
The outgoing guest feed is only half of a live interview. The guest also needs to see or hear the correct studio return. That may be a program feed, a presenter camera, a multiview-derived source or another production-specific signal.
Return routing should be planned so the guest can follow the programme without hearing a delayed copy of their own voice. Our detailed guide to program return, mix-minus and IFB for remote guests explains that audio path in more depth.
A repeatable pre-flight checklist
- Send the guest link early. Give the contributor time to choose a quiet location, power the device and test the connection.
- Use the lobby. Check framing, lighting, microphone selection and audio level before assigning an output.
- Confirm the SDI standard. Verify the DeckLink output and switcher input use compatible settings.
- Test the return. Ask the guest to confirm what they see and hear.
- Check lip sync. Use a clear clap or sync test before the programme begins.
- Keep a fallback. Agree on a phone number or audio-only path if the guest’s internet connection changes.
Where Falcon Live fits
Falcon Live is built around the operator rather than the meeting window. Guests enter through a simple company link, join from their browser and wait in a lobby. The production team can check video and audio, communicate with the guest, crop the contribution and route it to configured DeckLink SDI or NDI outputs.
For productions that want the simplest possible guest experience, see our guide to browser-based remote contribution without a guest app. For a broader evaluation checklist, read how to choose remote guest interview software for professional broadcast.
Frequently asked questions
Can a remote browser guest go directly into an ATEM switcher?
Yes, when the receiving system converts the guest contribution to a compatible SDI output. A DeckLink output can be connected to an ATEM input, provided the video standard and connector configuration match the switcher.
Does the guest need a DeckLink card?
No. The DeckLink hardware is installed at the receiving production location. The remote guest uses a camera and microphone through a supported browser.
Should I choose SDI or NDI for a remote guest?
Use SDI when the signal must enter a traditional vision mixer or router through physical video infrastructure. Use NDI when the production is designed around compatible video-over-IP tools on a managed network. Some workflows use both at different points.
How much internet bandwidth does a remote guest need?
There is no single number that covers every camera, network and quality setting. A stable upstream connection, low packet loss and consistent latency are usually more important than a high headline download speed. Always perform a real test from the guest’s actual location.
Planning a remote guest workflow with SDI or NDI? Book a Falcon Live demo and describe the switcher, DeckLink hardware and return sources in your control room.