EpisodeReel

Serial work: what each tool documents about continuity

An element that outlives the production it was made in

The documentation states that elements are reusable across projects rather than only within one. That single word, across, is the whole content of this reading: it decides whether a second series with the same lead starts from a stored character or from a rebuild. As of 2026-09-22.

What a second production starts fromAn element scoped wider than a project means the next title picks the same character up. Scoped to a project it means the next title rebuilds it.Does the object cross the project boundary?Yes, across projectsA company assetCheaper and more consistent, and one careless editreaches signed-off work.No, inside oneA project assetCleanly isolated, and the second series pays for arebuild.Stated explicitly here, which is rare in this column
Fig. 1 The difference becomes money at the point where changing tools is most expensive.
LTX Studio on the cross-episode cast, in the wording the page uses. Read 2026-09-12.
PointWhat the vendor's page statesHow this file reads it
The sentenceElements reusable across projects, not only inside oneDocumented, with scope stated explicitly
What it namesThe element, and the boundary it is allowed to crossA stored object with a published scope
What it leaves outWhether an element can be edited without disturbing finished workThe question a second season raises immediately

Inclusion rule. Three points per reading: the sentence as the vendor published it, the thing that sentence names, and what it declines to settle. Nothing here is inferred from an interface or a demo. Order. From the published sentence, to what it names, to what it leaves open.

1Scope is the field a feature comparison flattens first

Two products can both offer a reusable character and mean different things by reusable. One means inside this production; the other means anywhere in this account. A tick in a column erases the difference, and the difference is what a studio with three titles cares about.

Recorded here as published, the scope also implies an obligation: something reusable everywhere has to keep working when the production it was born in is archived.

2A shared object is an asset and a liability at once

A lead held once and used by every title is cheaper and more consistent. It is also a single point of failure: one careless edit propagates into work that was already signed off, and nothing published says whether that is possible.

Teams that have run a shared asset library before will recognise the trade. The register notes it without scoring it, because the page does not address it either way.

3Where this sits in the column

