Captioned and dubbed streams for the platforms that only speak RTMP
Social and live-commerce destinations have no transcoder or packager to integrate with, just an RTMP(S) endpoint. SyncWords takes your stream in over RTMP(S), embeds captions or produces a dubbed feed, and hands it back ready for the platform.
- Embedded EIA-608
- A dubbed stream per language
- YouTube & Facebook presets
- Any RTMP(S) encoder
How it works
In from your encoder, out to the platform
Any RTMP(S) encoder connects, because compatibility is a property of the protocol rather than a per-vendor integration: OBS Studio, Wirecast, vMix, StreamYard, a hardware encoder, or the stream your production tool already emits.
Your stream in
Push your live stream to SyncWords over RTMP with a stream key, with TLS if you want it.
Captioned, translated, dubbed
Live ASR captions the audio; translation and AI dubbing produce each additional language from the same session.
Captions embedded, dubs as streams
EIA-608 captions are embedded in the stream itself. Because social platforms carry one audio track per stream, each dubbed language goes out as its own stream.
Out to the destination
SyncWords pushes to your RTMP(S) destination, with presets for YouTube and Facebook, or hands the stream back for you to publish.
Formats on this path
What this path carries
Embedded EIA-608
Captions embedded in the stream, rendered natively by YouTube Live, LinkedIn Live and Facebook Live with no configuration at the far end.
Dubbed audio
Live AI dubbing in real time, one output stream per language. Captions and subtitles come with every dub.
Subtitles alongside
Translated subtitles can run in parallel on a caption page your viewers open anywhere, since embedded 608 covers only the seven languages the standard supports.
Destinations
Tested destinations on this path
The big RTMP destinations render embedded 608 captions natively. For live shopping and market-by-market dubbing, each platform has its own rules about ingest and audio tracks; the FAQ below states them plainly.
Frequently asked questions
Which encoders and streaming tools work with this path?
Any RTMP(S) encoder. Compatibility is a property of the protocol, not a per-vendor integration, so OBS Studio, Wirecast, vMix, StreamYard, Restream, XSplit and hardware encoders all connect the same way. NDI is not supported.
Can one stream carry several dubbed languages?
No, and that is a platform constraint rather than a SyncWords one: social platforms carry one audio track per stream. Each dubbed language is produced as its own output stream from the same live session, and each goes to its own destination or channel.
Can you dub our Instagram Live feed?
No. Instagram Live has no official third-party RTMP ingest, so a live dubbed IG feed is not something we or anyone can honestly promise. What works instead is the localized replay: dub the recording and publish per market.
What about TikTok Live?
TikTok gates RTMP stream keys behind follower thresholds, issues per-session keys that expire in about two hours, and TikTok Shop uses a separate seller dashboard per market. Where you have RTMP access, the path works; plan the key logistics into the run of show.
Is the broadcast MPEG-TS pipeline behind this path too?
RTMP reaches the same platform, but through a different front end than the SRT path's transport-stream stack. For broadcast-grade MPEG-TS delivery with Teletext, DVB-SUB or DVB-TTML, use the SRT path; RTMP is the right tool for destinations that only accept RTMP.
Which languages can embedded captions carry on this path?
Embedded EIA-608 carries the seven languages the standard supports, including English, Spanish, French, Portuguese and Italian. For other languages and scripts, deliver subtitles on a parallel caption page, or dub the stream.
Run a captioned test stream this week
Point your encoder at us and our engineers will send a captioned or dubbed stream back to your destination in a proof of concept.