Per scene, not per project
A terrace at dusk may deserve AI motion while a bedroom is better held for three seconds. The plan mixes both; the cost line reflects the mix, and each clip carries its own provider request id.
AI motion and transitions
Opt-in cinematic AI per scene, with the provider, model version and price recorded before it runs.
Not built as a product surface. The provider adapter, queue and budget guard exist and are tested against a simulated provider; no paid generation has run.
Fidelity motion is cheap, deterministic and cannot invent a wall. Cinematic AI is the opposite trade: real movement, a real bill and a chance of an artefact you have to reject. It is therefore a per-scene decision, never the default, and never applied to a photograph that has not been reviewed.
A terrace at dusk may deserve AI motion while a bedroom is better held for three seconds. The plan mixes both; the cost line reflects the mix, and each clip carries its own provider request id.
Every attempt stores the provider, model version, parameters, duration, cost and a redacted request snapshot. That is what makes a re-generation decision auditable instead of a guess.
Refusing a clip restores the deterministic move for that scene. The rest of the film stays untouched, and the previous version remains in the project record.
No, and it should not try. It animates a frame; it does not re-shoot it. If the source is soft, out of focus or badly exposed, the honest move is to re-shoot or to hold the still.
No. A model that animates can bend a doorframe. The product prices a regeneration and makes rejection easy; it does not pretend the output is deterministic.
The workspace, the roles, the credit ledger and the invitation flow are live. Create the account now and be first in line when this milestone opens — no card is collected.