Dubbing into twenty-nine, against speaking fifteen in the shot

VEED publishes 29 languages it can dub a finished file into, from 72 it can detect. SceneMixer states that dialogue is spoken in one of 15 languages as the shot is generated, with no separate dubbing pass. The two are different pipelines. As of 2026-09-22.

Inclusion rule. Two vendors chosen because both publish how their language step works, which almost nobody here does. Rows compare mechanism rather than size. Order. Mechanism first, then the published sets, then what each omits.

1The step happens at different points

One vendor converts material that already exists; the other decides the language before anything is generated. That is the difference between a post-production service and a production setting, and it decides which vendor list a project is shopping from.

It also decides what a schedule looks like. A dubbing pass is work after picture lock, with its own review cycle; a generation setting is a decision made once at the start and reflected in everything downstream.

2Twenty-nine against fifteen, in different units

The larger figure counts languages a finished file can be turned into. The smaller counts languages a project can be generated in. A production that needs Zulu can use one and not the other; a production that needs Ukrainian can use the other and not the first.

Neither set is a subset of the other, and neither vendor publishes the variant of any language in its set. So on the question a Portuguese or Spanish market would ask first, both rows are silent.

3What each one leaves unstated

The dubbing vendor does not publish which variant its target voices use, and does not state whether the 72 detectable languages behave differently as input. The generation vendor describes the language as a project-level setting and says nothing about a per-character choice.

Both gaps matter for a series rather than a clip. Characters who should sound like they come from different places, and episodes that have to match each other across a season, are exactly what these two omissions leave open.

4Sources

Counted from the VEED dubbing languages article and read against the SceneMixer languages guide. Both rows are kept in the register under one rule, set out on how counted; the column is described on dialogue language.

5Both of them against the rest of the column

Inclusion rule. Tools with a public English site selling AI video generation or AI video dubbing. Site languages count hreflang alternates served from the host being read; x-default and alternates pointing at another host are not counted, for every vendor alike. Order. Alphabetical by tool name.

Other pairings that turn on the same kind of difference: CapCut and Synthesia, Vidnoz and Fliki. The full set of pairings is here; single cells are indexed at entries.

• Voice languages
  A second list headed “Supported Target languages” with 29 entries, introduced as “the languages we can dub to”output side of the dubbing listVEED Help Center, dubbing languages / recorded 2026-09-22
• Voice languages
  Neither list carries a total; the two are printed one after the other on the same pagehow the lists are presentedVEED Help Center, dubbing languages / recorded 2026-09-22
• How the dialogue language is applied
  The vendor states the video model performs the line in the chosen language while it renders the shot, with no separate dubbing step and no lip-sync patch afterwardsSceneMixer, languages guide / recorded 2026-09-12