Sentioscope

Speech and voice controls, as each vendor documents them

Entries claiming languages without naming or counting

Two entries claim breadth and produce no figure: a language field on every voice record, and an optional language field with no values. Neither can be checked, and neither can be wrong. From 2 source pages, read 2026-09-22 to 2026-10-25; no maker pays to be listed.

A claim that no experience can contradictNo market is named, so none can be missing, and the claim survives any amount of contrary experience. It sits one grade above silence only because it tells a reader the capability is intended.Most useful to a decisionA named listCheckable against the markets a series is committed to.A totalComparable, and silent about which markets are inside it.A claimWhere this route sits: unfalsifiable, and better than nothing.SilenceThe commonest answer in the column, and the only weaker one.Least useful
Fig. 1 A feature table with a checkmark here for both would be describing a market that does not exist.
Two unnamed language claims, beside the voice route each vendor documents. Recorded 2026-09-22.
ModelThe claim as publishedAnd where a voice comes from
D-IDA language field, no listA voice id, or a recording by url
PixVerseA language field, no listA sample, or a built-in voice

Inclusion rule. Entries whose documentation asserts spoken-language support, or carries a language field, without naming any language or giving a number. Entries with a published total are on a separate route page. Order. Alphabetical by model name.

1An unfalsifiable claim is still worth recording

Neither of these two can be tested against a page. No market is named, so none can be missing, and the claim survives any amount of contrary experience. It sits one grade above silence only because it tells a reader the capability is intended.

Recording it as a claim rather than promoting it to coverage is the whole point of keeping wording instead of ticks. A feature table with a checkmark in this column for both would be describing a market that does not exist.

2One of the two has somewhere the answer could live

One delegates its voices to five named speech providers, so the enumeration belongs to them and is genuinely published, one level down.

That is defensible engineering and poor commissioning. A decision about which markets a series can reach is usually taken by somebody who will never audit five upstream catalogues.

3The other keeps the answer in a response

The other entry gives every voice in its speaker list a languages field, so the values exist and anyone calling the endpoint can read them. The page this register is allowed to quote names none, which makes the answer real and out of reach at the same time.

It is a useful reminder that a blank is not always laziness. A vendor can put the inventory in a response and never print it on a reference page, and the register records what the page says rather than what a call might return.

4The entries on this route, one page each

Each of these links to that entry on the field this route groups by. The wording behind every cell, and the date it was read, sits on the page it links to.

  • D-ID — a language field, no list.
  • PixVerse — a language field, no list.
  • Languages
    Each voice in the speaker list carries a languages field and an accent field, and no language is named on the pagea field on each voice, no list or countPixVerse, Get TTS Speaker List reference / recorded 2026-10-25
  • Voice source
    Five speech providers are named for the voice: Microsoft, ElevenLabs, Amazon, Google and Azure OpenAIoutside catalogues named on the pageD-ID, create a talk reference / recorded 2026-09-22
  • Per-character binding
    The voice is a voice id selected from the list of available voices, with an optional language field beside ita voice id on every requestD-ID, create a talk reference / recorded 2026-09-22
  • Voice source
    The speaker list returns the built-in voices and the account's custom voices, and can be filtered to either kindcatalogue or supplied samplePixVerse, Get TTS Speaker List reference / recorded 2026-10-25

5Speech, generated with the picture

For the speech side of “Breadth claimed”, SceneMixer's guides describe how lines are spoken:

The samples page for 15 languages lists one finished series per language, each with the cast speaking that language natively and every segment's storyboard shown next to its video.

SceneMixer, AI Short Drama in 15 Languages (2026): Interface, Scripts and the Dialogue Your Cast Actually Speaks — “Can I watch a sample in my language before I start?” (read 2026-10-13)

A line lives inside the shot where it is spoken, in four parts: the speaker chip, the delivery note in round brackets, the words after the colon, and the voice chip after the words.

SceneMixer, Dialogue in the Storyboard: How to Write a Line, and What Save Tidies Up (read 2026-10-13)

6Sources

Membership of this route is decided by the wording in the field it groups by, read from the documentation each vendor publishes. The column itself is on the field note, all five columns are on the speech table, and what counts as documented is on how read. Other routes: A figure in writing, A named driver.