What analysis produces
Scenes
Distinct story sequences extracted from scene headings and structural context. Each scene has a location, time of day, and a list of the characters who appear.
Shots
Subdivisions of each scene, defined by camera framing or coverage. Shots give Ozu the cinematic layer — “how is the camera looking at this.”
Beats
The atomic units — one beat per rendered frame. Each beat is tagged with its
Scene.Shot.Beat address (e.g., 1.1.3).Actor / Prop / Set nodes
Every named character, object, and location gets its own node on the Flow canvas — auto-spawned, ready to generate.
The results view
Once analysis completes, the Script Node switches to a tabbed results view. Five tabs, one per category, plus a stats bar across the top showing your totals — scenes, shots, beats, Actors, Sets, Props.
The Scenes tab is usually where you start — scrolling through expanded scenes lets you see the whole story at a glance.
Reading a Scene
Open a scene in the Scenes tab and you’ll see:- Scene heading —
INT. KITCHEN — MORNING, or whatever you wrote. - Shots — listed in order, each with its camera framing intent (“Wide establishing,” “Close on the coffee cup”).
- Beats — nested under each shot, each with its beat ID and a short description of what happens.
- Dialogue — any lines assigned to this scene, grouped by character.
- Tags — the Actors, Props, and Sets involved.
The QC Log
The QC Log is Ozu’s analysis checklist. If anything in your script was ambiguous or under-specified, it shows up here.Ambiguous references
A character named “the detective” who’s otherwise unnamed, or a prop called “the artifact” without a description. Ozu still creates nodes for these, but flags them for your review.
Missing details
Scenes without clear time-of-day, characters without physical descriptions, or sets without explicit locations. Ozu makes reasonable inferences and shows its work.
Orphan entities
Anything referenced in dialogue or action but never introduced — a name that appears once in passing, for example. You decide whether to add the entity or edit the reference.
Editing the results
You can adjust anything in the analysis before the pipeline moves forward.- Edit scene structure. Expand any scene and rename it, change its location, or adjust its time-of-day. You can also reorder shots within a scene.
- Add, merge, or remove beats. Open a shot and add a beat between two existing ones; downstream beat numbers renumber automatically. Merge two beats into one if they should share a frame.
- Rename or merge Actors. If Ozu created two Actor nodes for the same person (e.g., “SARAH” and “Sarah Walker”), merge them from the Actors tab. Renames propagate through every scene.
- Edit Prop and Set descriptions. Sharpen the description on any asset card. The text here becomes the seed for hero-look generation.
- Resolve QC issues. Click a flagged item in the QC Log to jump to the affected entity and fix it in context.
Creating the Asset Nodes
When the analysis looks right, tap Create Asset Nodes. Ozu spawns a node on the Flow canvas for each Actor, Prop, and Set — plus a DRB (Director Review Board) node downstream of all of them.- Actors get their own column, with wardrobe variant nodes branching off the hero.
- Props get their own column, with set-integrated props wired to their parent Set.
- Sets follow the props, aligned so set-integrated props feed into them.
- DRB sits at the far right, connected to every asset.
Shot lists
If you want a production-planning view of everything your script requires — grouped by scene, with status, priority, notes, and assignments — the Shot List Node reads from the Timeline and your script structure. It’s not the same as the Shots extracted during analysis; it’s a downstream planning layer for crews on set. See the Shot List docs for detail.Related
Writing Your Script
Formats and conventions that produce cleaner analysis results.
Ozu Consult
The optional clarifier that sharpens results before analysis runs.
Scene, Shot, Beat
The three-level hierarchy the results view is built around.
Pipeline and Nodes
What happens after you tap Create Asset Nodes.