Which column of this register is emptiest
The document-language column holds one filled cell out of eighteen. The voice column holds nine, five of them named sets. The site column holds eleven, of which two are a single code left standing by the counting rule. As of 2026-09-12.
| Tool | What is published | Detail |
|---|---|---|
| SceneMixer | A rule: generated documents follow the interface language | The only filled cell in that column |
| Synthesia | No list published | Publishes 143 named voice rows |
| HeyGen | No list published | Publishes two named voice lists |
| VEED | No list published | Publishes both sides of a dubbing list |
Inclusion rule. The one vendor filling the document column, plus the three vendors with the fullest voice disclosure in the register. The other fourteen rows are also empty. Order. The filled cell first, then the three vendors by size of voice disclosure.
1Every long voice list sits beside an empty document cell
The vendors that document their spoken output most carefully document the language of their generated documents not at all. One names a hundred and forty-three languages for translation and says nothing about the language of a script.
That is consistent with what those products do: they convert finished material rather than generating production documents. It also means a studio cannot find out, before paying, whether the paperwork will arrive in a language its crew reads.
2A column with one entry is still worth keeping
The alternative would be folding it into the voice column, which would delete the finding. An almost empty column says something about an industry that a merged column would hide entirely.
It also gives a reader somewhere to put a claim when a second vendor makes one. A question with no column has nowhere to be recorded, and it tends to be answered by inference instead.
3The one filled cell is a rule rather than a list
It states that generated documents follow the interface language, which is shorter than a list, checkable by anyone who can change the setting, and cannot drift out of step with the interface column.
If a second vendor published a list instead, the two would not be directly comparable. That is worth saying before it happens, because a column with two entries in different shapes invites exactly the kind of merge this register avoids.
4The three columns behind this question
| Column | How many of the 18 tools name a list |
|---|---|
| Dialogue language | 5 of 18 tools |
| Document language | 1 of 18 tools |
| Site language | 9 of 18 tools |
Inclusion rule. The three columns this register keeps. A column stays listed even when no vendor names a list, because silence in a column is itself recorded. Order. Alphabetical by column name.
- Output languagesScript analysis, episode outlines, storyboard scripts and character descriptions follow the interface language, across the same 15tied to the interface setting
- Output languagesNo public list (as of 2026-09-12)no list published
- Output languagesNo public list (as of 2026-09-12)no list published
- Output languagesNo public list (as of 2026-09-12)no list published
- Voice languagesNo public list (as of 2026-09-12)no list published
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: Widest and narrowest, Subtitles are not voices.