Live broadcast captions: routing a clean feed into OBS, vMix and production switchers

A production caption workflow is not a screen capture of the operator console. It separates caption content, visual treatment and the program signal so operators retain control while the audience receives a clean, stable layer.

SHORT ANSWER

Send a clean feed from the mixing desk or conference platform into recognition and translation, allow the operator to monitor and correct important text, then publish a control-free caption view. Production adds that view as a browser, window or converted transparent source. Venue, broadcast and audience outputs can share content while using separate layouts.

The production route

A practical route is “mixing-desk AUX or program audio → transcription and translation → operator correction → clean caption feed → OBS, vMix or switcher → streaming platform”. The workstation carries controls and status; the clean output carries captions only.

Product launch stage and live production environment
Field record: a launch workflow coordinates program audio, stage graphics, caption safe areas and production switching.

What makes a feed production-ready

  • No controls, room status or diagnostic text
  • Transparent or consistent key background
  • Independent source and translation styling
  • Stable dimensions while captions update
  • Configurable typography, line count and safe area
  • Separate scaling and cropping at production

One text stream, several layouts

EndpointMain constraintDesign priority
Venue LEDViewing distance and unusual canvasLarge type, contrast and fewer lines
16:9 streamFaces, logos and lower thirdsSafe-area coordination
Vertical streamNarrow width and platform controlsShort lines and bottom clearance
Audience browserDifferent devices and languagesReadable history and independent controls

Rehearsal checklist

  1. Confirm whether the feed is microphone-only or program mix.
  2. Check music, echo and level before recognition.
  3. Validate transparent edges and browser refresh.
  4. Test every program resolution and safe area.
  5. Confirm captions survive scene changes.
  6. View the encoded stream on a real phone.
  7. Test restart, network loss and reconnection.
  8. Assign primary and backup devices and operators.

Latency is an end-to-end property

Audio buffering, recognition, segmentation, translation, network transport and platform encoding all contribute. The objective is not an abstract zero-latency claim; it is a useful balance of semantic completeness, readability and response for the event. Clear audio and prepared terminology matter more as speech becomes faster or more specialist.

Frequently asked questions

Can OBS and a hardware switcher share one caption source?

They can share content, but source type, resolution and transparency treatment may differ and must be tested independently.

Should the venue screen and stream use the same layout?

Usually no. They have different viewing distances, canvases and safe areas.

RELATED READING

Build the complete live workflow

Live event caption planningAudience QR captions and AI voiceTerminology preparationDiscuss production captions

Editorial note: Integration depends on the production system, browser-source support, resolution and project network. Rehearse with the actual equipment.