Sentioscope

Speech and voice controls, as each vendor documents them

SceneMixer: a library exists, and persistence does not

Two voice routes are named and neither is described as attaching to anybody. A library exists, recordings are accepted, and how a selection survives from one shot to the next is not addressed anywhere public. As of 2026-09-12.

A per-project setting, and no per-character oneThis vendor keeps dialogue language at the project level, so the platform already holds settings that outlast a shot. A per-character voice would fit in the same place, and no document says that it does.Stated to persistNot addressedLanguageSet per project, fifteen namedWhether a voice follows a language changeVoice routesA preset library, or your recordingsHow a selection is storedPerformanceSpoken as the shot rendersWhether the same voice returns nextepisodeWhere it is writtenA compliance checklistAnywhere that explains the mechanismA documentation gap rather than an architectural one
Fig. 1 The sentence that fills the voice field comes from a likeness checklist, which was written to constrain rather than to explain.
SceneMixer on per-character binding, statement by statement. Read from the vendor's languages guide on 2026-09-12.
What the documentation settlesWhat it leaves to a take
Users are told to use a preset voice library or their own recordingsHow a selection from that library is recorded against a character
Voice routes are described; persistence between shots is notWhether a project holds one voice per character or one per shot
Dialogue is set per project to any of fifteen languages, with Cantonese a sixteenthWhether a chosen voice follows a project that changes language

Inclusion rule. Only statements found on the vendor page named in the caption, and only ones bearing on this one field. Nothing here is filled in from generated output. Order. In the order the statements arrive on the vendor's page.

1A per-project language setting makes the blank stranger

This vendor is unusually specific about language, and language is set at the project level rather than per call. A platform that already keeps a per-project setting has somewhere obvious to keep a per-character voice, and the documentation does not say that it does.

So the blank reads as a documentation gap rather than an architectural one. That still matters for this register, because a production choosing between tools has only the pages, and the pages are what a comparison can be built from.

2The compliance framing cuts both ways

The sentence that fills the voice field here comes from a checklist about likeness, which means it was written to constrain rather than to explain. Checklists say what may be used; they do not usually say how a choice is stored.

Read that way, the absence is unsurprising and uninformative about the product. The cell records what is published and the page says plainly which document it came from, so a reader can weigh it accordingly.

3Others whose documentation never addresses persistence

Seven more entries reach this column empty. Most of them say much less about voices overall, which is what makes this one worth reading: two routes named, and no pairing described.

  • Hedra — not documented by the vendor.
  • Luma Ray — not documented by the vendor.
  • sync-3 — not documented by the vendor.
  • Synthesia — not documented by the vendor.
  • Veo — not documented by the vendor.
  • Vidu — not documented by the vendor.
  • Wan2.2-S2V — not documented by the vendor.
  • Per-character binding
    Not documented by the vendor (as of 2026-09-12)no public descriptionSceneMixer, compliance guide / recorded 2026-09-12
  • Voice source
    The guide tells users to use a preset voice library or their own recordingstwo routes namedSceneMixer, compliance guide / recorded 2026-09-12
  • 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

4Sources

Read from the languages guide at scenemixer.com on 2026-09-12. The same column across every entry is on per-character binding; everything this vendor publishes about speech is on SceneMixer. What counts as documented is on how read.