DEV Community

田也
田也

Posted on

Translating a video into another language: the three outputs that matter

Every "translate my video" project I have watched fail failed for the same reason: the subtitles and the dub were produced by two different pipelines, so they disagree.

Here is the smaller version of that problem, and what actually matters.

Three outputs, not one

A translated video is really three deliverables:

  1. Subtitles (SRT) — for people watching muted, and for search indexing.
  2. Dubbed audio (MP3) — for people who cannot read the original language fast enough.
  3. Subtitled video (MP4) — the thing you actually upload, with burned-in text.

Most tools give you one and let you stitch the rest. That is where inconsistency creeps in: the SRT says "Ana", the voice says "Anna", and the viewer notices in the first ten seconds.

Why one transcript matters more than model choice

The quality of a machine translation is mostly decided before translation begins — by the transcript.

If the ASR mishears a product name, every downstream artefact inherits the error. If the subtitle pipeline and the dubbing pipeline each run their own ASR, they inherit different errors.

So the practical rule: run ASR once, translate once, render three outputs from that single source. It removes an entire class of bugs, and it makes the subtitle match the voice-over word for word.

What you can fix before uploading

Machine translation does not fail randomly; it fails on predictable inputs:

  • Music over speech. If the vocal sits under a track, the transcript degrades. Cut a version with the music muted for transcription.
  • Multiple speakers without separation. Diarisation helps, but clean single-speaker clips are dramatically better.
  • Names and product terms. Anything invented will be transliterated differently each time.
  • Long silences and an intro slate. Trim them before upload; you pay per minute.

Three minutes of prep saves an hour of sorting out the output.

When to keep a human in the loop

Machine output is a strong first draft and a weak final version for:

  • jokes, puns and cultural references
  • legal or medical phrasing
  • brand names that must stay untranslated
  • on-screen text baked into the footage

The useful division of labour is: machine for the 90% that is mechanical, human for the 10% that carries meaning.

A workflow that costs minutes, not weeks

I have been using a small service called LinguaReel for this. It takes one upload — MP4, MOV, MKV, AVI, WEBM or audio-only — and returns subtitles, a dub and a subtitled video from the same transcript, in 12+ languages.

Two details that matter in practice:

  • The quote appears after upload and before payment, so you can see the per-minute cost before committing.
  • The free trial covers 60 seconds and 100 MB, needs no account, and returns subtitles — enough to judge whether the ASR handles your audio.

Full disclosure: I work on the project, so treat the recommendation accordingly. The workflow advice above is independent of which tool you pick.

The checklist I would use

  1. Is the transcript produced once, or once per output?
  2. Do the subtitle and the dub share wording?
  3. Is the price shown before the work starts?
  4. Can you test 60 seconds for free before paying?
  5. Who fixes the names — you, or nobody?

Five questions, and most of the market fails at least two of them.

What is your rule for deciding when a machine translation is good enough to publish?

Top comments (1)

Some comments may only be visible to logged-in visitors. Sign in to view all comments.