EpisodeReel

Serial work: what each tool documents about continuity

One to seven images per call, and nothing kept between calls

The reference documents one to seven reference images per call, supplied so the model produces a consistent subject, and documents no reusable character or element held between calls. Input limits are published as well, which is how a developer's page differs from a product page. As of 2026-09-12.

Where the filing of a cast ends upWith images attached to every request the folder belongs to the caller; with a stored object it belongs to the vendor, along with whatever happens when the model is replaced.Who keeps the reference?The caller, per requestA folder and a disciplineCorrect on day one, and degrading slowly once a secondoperator joins.The vendor, onceAn object and a dependencyLess work per shot, and nothing to inspect when itslips.This reference documents the first and no version of the second
Fig. 1 Both arrangements produce a consistent subject; they differ in whose discipline is required.
Vidu 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 sentenceOne to seven reference images per call, for a consistent subjectDocumented in a developer reference
What it namesThe request, the images and the stated input limitsEverything the caller controls, and nothing it does not
What it leaves outAny object surviving the callRecorded as not documented, which is what the page supports

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.

1The cast lives in the caller's filing system

Sending the same images on every request will produce a subject that looks the same, so the continuity is real. What holds it is a folder on the caller's side, along with whatever discipline keeps that folder correct across forty episodes and more than one person.

That is a legitimate arrangement and a common one. It is also the opposite trade from a stored cast, where the vendor owns the artefact and also owns what happens to it when the underlying model is replaced.

2Published input limits are a different kind of generosity

A minimum pixel size and an allowed aspect-ratio range are the sort of numbers a product page never carries and an integration cannot proceed without. They also make this the one reading in the column where a reader can tell in advance whether their existing stills qualify.

The limits say nothing about continuity, and that is the point of recording them separately. Precision in one place is not evidence about another.

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 Vidu 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
    One to seven reference images per call, used so the model generates a video with consistent subjectsper call rather than per characterVidu, reference-to-video API reference / recorded 2026-09-12
  • Cross-episode cast
    No reusable character or element stored between calls is documentedwhat the documentation does not describeVidu, reference-to-video API reference / recorded 2026-09-12
  • Stated limits on the inputs and the output
    Reference images must be at least 128x128, with an aspect ratio inside 1:4 to 4:1; durations run 1 to 16 seconds depending on modelVidu, reference-to-video API reference / recorded 2026-09-12

5Sources

Read from the reference-to-video API reference at platform.vidu.com, checked 2026-09-12. The whole column is on cross-episode cast and this vendor on every column is on Vidu; where the line falls between documented, claimed and absent is under how read. Other readings of the same column: PopShort AI, Showrunner Studio.