Skip to content
Preflight Cinema
Resources

Docs

Create a project to keep scripts, assets, scenes, shots, takes, and generated outputs together. Upload references only when you have the rights to use them, then assign each reference to the correct role before generating.

On this page
  1. Start with a project
  2. Prepare, check, preview, generate
  3. Use reference lanes deliberately
  4. Compare what was written, sent, and returned
  5. Questions

Start with a project

Create a project to keep scripts, assets, scenes, shots, takes, and generated outputs together. Upload references only when you have the rights to use them, then assign each reference to the correct role before generating.

Prepare, check, preview, generate

A normal take moves from Script / Action to Prompt Preflight, optional Frame Preflight, proxy review, feedback, and master generation. The exact path depends on the selected model, available references, and whether the shot needs speed or control.

Use reference lanes deliberately

A start frame, end frame, character, location, product, and style reference do different jobs. Assigning the wrong role can make the provider chase the wrong target, so the workspace keeps reference role metadata visible for review.

Compare what was written, sent, and returned

When a result is wrong, inspect the user script, approved prompt, exact provider request, returned output, frame evidence, and saved feedback before starting the next paid take. That trace is the core Preflight Cinema workflow.

Questions

  • Why use preflight before generation?

    Prompt Preflight and Frame Preflight help reduce wasted generations by checking the script, references, model route, and visual direction before more expensive output is requested.

  • Can final regeneration be exact?

    Exact regeneration depends on the selected model and provider. Preflight Cinema can preserve prompts, references, settings, and evidence, but AI video may still drift between attempts.

  • When should teams approve a direction?

    Teams should approve the direction before expensive generation when references, camera choices, and constraints are clear enough to continue.

  • When should I use Safe Path instead of Fast Path?

    Use Safe Path when continuity, identity, product details, logo stability, or client approval matter. Use Fast Path for lower-risk drafts, mood tests, or quick exploration.

  • What should I include when reporting a failed generation?

    Send the project name, video ID, generation attempt ID if available, approximate time, what you expected, and what was wrong. Do not send passwords, card numbers, or provider secrets.

  • Who is responsible for commercial rights?

    The user is responsible for confirming rights to uploaded references, people, brands, products, locations, artwork, footage, and final use. Preflight Cinema helps organize review but does not provide legal clearance.

Stuck on a shot or a payment? Tell us the project and the shot, and we will look at the same thing you see.

Contact support