Sentioscope

Speech and voice controls, as each vendor documents them

LTX Studio: voices attached to character Elements

Voices are attached to character Elements, which puts them alongside the appearance a production already defines once. Nothing is re-specified per shot, so there is no per-call step to forget and no place for a mismatch to enter. As of 2026-09-12.

A face, a costume, a way of moving, and a voiceA character in a generated series is a bundle of continuity obligations. Systems that keep some of them in one object and the rest on the request produce the failure where a character looks right and sounds wrong.What one Element holdsAppearanceDefined once on the Element and drawn on for every shot.VoiceAttached to the same Element, so it needs no per-shotspecification.Audio to videoA second documented route, with no stated precedence over thefirst.And the conflict the page does not resolve
Fig. 1 There is one authoritative copy rather than forty transcribed ones, which is why this shape survives a long shoot.
LTX Studio on per-character binding, statement by statement. Read from the vendor's product page on 2026-09-12.
What the documentation settlesWhat it leaves to a take
Voices are attached to character ElementsWhere a voice comes from before it is attached to one
Joint audio and video generation is documented on LTX-2.5Whether the joint route always uses the attached voice
An audio-to-video route runs in the other directionWhether that route overrides an Element's voice

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.

1Appearance and voice in one object is the right shape

A character in a generated series is a bundle of continuity obligations: a face, a costume, a way of moving and a voice. Systems that keep some of those in one place and the rest on the request produce the failure where a character looks right and sounds wrong.

Putting the voice on the same Element as the appearance means a production defines a cast once and draws on it. That survives a long shoot for the same reason a call sheet does: there is one authoritative copy rather than forty transcribed ones.

2Two routes and no stated precedence

The same product documents an audio-to-video route where an existing track drives the generation. If a track is supplied for a shot featuring a character with an attached voice, something has to win, and the page does not say which.

Recorded as a documented arrangement with an undocumented conflict. A production relying on either behaviour should establish it by test and keep the result beside the shot list, because it is not a promise.

3The others where a voice exists before any shot does

Three more entries let a voice outlast a call. One other attaches it to the character; two keep a voice object that has to be named on each request.

  • Per-character binding
    Voices are attached to character Elementstied to the element systemLTX Studio / recorded 2026-09-12
  • Audio source
    Joint audio and video generation, plus audio-to-video, on LTX-2.5two directionsLTX Studio / recorded 2026-09-12

4Sources

Read from the product page at ltx.io on 2026-09-12. The same column across every entry is on per-character binding; everything this vendor publishes about speech is on LTX Studio. What counts as documented is on how read.