EpisodeReel

Serial work: what each tool documents about continuity

An element that crosses productions, against a lock that ends at the project

One documentation states that elements are reusable across projects rather than only within one. The other states that appearance is locked when a character is created and held for the entire project. Both keep a character; they disagree about how far it reaches. As of 2026-09-22.

How far a stored character is allowed to reachThree possible boundaries for a reusable cast: one scene, one project, or every project in the account. Two of the three are stated on these pages and the widest one changes what a second series costs.Widest stated scopeAcross projectsStated explicitly: the same element can be picked up by a laterproduction.The whole projectStated as the span of a lock applied when the character iscreated.One scene at a timeWhat a page promises when it declines to mention a project atall.Narrowest
Fig. 1 Ordered by width, because width is the field a capability tick erases first.
Steps each tool documentsFilled where the tool publishes a mechanism for that step, hollow where it publishes nothing on it.Steps each tool documentsLTX StudioNovi AIThe stated boundaryThe stated boundary — LTX Studio: Across projects, explicitlyThe stated boundary — Novi AI: The entire projectWhen the object is fixedWhen the object is fixed — LTX Studio: Not statedWhen the object is fixed — Novi AI: At the moment the character is createdWhat a second series inheritsWhat a second series inherits — LTX Studio: The same element, if wantedWhat a second series inherits — Novi AI: Nothing the page commits to
Fig. 2 Filled where the tool publishes a mechanism for that step, hollow where it publishes nothing on it.
LTX Studio and Novi AI on the cross-episode cast, point by point. Read 2026-09-12 and 2026-09-22.
Point at issueLTX StudioNovi AI
The stated boundaryAcross projects, explicitlyThe entire project
When the object is fixedNot statedAt the moment the character is created
What a second series inheritsThe same element, if wantedNothing the page commits to

Inclusion rule. Both pages name an object and a scope. The contrast is the boundary each one draws, which is the field a capability tick erases first. Order. The wider scope first, then the narrower one.

1Scope decides whether a cast is a project asset or a company asset

A studio with three titles and a recurring lead is asking a question no feature list answers: can the same character be used again without being rebuilt. One of these pages says yes in one word; the other draws its line at the project and says nothing beyond it.

For a single series both are sufficient. The difference only becomes money at the point a second production starts, which is also the point at which changing tools is most expensive.

2A lock at creation is a different promise from a reusable object

Locking at creation says the appearance cannot move, which removes drift by removing flexibility. A reusable element says the appearance can be picked up again, which implies it persists but not that it is immutable.

Those two guarantees answer opposite worries. One reader fears the face changing; the other fears having to make it twice. Neither page addresses the other reader's fear.

3The unstated half on each side

Neither page says whether the stored thing can be edited after work has been generated from it. A shared element edited carelessly propagates into finished episodes; a locked appearance that cannot be revised means the first version ships.

Both of those are discovered in week three. The register records the scope as published and marks the revision question as open on both sides.

4The wording both sides published

  • 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

5The same column, read for a third tool

On the cross-episode cast, SceneMixer's published page puts it in one line: A full-body sheet per character, made while the script is analysed. Its reading here, A reference sheet made once and cropped into every segment, sets out what that line settles for a series and what it leaves to a production run.

6Sources

Read from the Elements documentation at ltx.io and the short-drama generator page at noviai.ai, checked 2026-09-12 and 2026-09-22 respectively. The full column is on cross-episode cast; the single readings behind this contrast are LTX Studio and Novi AI. Other contrasts filed here: Google Flow and PopShort AI, Medeo and SceneMixer, Kling AI and Arcloop.