Lore

Sub-Scene Decomposition for Complex Multi-Beat Scenes

A technique for handling complex, multi-beat scenes: break the scene into smaller sub-scenes (e.g., arrival, dialogue, exit), generate and direct each one separately using the Actor-Directing Prompting Method (Takes and Incremental Notes), then stitch the results together into the final sequence. Reduces the amount of continuity and blocking that must be held within a single generation.

Shooting Order: Dialogue-First

Concrete example from the source: an arrival/dialogue/exit scene was split into labeled sub-scenes 5A, 5B, and 5C rather than shot as one continuous generation.

The order the sub-scenes are actually generated in matters as much as the split itself. The dialogue-heavy middle beat is shot first — 'the dialogue is the heart of the scene, it decides where the car sits and what's outside every window' — because it has the least positional freedom (actors have to be arranged for the conversation to read). Once that shot's car position and surroundings are locked, the arrival (5A) and exit (5C) sub-scenes are generated to match it, using it as their position reference, rather than the other way around. Splitting addresses compounding physics/composition errors directly, not just prompt length — see Claude-Assisted Prompt Splitting.

Why Overloaded Scenes Fail

AI video models can only convincingly render so much at once. Packing a single scene with many simultaneous events — the example given: 15 explosions, an earthquake, and an emotional conversation all at once — overwhelms both the model's rendering capacity and the viewer's ability to parse the scene. The fix is one primary action plus one or two secondary actions per scene: split complex scenes into separate shots (e.g. wide, medium, close-up) and stitch them together in editing, or use multi-shot generation (Multi-Shot Generation from a Single Prompt) with a distinct prompt per sub-scene rather than one prompt trying to cover everything at once.

Why: One Primary Action Per Scene, and Matching Shot Scale

The underlying reason a complex scene needs decomposing at all: AI video models can only track so much happening at once, so any given scene should center on one primary action plus at most one or two secondary actions. When a scene has several simultaneous events — e.g. an explosion, an earthquake, and a conversation happening together — split each event into its own shot at the shot scale that fits it (wide shot for the explosion, medium shot for the earthquake, close-up for the conversation), generate each one separately (per-scene prompts in Multi-Shot Generation from a Single Prompt, or separate generations), then stitch the shots together in an editor.