What the vendor publishes on the cast, entry by entryEvery entry on the cast column, with this one marked.What the vendor publishes on the cast, entry by entryWhat the vendor publishes on the castAI Drama Generator — What the vendor publishes on the cast: Consistent characters listed among the outputs, with no mechanism namedAI Drama GeneratorAI Dramas — What the vendor publishes on the cast: Each character saved with a name, a face and a voice style, then called by name in every scriptAI DramasAnijam — What the vendor publishes on the cast: Locking characters' faces across every episode stated as an action the tool performsAnijamArcloop — What the vendor publishes on the cast: Locking a face, outfit, personality and visual identity listed as a step, with no object namedArcloopcharacter.app — What the vendor publishes on the cast: A recurring Cast and World described as objects the series is built oncharacter.appCrano AI — What the vendor publishes on the cast: The same identity stated to hold across episodes, with stable appearance and emotional presenceCrano AIDramaSo — What the vendor publishes on the cast: Consistent characters listed among the outputs, with no mechanism namedDramaSoDramily — What the vendor publishes on the cast: Character dynamics, scenes and props turned into reusable assetsDramilyGenra — What the vendor publishes on the cast: Cast cards holding a face and a voice, stated to carry across every sceneGenraGoogle Flow — What the vendor publishes on the cast: Ingredients, the same images reused for a character and key objects from one clip to the nextGoogle Flowinvideo AI — What the vendor publishes on the cast: Project memory holds character sheets and locationsinvideo AIKling AI — What the vendor publishes on the cast: Elements carry appearance and voice between generationsKling AILTX Studio — What the vendor publishes on the cast: Elements are reusable across projectsLTX StudioLuma Agents — What the vendor publishes on the cast: Characters, products and brand elements defined once and preserved across named operationsLuma AgentsMedeo — What the vendor publishes on the cast: Consistency attributed to the video model the product runs onMedeoNovi AI — What the vendor publishes on the cast: A character created in the product, whose appearance the system locks for the whole projectNovi AIOpenArt — What the vendor publishes on the cast: Leads stated to stay the same across every episode, face, wardrobe and chemistryOpenArtPexo — What the vendor publishes on the cast: Hyperframe, named as what locks a face, wardrobe and voice across every episodePexoPopShort AI — What the vendor publishes on the cast: Characters, scenes and props stored as reusable production assets, from Episode 1 to Episode 50PopShort AISceneMixer — What the vendor publishes on the cast: Reference sheet per character, crops injected into every segmentSceneMixerShowrunner Studio — What the vendor publishes on the cast: Sets, characters and canon stated to persist across the whole seriesShowrunner StudioStoryShort — What the vendor publishes on the cast: Casting consistent characters listed as a step, with no mechanism namedStoryShortTopview — What the vendor publishes on the cast: Characters and scenes stated to be built before video generation, to help continuityTopviewTrendShort — What the vendor publishes on the cast: Locking identity, wardrobe, face and emotional range listed as a stepTrendShortVidu — What the vendor publishes on the cast: One to seven reference images supplied per callVidu
Fig. 2 Every entry on the cast column, with this one marked.
The cross-episode cast column with LTX Studio marked. Rows read between 2026-09-12 and 2026-09-22.
ToolWhat the vendor publishes on the cast
AI Drama GeneratorConsistent characters listed among the outputs, with no mechanism named
AI DramasEach character saved with a name, a face and a voice style, then called by name in every script
AnijamLocking characters' faces across every episode stated as an action the tool performs
ArcloopLocking a face, outfit, personality and visual identity listed as a step, with no object named
character.appA recurring Cast and World described as objects the series is built on
Crano AIThe same identity stated to hold across episodes, with stable appearance and emotional presence
DramaSoConsistent characters listed among the outputs, with no mechanism named
DramilyCharacter dynamics, scenes and props turned into reusable assets
GenraCast cards holding a face and a voice, stated to carry across every scene
Google FlowIngredients, the same images reused for a character and key objects from one clip to the next
invideo AIProject memory holds character sheets and locations
Kling AIElements carry appearance and voice between generations
LTX StudioElements are reusable across projects
Luma AgentsCharacters, products and brand elements defined once and preserved across named operations
MedeoConsistency attributed to the video model the product runs on
Novi AIA character created in the product, whose appearance the system locks for the whole project
OpenArtLeads stated to stay the same across every episode, face, wardrobe and chemistry
PexoHyperframe, named as what locks a face, wardrobe and voice across every episode
PopShort AICharacters, scenes and props stored as reusable production assets, from Episode 1 to Episode 50
SceneMixerReference sheet per character, crops injected into every segment
Showrunner StudioSets, characters and canon stated to persist across the whole series
StoryShortCasting consistent characters listed as a step, with no mechanism named
TopviewCharacters and scenes stated to be built before video generation, to help continuity
TrendShortLocking identity, wardrobe, face and emotional range listed as a step
ViduOne to seven reference images supplied per call

Inclusion rule. Every entry on this file appears in the column below, including the ones whose vendor says nothing on this step. The marked row is the entry this page is about. Order. Alphabetical by tool name.

4The wording itself

  • Cross-episode cast
    Elements are reusable across projects rather than only within oneacross productionsLTX Studio, Elements / recorded 2026-09-12
  • Cross-episode cast
    The page states that when a character is created the system locks their appearance, and that consistency is maintained across the entire projectlocked at creationNovi AI, drama generator page / recorded 2026-09-22

5Sources

Read from the Elements documentation at ltx.io, checked 2026-09-12. The whole column is on cross-episode cast and this vendor on every column is on LTX Studio; where the line falls between documented, claimed and absent is under how read. This vendor's other readings: the split into episodes. Other readings of the same column: Luma Agents, Dramily.