StreamTranslateA caption-generation API, a video-ingestion API and a player subtitle track are different interfaces. Confirm the contract between them. StreamTranslate’s public streaming setup is not a general Mux-compatible caption API, and its OBS Browser Source is not an embedded subtitle transport.
Separate generation, transport and rendering
The generator converts audio into text and, when requested, translates it. Transport moves that text alongside or separately from the video. Rendering turns the delivered data into something a viewer can read. Each stage has its own language, timing and failure constraints.
A working transcript in a dashboard proves only the first stage. A successful HTTP response proves that a receiver accepted a request, not that the audience saw the right words. Define an end-to-end test with a distinctive sentence and verify it in the target player, including its caption menu and saved recording where required.
Read the ingestion contract before configuring an encoder
Mux’s own-caption guide describes receiving one CEA-608 language embedded in H.264 and delivering it as WebVTT in HLS. Its configuration names the caption language and CC1 channel, and an active stream cannot have that caption configuration changed through the documented setup.
That is one provider’s contract, not a universal RTMP feature. For your destination, write down the accepted codec, caption format, channel identifier and configuration timing. Do not infer arbitrary Unicode support or multiple selectable languages simply because the surrounding video pipeline supports several audio tracks.
Build a small integration acceptance matrix
| Boundary | Check |
|---|---|
| Audio to text | Correct speaker feed and source language |
| Text to transport | Character encoding, timing and caption length |
| Transport to player | Track availability, labels and readable output |
| Reconnect | No stale, duplicated or out-of-order captions |
| Archive | Captions survive the recorded-video workflow if required |
Use short fixtures with accented characters, numbers and a deliberate pause. Keep a copy of expected text and compare results at each boundary so a player problem is not mistaken for a recognition error.
Choose a published StreamTranslate delivery route
For a creator operating OBS, the supported StreamTranslate route takes microphone or filter audio into caption processing and returns display text through a Browser Source. That overlay becomes part of the video image. The current plugin is an audio-input component, not an API that inserts native Twitch CC.
For YouTube, follow the native live-caption guide: the video and caption feed must refer to the same broadcast. Use the documented broadcast settings and selected output language. A working YouTube HTTP feed does not establish compatibility with an unrelated platform’s caption-ingestion endpoint.
Design recovery before connecting a real event
Give each test session an owner and a clear stop condition. Check what happens when video continues while caption transport fails, then when captions reconnect before video does. Expire old text rather than displaying an earlier sentence over a new speaker. Preserve ordering without letting an unbounded queue build up.
Keep keys and ingestion URLs out of screenshots and normal logs. Diagnostic records should contain request outcomes, sequence information and timings needed for troubleshooting. Test against an isolated destination first; changing an active encoder or stream configuration is not an appropriate first experiment.
Quick answers
Is a Browser Source a live-caption API?
No. It renders a web page inside a scene. Unless an additional integration exists, the output is visible video text rather than a selectable player subtitle track.
Can I point any RTMP encoder at a caption provider?
Only if the documented input, output and credential requirements match. Confirm the provider’s expected caption format and stream lifecycle before changing routing.
Does StreamTranslate provide Mux’s embedded_subtitles API?
No such public compatibility is established here. Use the documented StreamTranslate OBS or YouTube workflow, or obtain a separately confirmed developer integration.
Continue with your setup
Sources and further reading
Reviewed October 28, 2026. Follow the linked provider instructions for current availability and setup requirements.