EpisodeReel

Serial work: what each tool documents about continuity

One upload read once, with the episode structure falling out of it

The guide states that one upload is analysed into characters, scenes, props and episode structure. All four arrive from the same pass, which is a different claim from a planner run over an outline, and it changes what a second upload costs in time. As of 2026-09-22.

Four things out of one reading of the sourceCharacters, scenes, props and the episode structure are described as arriving from the same analysis pass, so they agree with each other by construction.CharactersExtracted from theuploadA cast listUsed by every later stepScenesExtracted from theuploadA set listReferenced per segmentPropsExtracted from theuploadAn object listAttached where mentionedEpisode structureExtracted from theuploadA running orderAgrees with the threeothersOne analysis pass over one uploadWhat a second pass would have to reconcile
Fig. 1 The other side of the same design is that a revision means reading the source again.
SceneMixer on the split into episodes, in the wording the page uses. Read 2026-09-12.
PointWhat the vendor's page statesHow this file reads it
The sentenceOne upload analysed into characters, scenes, props and episodesDocumented, as a single operation
What it namesThe pass, and the four things it producesAn operation with a stated output list
What it leaves outWhat happens to generated episodes when scene six is rewrittenUnanswered here and on every other page in this column

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.

1Four outputs from one pass is an architectural statement

If the cast, the sets, the props and the running order all come out of the same read, then they agree with each other by construction: the character who appears in episode nine is the same entry that was extracted in the first place.

Products that plan episodes separately from extracting assets have to reconcile the two afterwards, and reconciliation is where a name becomes two names. Nothing on the page claims this advantage, which is why the register records the shape and not the benefit.

2A single pass raises the cost of changing your mind

The other side of the same design is that a revision means reading again. A team that expects the source to move under them wants to know whether a second pass replaces the episodes, merges with them, or leaves the old ones stranded.

No page in this column answers that, which makes it the most useful question to ask in a sales conversation and the one least likely to be volunteered.

3Where this sits in the column

What the vendor publishes on the split, entry by entryEvery entry on the split column, with this one marked.What the vendor publishes on the split, entry by entryWhat the vendor publishes on the splitAI Drama Generator — What the vendor publishes on the split: The narrative stated to be structured automatically into episodes, scenes, dialogue and beatsAI Drama GeneratorAI Dramas — What the vendor publishes on the split: Nothing published on a script being split; scenes are written one at a time by the userAI DramasAnijam — What the vendor publishes on the split: Multi-episode short drama and one-to-two-minute micro drama both stated as supportedAnijamArcloop — What the vendor publishes on the split: Recurring episodes with consistent characters given as the outputArcloopcharacter.app — What the vendor publishes on the split: Story setup and connected Scenes named as stagescharacter.appCrano AI — What the vendor publishes on the split: Repeatable episode structures described as something the user buildsCrano AIDramaSo — What the vendor publishes on the split: A season of up to 60 episodes stated as plannable from one premiseDramaSoDramily — What the vendor publishes on the split: Episode scripts drafted from an idea, with a project stated to run to 120 episodesDramilyGenra — What the vendor publishes on the split: Structured episode outlines and scene breakdowns, described on the vendor's blogGenraGoogle Flow — What the vendor publishes on the split: Nothing publishedGoogle Flowinvideo AI — What the vendor publishes on the split: An agent plans a season episode by episodeinvideo AIKling AI — What the vendor publishes on the split: Nothing publishedKling AILTX Studio — What the vendor publishes on the split: Organised per production, no episode structureLTX StudioLuma Agents — What the vendor publishes on the split: Characters, story arcs and episode boards developed on the board, then a pilotLuma AgentsMedeo — What the vendor publishes on the split: Turning one story into numbered parts, recap clips and next-episode teasersMedeoNovi AI — What the vendor publishes on the split: Serialized mini-dramas stated to be creatable from scripts, novels or story outlinesNovi AIOpenArt — What the vendor publishes on the split: A director feature stated to structure a story into episodes and scenesOpenArtPexo — What the vendor publishes on the split: An open loop at the end of one cut carries the cast into the nextPexoPopShort AI — What the vendor publishes on the split: A script or novel uploaded into Drama Canvas, with characters, scenes and props extractedPopShort AISceneMixer — What the vendor publishes on the split: One upload analysed into characters, scenes, props and episodesSceneMixerShowrunner Studio — What the vendor publishes on the split: A written scene stated to return an episode, and a show shaped into a seasonShowrunner StudioStoryShort — What the vendor publishes on the split: Scene-by-scene writing and a named beat order: hook, escalation, reveal, cliffhangerStoryShortTopview — What the vendor publishes on the split: Nothing publishedTopviewTrendShort — What the vendor publishes on the split: A script, draft or outline broken into shots, beats and visual prompts, one level below episodesTrendShortVidu — What the vendor publishes on the split: Nothing publishedVidu
Fig. 2 Every entry on the split column, with this one marked.
The split into episodes column with SceneMixer marked. Rows read between 2026-09-12 and 2026-09-22.
ToolWhat the vendor publishes on the split
AI Drama GeneratorThe narrative stated to be structured automatically into episodes, scenes, dialogue and beats
AI DramasNothing published on a script being split; scenes are written one at a time by the user
AnijamMulti-episode short drama and one-to-two-minute micro drama both stated as supported
ArcloopRecurring episodes with consistent characters given as the output
character.appStory setup and connected Scenes named as stages
Crano AIRepeatable episode structures described as something the user builds
DramaSoA season of up to 60 episodes stated as plannable from one premise
DramilyEpisode scripts drafted from an idea, with a project stated to run to 120 episodes
GenraStructured episode outlines and scene breakdowns, described on the vendor's blog
Google FlowNothing published
invideo AIAn agent plans a season episode by episode
Kling AINothing published
LTX StudioOrganised per production, no episode structure
Luma AgentsCharacters, story arcs and episode boards developed on the board, then a pilot
MedeoTurning one story into numbered parts, recap clips and next-episode teasers
Novi AISerialized mini-dramas stated to be creatable from scripts, novels or story outlines
OpenArtA director feature stated to structure a story into episodes and scenes
PexoAn open loop at the end of one cut carries the cast into the next
PopShort AIA script or novel uploaded into Drama Canvas, with characters, scenes and props extracted
SceneMixerOne upload analysed into characters, scenes, props and episodes
Showrunner StudioA written scene stated to return an episode, and a show shaped into a season
StoryShortScene-by-scene writing and a named beat order: hook, escalation, reveal, cliffhanger
TopviewNothing published
TrendShortA script, draft or outline broken into shots, beats and visual prompts, one level below episodes
ViduNothing published

Inclusion rule. Every entry on this file appears below. A vendor stating that work is organised some other way is recorded as publishing something; silence is recorded as silence. Order. Alphabetical by tool name.

4The wording itself

  • Script to episodes
    One upload is analysed into characters, scenes, props and episode structurein one passSceneMixer, how-to guide / recorded 2026-09-12
  • Script to episodes
    A script or novel uploaded into Drama Canvas is stated to have characters, scenes and props extracted from it automaticallyextraction from an uploadPopShort AI, home page / recorded 2026-09-22

5Sources

Read from the published how-to guide at scenemixer.com, checked 2026-09-12. The whole column is on script to episodes 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 cross-episode cast, the assembly step, the shape of the deliverable. Other readings of the same column: Luma Agents, invideo AI.