Translate a StreamYard broadcast in real time

StreamYard is the browser-based studio of choice for creators who multistream — webinars, podcasts, interview shows, small-business marketing broadcasts going out to YouTube, LinkedIn, Facebook, and X simultaneously. It hides the complexity of OBS behind a clean browser UI: invite a guest with a link, drop in branding, hit “Go Live,” and the same feed reaches every destination platform at once.

That simplicity comes with a constraint, though: StreamYard runs entirely in the browser. There is no plugin ecosystem, no virtual audio cable support, no way to inject a translated audio track into the broadcast. For creators with an international audience, that has historically meant subtitles after the fact — or nothing.

Loquira solves this without touching the browser. The microphone you already use for StreamYard produces a signal that more than one application can read in parallel. StreamYard reads it for the broadcast; a second device running Loquira reads the same signal for translation.

The parallel pattern in a browser studio

The mental model is the same as for OBS Studio but simpler in execution, because StreamYard does not let you near its audio chain. There is nothing to misconfigure. The host’s microphone feeds StreamYard’s browser tab. A phone or tablet on the desk runs Loquira and reads the same voice from across the room. Each non-English viewer scans the QR code from the StreamYard banner overlay and listens in their own language while watching the broadcast on the main screen.

The link distribution is the only thing different from a pure OBS workflow: because StreamYard multicasts to several destinations, the Loquira link needs to appear in every destination’s chat — YouTube chat, LinkedIn live comments, Facebook Live comments. Most creators paste it into each chat at the start as a pinned message and again every ten or fifteen minutes for late arrivals.

Recommended setup

• Microphone. Whatever StreamYard already uses — USB condenser, XLR through an interface, or headset. The microphone guide covers the trade-offs. Close-mic positioning matters more than mic price.
• Loquira device. A phone with a tripod, sitting on the desk near your microphone. The phone’s built-in mic picks up your voice in parallel with the studio mic feeding StreamYard.
• Brand assets. Upload the Loquira QR as a PNG into StreamYard’s brand library. Create a lower-third graphic with the QR + the words “Listen in your language” so it can be dropped in at any moment without disrupting the broadcast.
• Calendar invite copy. For broadcasts that pull from a registered audience (LinkedIn events, scheduled YouTube premieres), put the Loquira link in the event description so attendees can pre-load it on their phone before the broadcast starts.

Multistream-specific behaviour

StreamYard’s value proposition is the multistream — one broadcast, several destinations. Loquira fits this cleanly because it does not care about your destinations. The translation track exists once, accessible by a single QR code, regardless of which destination platform the viewer found the broadcast on. A LinkedIn viewer and a YouTube viewer scan the same QR and hear the same translated audio.

This is also the answer to the question “do I need a separate Loquira session per platform?” — no. One Loquira session covers all destinations because the source audio is identical across them.

Guest interviews and panels

StreamYard’s killer feature is the easy guest invite. For interviews where the guest speaks a different language than the host, the per-speaker pattern from other meeting setups applies: each speaker who wants their voice translated runs their own Loquira session from their own location. A host in English and a guest speaking Spanish can each run Loquira against their own microphone; viewers in the audience switch between the two sessions in the Loquira listener interface as the conversation moves between speakers.

For panels where all guests speak the same language, a single host-side Loquira session covers the whole conversation as long as the host’s device picks up the host’s voice and the speaker labels in the transcript are not critical.

Known limitations

• Browser audio routing. StreamYard is sandboxed in the browser; you cannot install a virtual audio cable or route StreamYard’s output through anything else. This is not a problem for the parallel pattern (which never touches StreamYard’s audio chain), but it does rule out the same-machine routing options described in OBS audio routing.
• Browser-source overlays. StreamYard’s branding system supports images, not arbitrary browser sources. If you want a live transcript on screen as part of the broadcast, that has to come from a different layer — Loquira’s transcript view on a separate display the camera can capture is one workaround.
• Mobile broadcasting via the StreamYard app. The StreamYard mobile app does not currently support parallel branding assets the same way the browser studio does. For mobile broadcasts, paste the Loquira join link into chat and verbally mention it during the intro instead of relying on a graphic overlay.