EpisodeReel

Serial work: what each tool documents about continuity

A reference sheet made once and cropped into every segment

The page states that a full-body reference sheet is generated per character at analysis time, and that face and body crops from it are injected into every segment featuring that character. Two things are located by that sentence: when the artefact is made, and what reaches each generation. As of 2026-09-16.

When the sheet is made and where it goesThe sheet is produced while the script is read, before any shot exists, and crops from it travel into every segment that uses the character.Script analysedA full-body sheet is producedper character, before anygeneration.a sheetSegment builtFace and body crops from thesheet are injected into therequest.cropsShot returnedA shot that did not receivethem is identifiableafterwards.Why the ordering mattersA sheet made at analysis time settles the cast where it is cheapest to argue about, ratherthan in the middle of a queue of generations.
Fig. 1 A segment produced without the crops differs from its neighbours in a way somebody can find later.
SceneMixer 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 sentenceA full-body sheet per character, made while the script is analysedA mechanism with a stated moment
What it namesThe sheet, and the face and body crops taken from itAn artefact a production can look at, version and replace
What it leaves outHow near the ninth episode's face lands to the firstUnanswerable from any page; it needs a production run

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.

1Injection per segment leaves a trail

If crops travel with every segment that uses a character, a segment produced without them differs from its neighbours in a way somebody can find later. Drift stops being a mood and becomes a question with a checkable answer: did this shot get the crops or not.

Systems that resolve a character internally offer no such trail. They are less work per shot and they give a production nothing to examine on the morning a lead arrives looking like a relative of herself.

2Making the artefact at analysis time fixes an order of work

A sheet produced while the script is read exists before any shot does, so the cast is settled at the point where it is cheapest to argue about. A sheet produced on demand during shooting would put the same decision in the middle of a queue of generations.

That ordering is a scheduling fact rather than a picture-quality one, and it is the sort of thing a feature list never carries because it is not a feature.

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 SceneMixer 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
    A full-body reference sheet is generated per character at analysis time, and its face and body crops are injected into every segment featuring that charactera stated mechanismSceneMixer, how-to guide / recorded 2026-09-12
  • Cross-episode cast
    Character consistency is attributed to the underlying video model rather than to the productattributed to a modelMedeo, short drama page / recorded 2026-09-16

5Sources

Read from the published how-to guide at scenemixer.com, checked 2026-09-12. The whole column is on cross-episode cast and this vendor on every column is on SceneMixer; where the line falls between documented, claimed and absent is under how read. This vendor's other readings: the split into episodes, the assembly step, the shape of the deliverable. Other readings of the same column: Vidu, Google Flow.