From Storyboard to Video

There is a gap between a shot on paper — "Mira turns and sees the door" — and a finished video clip. Closing that gap is the heart of production, and there is never just one way across. One shot might start from a hand-drawn frame; another from a single line of text; another from a reference video you crop to length. Ordinary Animator does not try to flatten that variety into one rigid procedure. It gives you two clear goals, lets recipes and the AI carry the variable work in between, and stays out of your way if you'd rather do it by hand.

Two goals, not many phases

Shot work has two deliverables, and each phase is named for the media you end up with:

• Shot Design — a quick storyboard image for every shot.
• Animation — a finished video clip for every shot.

That's deliberately small. Everything between a storyboard and a clip is too variable to pin into fixed steps, so we don't — recipes and the AI handle it. The pipeline tells you what you're trying to have; it doesn't dictate how you get there.

Shot Design: the storyboard

A storyboard is a quick image — a preview. It can be a hand sketch, a fast AI pass, or one frame pulled from a multi-angle reference. Fidelity is not the point; blocking is.

Blocking is working out the staging of the shot: who is in frame and where they stand, how they're posed and what they do, where the camera sits and whether it moves, and what the audience's eye is drawn to. Borrowed from theatre and animation, it's the cheap place to get staging right — redraw a rough frame in seconds instead of paying to regenerate a finished clip.

As you board a shot you also capture details about it — shot type, who's in it, camera angle, motion, rough duration. This isn't busywork or a form to grind through: those details are what the generation models and the AI read later to produce the right image and video. The AI helps fill them in and flags what's missing, so you're making creative decisions, not data entry.

Media, tagged by purpose

The concrete thing that flows through production is media, tagged by its purpose. The media gallery shows every image, clip, and audio file; each one carries a tag for what it's for:

• storyboard — a quick preview frame
• start frame — a high-quality still used to seed image-to-video
• plate — a background image to composite onto
• reference — a character, style, or location image the model should match
• driving clip — a video whose motion or expression is copied
• audio — the dialogue and music you've already produced

Recipes read tagged media and write new tagged media. The same purpose can be reached many ways — a start frame might come from a sketch, from a text prompt, or from a posed 3D figure — so the tag is the stable, useful thing, and the route to it is not worth naming.

Animation: producing the clip

The second goal is a video clip per shot, and this is a single production step — because the path is recipe-shaped and varies from shot to shot:

• Text-to-video — just a prompt; nothing to prepare.
• Image-to-video — make a high-quality start frame first, then animate it.
• Video-to-video — crop a driving clip to length, gather reference images, generate.
• Static + effects — a slow camera move over a still; no character motion to get wrong.

Sometimes you build a polished still before generating; sometimes you go straight to the clip. That variability is exactly why this isn't carved into fixed sub-steps — the recipe decides what's needed, and the recipe is the concrete, repeatable thing that does the work.

The AI rides alongside. It looks at how the shot was blocked and suggests an approach in plain language — "one good route here is a hand sketch into an image model for the start frame, then image-to-video" — and hands you the recipe to run. Before you spend generation time, it checks you have the right inputs: "this model needs a clean, face-forward start frame, and yours is a wide shot — consider a static shot with a push-in instead." That suitability check is cheap and happens before you pay for a render.

The AI guides; you don't grind a checklist

The goal of all this captured detail is twofold — feed the models the specifics they need, and support good creative choices through AI review. It is not a 40,000-item checklist to tick off by hand. The AI fills in what it can, reviews each shot with awareness of your project's genre and tone, and surfaces only what needs your judgement. You stay in the creative seat; the system carries the bookkeeping.

Review at the scene level

You generate clips shot by shot, but you review them by scene — because the qualities that matter most are properties of the scene, not the single shot:

• Does the motion hold together and feel right for the style?
• Is continuity preserved across adjacent shots — clothing, props, lighting, screen direction?
• Is the visual style consistent, and does each character stay recognisable?
• Does the sequence tell the scene clearly?

One scene-level review, with notes against each quality, replaces a long per-shot sign-off. Watch the scene's clips together, fix what doesn't hold, approve the scene.

The knowledge base

The AI's suggestions are only as good as what it knows about each model. That accumulated wisdom — "image-to-video with this model shines from a clean full-face frame but falls apart on wide, multi-character shots" — is the knowledge base: an experienced artist's instincts, written down so the AI can apply them on every shot. A new model arrives as a new entry, not a rebuild.

Knowledge base — not yet implemented. The wisdom that will feed the AI's advice is being gathered now (a model-discovery process collects what each model is good and bad at). Wiring it into per-shot suggestions comes later.

You don't have to follow the pipeline

The two-goal flow is guidance, not a gate. If you already know exactly how you want to make a shot, open the media gallery, run the recipes you want, and select your final clip. The pipeline is there to help when you want a path through the variety — not to stand between you and the work.