Sentioscope

Speech and voice controls, as each vendor documents them

Voice catalogue: an inventory you can choose from

A voice catalogue is an inventory the platform supplies. Five entries have one. Only one publishes it with enough structure to filter before committing, and the rest assert it or hide it behind an endpoint. As of 2026-09-12.

Published, hidden behind an endpoint, or merely assertedA catalogue published per voice with a code and an id can be filtered before anything is signed. One retrieved at runtime is current and unreadable. One asserted in a sentence is neither.Most useful before a commitmentPublished per voiceA language code, a gender and an id, so it can be filtered andaudited.Behind an endpointAlways current, and unreadable by anyone evaluating theplatform.Delegated by nameFive outside providers, each with its own list and its ownterms.Asserted in proseA library exists; no count, no languages, nothing to shortlist.Least useful
Fig. 1 The same design can be strong for an engineer and useless for the person deciding whether a series can be cast.
Voice catalogue, as published. Recorded 2026-09-12.
ModelHow the catalogue is publishedWhat a production can do with it
D-IDDelegated to five named providersAudit five upstream lists
HedraBehind a voices endpointEnumerate it in code
PixVerseBuilt-in voices, named as a categoryNothing before a call
SceneMixerA preset library, named in a checklistNothing before a call
SynthesiaPer voice, with a language code and an idShortlist by market and gender

Inclusion rule. Entries whose documentation says a production may choose a voice the vendor supplies. An entry that only accepts a recording does not earn a row. Order. Alphabetical by model name.

1A list is not the same as a browsable inventory

Four of these five assert a catalogue and one publishes it. The published one carries a formal and native language name, a code, a gender, a name and an id per voice, which is enough to filter automatically and enough to audit later.

The others hand the enumeration to an endpoint or to somebody else's documentation. Both are reasonable engineering and neither helps a producer deciding whether a series can be cast at all.

2A catalogue behind an endpoint is current and unreadable

An inventory retrieved at runtime cannot go stale against the code, which is the argument for it. It also cannot be read by anybody evaluating the platform, because evaluation happens before there is any code.

So the same design is strong for the engineer and useless for the commissioner. This register records the documentation because that is what the second reader has.

3Delegation is more candid than a vague claim

Naming five outside speech providers tells a reader exactly where the real catalogue lives, which is better documentation than a sentence asserting broad support. It also imports five sets of licence terms and deprecation schedules.

Recording the provider alongside the voice id in a production's own notes is the cheap defence. The returned file does not say which service spoke, and a year later that is the one thing needed to reproduce a character.

4Sources read for this entry

This page defines the term and logs what each vendor documents about it, each figure read on 2026-09-12. Related: Language code, Guide track.