A production, not a pile of clips.
How a production works in 1VideoTool: story breakdown into acts, scenes and shots, reusable cast and locations, shot-level direction, takes that are never overwritten, a real timeline, and eight ways to export what you made.
How a production moves
- 01
Bring in the source
A concept, a screenplay, an image, a video, or an audio track. Import a Fountain script and it is parsed rather than pasted.
Story Workspace
- 02
Break it into structure
The source becomes acts, scenes and shots you can edit. Structure exists before a single frame is generated, so you can finish the plan without spending anything.
Guided Studio, Production Board
- 03
Cast the world
Characters, products, objects, locations, styles and voices become reusable entities with reference sets. Attach them to shots and they stay consistent across the film.
Cast & World
- 04
Direct each shot
Camera, composition, action, dialogue, duration, start and end frames, motion. The prompt is compiled from that intent, the attached entities and the provider's contract — you direct the shot, not the prompt box.
Director Workspace
- 05
Generate and review takes
Every result is a take. One becomes active; the alternatives stay reviewable. Nothing is silently overwritten, and the plan shows price and capability before it runs.
Generation Space
- 06
Cut, score and deliver
Approved takes land on a real timeline with dialogue, effects, music, captions, transitions and overlays. Export the cut, the animatic, the storyboard, an edit interchange, and the project itself.
Timeline, Finish & Deliver
The rules underneath it
The production survives the generator
Models change every few months. Provider and model are adapters attached to a shot, never part of the project schema, so swapping one does not invalidate the film.
Shots are the unit of work, not prompts
A prompt is a compiled artifact derived from shot intent, entities, style and the provider contract. You keep directing after the model changes.
Every generation is a take
Results are never silently replaced. One take is active; the rest stay on the shot with the prompt and settings that produced them.
Continuity is project data
Character, product, location, wardrobe, voice, lighting and frame continuity are recorded against the production, not held in your head or in a chat scrollback.
Cost is part of direction
A generation plan shows capability and price before it starts, then records what was actually spent. Your keys, your providers, no markup on compute.
Human approval is production state
Approval is recorded against a revision and an artifact. It is not a dialog that disappears when you close it.
Generation providers
You add the keys and you are billed by the provider. Keys go to OS secure storage, never into the production folder.
- Gemini
- Script breakdown, prompt assist, stills, and Veo motion.
- Runway
- Second image and video adapter.
- ffmpeg
- Local animatic and MP4 export when it is on your PATH.
What you can export
Final cut
MP4 through ffmpeg
Animatic
Board timing before generation
Storyboard
PDF, shot by shot
Image sequence
Frames as files
Edit interchange
FCP7 XML into your NLE
Captions
Local transcription
Project package
The readable folder itself
Manifest
What was made, by which model, at what cost
Where the boundaries are
Not a prompt box wired to one video model.
A single generator gives you clips. This gives you a production: story, entities, shots, takes, decisions, a timeline and a cut, all of which outlive whichever model made the pixels.
Not a cloud studio that owns your project.
The project, the assets, the timeline and the exports are files in a folder you chose. Generation goes straight from your machine to your provider.
Not a launch-video wizard.
Ads and product promos are outputs of a production system, not the product. Campaign strategy and publishing belong to 1MarketingTool.
Not a general editor with AI buttons bolted on.
The timeline exists to finish a generated production, with the references and decisions behind every frame still attached.
Everything, in one list
- Import a concept, screenplay, image, video or audio track as the source of a production
- Break a story into acts, scenes and directed shots before generating anything
- Reusable characters, products, objects, locations, styles and voices with reference sets
- Shot-level direction: camera, composition, action, dialogue, duration, start and end frames
- Prompts compiled from shot intent, attached entities and the provider contract
- Swappable generation providers, with capability and price shown before a run
- Every generation preserved as a take; one becomes active without destroying the alternatives
- Frame chaining and explicit continuity notes across shots
- A real timeline with dialogue, sound effects, music, captions, transitions and overlays
- Production control: readiness, missing artifacts, decisions, approvals, spend and resumable jobs
- Export a final cut, animatic, storyboard PDF, image sequence, FCP7 XML and a manifest
- Productions stored as versioned JSON, media and ledgers in a folder you own
- Provider keys held in OS secure storage, never in the production folder
- A bundled twelve-shot sample production that works with no API keys at all
- An MCP server so external tools can drive the production through typed commands