Speaking the line versus dubbing it afterwards
One published sentence in this register places the language decision inside the render: the spoken line arrives with the shot rather than after it, which leaves no dubbing pass and no lip-sync repair in the described pipeline. As of 2026-09-12.
| Tool | What is published | Detail |
|---|---|---|
| Generated in-language | Stated by one vendor | No dubbing pass described |
| Dubbed after render | Not described by anyone here | Would imply a separate track |
| Not addressed | Every other tool | No statement about method |
Inclusion rule. Statements about method, taken from vendor pages. This register records where the language decision sits in the pipeline and does not assess how the result sounds. Order. Methods that a vendor describes first.
1This is a scheduling fact before it is a quality claim
A production that plans a dubbing pass is planning a different pipeline from one that does not: different vendors, different timeline, different budget line. Where the language decision is made determines which of those a team is in, and that is decidable from a published sentence without anyone listening to output.
Whether a native speaker finds the result convincing is not decidable that way, and this register does not attempt it. The two questions get confused constantly because they are answered by the same sentence in most marketing copy.
2The written and the spoken sides are separate settings
The same vendor describes working documents following the interface language across 15, and dialogue set per project. Those can differ: a crew reading Japanese outlines can be making a series whose characters speak Korean, and the product treats that as two settings rather than one.
No other tool here publishes enough to say whether it makes the same distinction. The register keeps the columns apart so that the distinction stays visible where it is published.
3What would change this row
Another vendor describing where its language decision is applied, in either direction. A documented dubbing pass would be just as informative as an in-language claim, and would give this page a second row with real content in it.
Until then it is one sentence from one vendor, recorded with its source and its date, and explicitly not generalised into a statement about how this category works.
4The three columns behind this question
| Column | How many of the two tools publish a list |
|---|---|
| Dialogue language | 1 of 2 tools |
| Document language | 1 of 2 tools |
| Site language | 2 of 2 tools |
Inclusion rule. The three columns this register keeps. A column stays listed even when neither tool names a list, because silence in a column is itself recorded. Order. Alphabetical by column name.
- How the dialogue language is appliedThe 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 afterwards
- Output languagesScript analysis, episode outlines, storyboard scripts and character descriptions follow the interface language, across the same 15tied to the interface setting
5Sources
Counts and lists are read from the vendor pages named in the register, checked 2026-09-12. The counting rule is on how counted. Nearby: How counted, Site vs product.