Sentioscope

Speech and voice controls, as each vendor documents them

Why API documentation answers the wrong questions

Most of the silence in this register is not evasion. API references are written for a developer calling an endpoint and describe parameters and return values; the fields this site keeps are about behaviour across a series, which those documents have no reason to cover. As of 2026-09-12.

Who each kind of vendor document was written forMost of the silence in this register is not evasion. An API reference is written for a developer calling an endpoint and describes parameters and return values. The fields kept here are about behaviour across a series, which such a document has no reason to cover. The most useful statement in the register came from a document about risk instead.An API referenceWhat this register asksWritten forA developer calling an endpointA production planning a seasonDescribesParameters and return valuesBehaviour across many shotsAnswersWhat one call acceptsWhether the same voice returns laterThe most useful sentence here came from a document about risk
Fig. 1 The audience explains most of the empty cells. Asking a parameter reference about episode forty is asking the wrong document.
The kinds of document these fields were read from, and what each kind is written to do. Recorded 2026-09-12.
ModelWhat is documentedDetail
API referenceParameters and returnsVeo, Vidu, D-ID
Product pageFeatures and plansMost entries
Prompting guideHow to write the requestSora 2, the dialogue block
Model cardInputs, arguments and a licenceWan2.2-S2V, open weights
Compliance guideBoundaries and obligationsThe one preset-library statement

Inclusion rule. Document types actually read for this register. Marketing announcements and launch posts are not read, because a capability shown once is not a documented behaviour. Order. By how many entries were read from that kind of document.

1The audience explains most of the empty cells

A developer wants to know what to send and what comes back. A producer wants to know whether a character will sound the same in episode forty. The first question is answered thoroughly across this register and the second is barely addressed, and those are the same documents.

Reading the emptiness as a product deficiency would be a mistake. It is a statement about who these pages were written for, and the register says so rather than letting blanks imply inadequacy.

2The most useful statement here came from a document about risk

The clearest description of where voices come from sits in a compliance checklist. That is not where anyone would look, and it exists because a different obligation forced the vendor to write down something product documentation had not.

It suggests where the next useful statements will come from: obligations rather than marketing. Pages written to satisfy a rule tend to be specific in the way this register needs.

3What this site would read if it existed

A behaviour note: what the model does with two speakers, whether a voice persists, what happens when a supplied sample conflicts with a bound voice. None of that is exotic and none of it appears in either kind of document today.

Until it does, the register reads what exists, records what it finds, and marks the rest not documented rather than filling it from how the products appear to behave.

  • Audio source
    Audio is generated with the video rather than added afterwardsgenerated with the pictureGoogle, Veo documentation / recorded 2026-09-12
  • Audio source
    Q3 outputs speech, sound effects and music natively, on by default in the API, with a speech-only modethree tracks in one passVidu, API reference / 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
  • What the card does settle
    The card states support for 480P and 720P and licenses the weights under Apache 2.0Wan-AI, Wan2.2-S2V-14B model card / recorded 2026-09-22
  • How a spoken line is written into a prompt
    Dialogue belongs in a dialogue block below the prose description, with exchanges limited to a handful of sentencesOpenAI, Sora 2 prompting guide / recorded 2026-09-22
  • Audio source
    A script is either text of up to forty thousand characters or an audio url, with audio limited to five minutes for clips and ten for talksa script read aloud or a fileD-ID, create a talk reference / recorded 2026-09-22

4Sources

Every line is read from the vendor documentation linked on the speech controls page, checked 2026-09-12. What counts as documented is on how read. Nearby: How long a shot can be, Fifteen seconds of voice, Answers software can check.