AreaAudit

Which languages each generator says it supports, and where

Why dialogue language gets its own column

The dialogue-language column records what a tool publishes about the language spoken in the finished shot. It is the column a drama production buys on, and the one vendors fill last: of the tools carried here, one names a list of spoken languages and one publishes a count with no names attached. As of 2026-09-12.

Three settings meeting in one render, with no dubbing passThe written line, the dialogue language chosen for the project and the voice that speaks it are held in three different places and arrive together at the moment the shot is generated. One vendor in the register states that the performance happens there, with no separate dubbing step afterwards.The written lineStoryboard script, in thedocument languageThe words to be spokenReadable and editable inthe projectThe dialoguelanguageA per-project setting, changedby the userWhich language it isperformed inRecorded on the projectThe voiceThe vendor's own inventory ofvoicesWho speaks the lineHeard in the finishedshotOne render, no separate dubbing passWhat a buyer can inspect afterwards
Fig. 1 Where the language is applied decides which failures are possible, which is why the register records the arrangement and not only the count.
How the register treats each kind of dialogue-language claim, and what a reader can do with it. Recorded 2026-09-12.
Kind of claimHow it is recordedWhat a buyer can do with it
A named list of spoken languagesRecorded language by language, with the page it was read onCheck one market against the list before paying for anything
A count with no namesRecorded as a count, with the missing list noted beside itLearn that the capability exists, without learning whether it reaches one market
A language offered for dialogue but not the interfaceRecorded in this column only, and flagged as a splitRead it as a decision about viewers rather than about operators
No statement about spoken outputRecorded as no list publishedNothing, which is the finding

Inclusion rule. Claim shapes this column accepts. A language heard in a demo reel is not a claim and does not appear, because a reader cannot repeat that check from a vendor page. Order. Most specific claim first, silence last.

1A spoken language is a different promise from a written one

Writing a line in Korean and performing it in Korean are separate capabilities that happen to be sold under one heading. A generator can produce a storyboard script in a language it has no voice for, and it can speak a language it will not write a breakdown in. Both combinations are in the register today.

Keeping them in one cell would hide the case a series actually fails on: documents a crew can read, dialogue an audience cannot understand, or the reverse. The two columns are printed side by side so the mismatch is visible instead of averaged away.

2Where the language is applied changes what can go wrong

One vendor in the register states that the model performs the line in the chosen language while the shot is being rendered, with no separate dubbing pass and no lip-sync repair afterwards. That is a claim about architecture, not about coverage, and it is recorded because it changes which failures are possible.

A pipeline that dubs after picture lock can lose sync when a translated line runs long. A pipeline that speaks at generation time cannot lose sync that way, but a language it performs badly cannot be repaired without regenerating the shot. Neither arrangement is better in the abstract; a buyer needs to know which one is being sold.

3A count is the hardest entry to use

The register carries one dialogue claim that is a count with no names: a number of languages with native audio, published without saying which ones. The count goes in because it is a published fact, and the missing list is recorded beside it because a number cannot be checked against a market.

A team in Jakarta cannot tell from that figure whether Indonesian is among them, and that is the only question they have. Rounding the count up into a list would invent names; dropping it would discard something the vendor did publish. Printing both the number and the gap is the honest reading, and the gap is the part worth quoting.

4Where this column sits in the register

Columns, and who names a list in eachDialogue language is the column this page is about, and the one a production buys on. Counted from named lists only. Recorded 2026-09-12.Columns, and who names a list in eachTools naming a listTools naming alistDialogue languageDialogue language — Tools naming a list: 1 of 2 toolsDocument languageDocument language — Tools naming a list: 1 of 2 toolsSite languageSite language — Tools naming a list: 2 of 2 tools
Fig. 2 Dialogue language is the column this page is about, and the one a production buys on. Counted from named lists only. Recorded 2026-09-12.
The three columns the register keeps, and how many of the two fully read tools name a list in each. Recorded 2026-09-12.
ColumnTools naming a list
Dialogue language1 of 2 tools
Document language1 of 2 tools
Site language2 of 2 tools

Inclusion rule. The three columns this register keeps apart. A column stays listed even where neither tool names a list, because an empty column is a finding about disclosure. Order. Alphabetical by column name.

  • Voice languages
    Spoken dialogue is set per project to any of the 15, with Cantonese a 16th option for dialogue onlyset per projectSceneMixer, languages guide / recorded 2026-09-12
  • 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
  • Voice languages
    Native audio on VIDEO 3.0 in five languages, with voices bound to elementscount published without a listKling AI, model guide / recorded 2026-09-12

5Sources

Every entry in this column is read from the vendor page named beside it and carries the day it was read; the current state of all three columns is in the register, and the rule that lets a claim into a cell is on how counted. The other columns: Site language, Document language. All three: the columns of the register.