Repository navigation
Plan Reference
Use this page when a Plan control is unclear. The supplied workflows already contain safe defaults.
| Control | Meaning | Practical choice |
|---|---|---|
run_name |
Production and checkpoint identity | New short name for a new production |
| width / height | H3 canvas | Keep the example; values must be divisible by 32 |
| default duration | Scene duration request | Keep the example until the graph works |
| default steps | Sampler steps inherited by scenes | Match the selected model/LoRA graph |
video_blend_frames |
Assembly-only overlap entering a scene |
0 for a hard boundary |
generation_fingerprint |
Model-body choices outside Plan | Connect automatic coverage where supplied |
| Field | Meaning |
|---|---|
id |
Stable scene name |
prompt |
Complete instruction for this scene |
seed |
Per-scene seed; use a string in raw JSON |
steps |
Optional override of the Plan default |
length / duration_seconds
|
Exact frames or a convenient duration request |
| incoming transition | Optional visual-continuity override |
| Source reference / generated continuity / source lock | Optional audio overrides |
| LoRA route | Optional connected per-scene LoRA selection |
Blank overrides inherit Generation Profile. Scene 1 has no incoming generated predecessor unless Existing Video Context supplies one.
H3 uses 24 fps and valid raw lengths on the 17k+5 grid. Requested seconds are
rounded upward. A continued scene delivers:
raw scene frames - repeated incoming context
Use Plan or Preflight's timing summary instead of estimating the final duration by hand.
Changing an accepted scene's prompt, seed, timing, references, source window, model fingerprint, or generation policy can require regeneration. Future-scene and assembly-only changes do not invalidate an earlier checkpoint. Preflight reports the exact mismatch.
The complete Plan format documents every JSON field and compatibility form.