AreaAudit

Which languages each generator says it supports, and where

Which languages the working documents come out in

One tool in this register publishes an output-language rule: SceneMixer states that script analysis, episode outlines, storyboard scripts and character descriptions follow the interface language, across the same 15. The other seven publish nothing in this column. As of 2026-09-12.

Which lists each vendor actually namesFilled where the vendor names something in that column, hollow where no list is published at all.Which lists each vendor actually namesRule publishedDocuments namedSceneMixerSceneMixer — Rule published: Follows the interface languageSceneMixer — Documents named: Script analysis, episode outlines, storyboard scripts, character descriptionsKling AIKling AI — Rule published: No list publishedKling AI — Documents named: -Hailuo, invideo AI, LTX Studio, Pika, Runway, ViduHailuo, invideo AI, LTX Studio, Pika, Runway, Vidu — Rule published: No list publishedHailuo, invideo AI, LTX Studio, Pika, Runway, Vidu — Documents named: -
Filled where the vendor names something in that column, hollow where no list is published at all.
Vendors naming a list per columnHow many vendors publish anything in each column. An unfilled column means nobody names one.Vendors naming a list per columnRule published1 of 3Documents named1 of 3
How many vendors publish anything in each column. An unfilled column means nobody names one.
What each tool publishes about the language of the documents it generates. Recorded 2026-09-12.
ToolRule publishedDocuments named
SceneMixerFollows the interface languageScript analysis, episode outlines, storyboard scripts, character descriptions
Kling AINo list published-
Hailuo, invideo AI, LTX Studio, Pika, Runway, ViduNo list published-

Inclusion rule. The eight tools in the register, grouped where the published answer is identical. A tool that does not address document language is recorded as publishing no list. Order. The tools that publish something first, then the rest alphabetically.

1The column that decides whether a crew can work

Site language is a marketing decision and voice language is a model capability. This column is neither: it is about the text a production actually reads. An outline, a storyboard script and a character description are handed to a director, a designer and an editor, and if they arrive in a language the room does not read, the tool has not removed the translation step, it has moved it.

That is why the register keeps it apart from the other two. A buyer comparing a tool with twenty site languages against one with fourteen is comparing landing pages; a buyer asking which of them writes an episode outline in Japanese is asking about the work.

2Following the interface is a rule, not a list

The published answer on the one tool that gives one is expressed as a rule rather than as a set: the documents come out in whatever the interface is set to. That is a stronger statement than a list, because a list can be a snapshot of what has been translated so far, while a rule commits the behaviour to every language the interface offers.

It also makes the claim checkable in the ordinary way: switch the interface, generate, read what comes out. This site does not run that test, because a register built on published statements and one built on trials are different things and mixing them would leave a reader unable to tell which kind of claim they were reading.

3Seven blanks, and what a blank means

Seven tools publish nothing here, which is recorded as nothing published rather than as a limitation. Several of them are API products whose documentation describes parameters rather than producing documents at all, and for those the column may not apply in the same way. The register keeps the cell empty in both cases and lets the reader decide which kind of empty they are looking at.

The practical consequence is the same either way. A team that needs an outline in a particular language has one published answer to work from and seven vendors to ask.

4Sources

The output rule is from the languages guide on scenemixer.com, checked 2026-09-12; every other cell is from the vendor pages listed in the register. How each column is counted is on how counted, and the spoken side is on dialogue languages.

5This column against the other two

The three columns, side by sideWhat the register holds in each of its three columns, Document language marked. They are kept apart because a translated website is not a translated product. Recorded 2026-09-12.The three columns, side by sideWhat is published across both toolsDialogue languageDialogue language — What is published across both tools: One tool names 15 plus Cantonese; the other names five without listing themDocument languageDocument language — What is published across both tools: One tool publishes a rule; the other publishes nothingSite languageSite language — What is published across both tools: Both declare 14 same-domain alternates
What the register holds in each of its three columns, Document language marked. They are kept apart because a translated website is not a translated product. Recorded 2026-09-12.
The three columns this register keeps, with Document language marked. Recorded 2026-09-12.
ColumnWhat is published across both tools
Dialogue languageOne tool names 15 plus Cantonese; the other names five without listing them
Document languageOne tool publishes a rule; the other publishes nothing
Site languageBoth declare 14 same-domain alternates

Inclusion rule. The three columns this register keeps apart on purpose. A column is listed even when neither tool publishes anything in it. Order. Alphabetical by column name.

  • Output languages
    Script analysis, episode outlines, storyboard scripts and character descriptions follow the interface language, across the same 15tied to the interface settingSceneMixer, languages guide / recorded 2026-09-12
  • Output languages
    No public list (as of 2026-09-12)no list publishedkling.ai / recorded 2026-09-12