Sentioscope

Speech and voice controls, as each vendor documents them

SceneMixer and Kling AI: names against a count of five

Two native-audio entries answering the language question at opposite grades. One sets fifteen named languages per project with Cantonese a sixteenth. The other documents five and leaves every name out. From 3 source pages, read 2026-09-12 to 2026-10-13; no maker pays to be listed.

Sixteen named against five counted, both nativeWith a large total a production can assume its market is probably covered. With five the probability runs the other way, and five is short enough that naming them would have been one line.SceneMixerKling AIThe language answerFifteen named, plus CantoneseFive, and none of them namedA voice lastingOn the character, for every lineBound to the element, and it travelsWhere the voice comes fromA preset library, or your recordingsNot documentedThe mouthPerformed in-language; redubbed on achangeNamed as a capability, no driverA different answer on every row
Fig. 1 One entry has answered the question; the other has confirmed it applies and declined to answer it.
Controls documented, model by modelFilled where the model documents that control, hollow where nothing is published about it.Controls documented, model by modelSceneMixerKling AIAudio sourceAudio source — SceneMixer: With the picture, in the language set for the projectAudio source — Kling AI: With the picture, on VIDEO 3.0Voice sourceVoice source — SceneMixer: A preset library, or the user's own recordingsVoice source — Kling AI: Nothing documented as an inputPer-character bindingPer-character binding — SceneMixer: On the characterPer-character binding — Kling AI: On the elementLanguagesLanguages — SceneMixer: A named list, set per projectLanguages — Kling AI: A count, no namesLip-syncLip-sync — SceneMixer: The new audio, when a line is redubbedLip-sync — Kling AI: Named, with nothing driving it
Fig. 2 Filled where the model documents that control, hollow where nothing is published about it.
SceneMixer and Kling AI on the five fields this register keeps, with the gap on each. Recorded 2026-09-22.
FieldSceneMixerKling AIWhere they part
Audio sourceWith the picture, in the language set for the projectWith the picture, on VIDEO 3.0Different answers
Voice sourceA preset library, or the user's own recordingsNothing documented as an inputDifferent answers
Per-character bindingOn the characterOn the elementDifferent answers
LanguagesA named list, set per projectA count, no namesDifferent answers
Lip-syncThe new audio, when a line is redubbedNamed, with nothing driving itDifferent answers

Inclusion rule. Two entries are given a page together when at least one column puts them at opposite grades of answer. Pairs that agree on every column, or that are both blank throughout, do not get a page. Order. Fixed field order, identical on every side-by-side page.

1Five unnamed is the hardest count to plan around

With a large total a production can assume its market is probably covered and check cheaply. With five the probability runs the other way, so an unnamed count of five turns a commissioning decision into a guess. Five is also short enough that naming the five would have been a single line.

The contrast with a named sixteen is therefore sharper than the numbers suggest. One entry has answered the question; the other has confirmed that the question applies and declined to answer it.

2Both keep a voice on the character, and only one says where it comes from

The one with the list matches each character to a preset from its library, with a sample to play before choosing, and uses that preset as reference audio on every shot the character speaks in. The one with the count binds a voice to an element that travels between generations.

So the two meet on persistence and part on selection. One documents a voice that can be heard before it is attached; the other documents the binding and not the source of the voice being bound.

3Both make a claim about method rather than about output

One states the line is performed in the chosen language while the shot renders, so no dubbing pass is needed, and documents a redub for a line changed afterwards. The other names lip-sync as a capability and describes no mechanism.

Neither claim can be checked from a page, and they fail differently if wrong. A line performed at render can still be redubbed; an unexplained capability cannot be reasoned about.

4Each of them on its own

The column this pair was chosen for is languages, and each entry has a page of its own on it. The full row for either, all five columns with the wording behind each cell, is on its model note.

  • Languages
    Dialogue is set per project to any of 15 languages, with Cantonese a 16th for dialogue onlya named list of 15SceneMixer, languages guide / recorded 2026-09-12
  • Lip-sync
    The vendor states there is no separate dubbing step and no lip-sync patch afterwardsstated as unnecessary rather than as a featureSceneMixer, languages guide / recorded 2026-09-12
  • Per-character binding
    A voice matched to a character from the built-in preset library is used as reference audio on every shot that character speaks ina matched preset kept on the characterSceneMixer, character voices guide / recorded 2026-10-13
  • Audio source
    Native audio on VIDEO 3.0 in five languagesgenerated with the pictureKling AI, model guide / recorded 2026-09-12
  • Per-character binding
    Voices are bound to elements, so a character carries its voice between generationstied to the element systemKling AI, model guide / recorded 2026-09-12
  • Lip-sync
    Lip-sync is documentedstated without a mechanismKling AI, model guide / recorded 2026-09-12

5Sources

Every cell above is read from the documentation each vendor publishes, on the dates carried by the two model notes. The whole register on one column is on the field note; entries grouped by the shape of their answer are on the routes. Other pairs: Runway and MiniMax, HeyGen and LTX Studio.