(deforum) Animation Parameters
The node that decides what kind of animation you're making
- deforum_data
- deforum_data
(deforum) Animation Parameters is where every Deforum graph starts, because it's where you pick what kind of animation you're making. Three fields - animation_mode, max_frames, border - and one of them determines the entire shape of the thing you're building. Set the mode wrong and nothing downstream makes sense; set it right and the rest of the parameter chain slots into place.
The inputs that matter
- animation_mode - the dropdown with five choices:
None,2D,3D,Video Input,Interpolation. This is the master switch.- 2D - classic Deforum: zoom, pan and rotate the image plane between renders. The style that made Deforum famous, and the easiest to start with.
- 3D - adds depth-based warping: the camera actually moves through the scene using a depth map. More convincing, needs a depth model, and costs more VRAM. This is the mode people mean when they say "the camera moves."
- Video Input - you bring a real video and Deforum re-renders it frame-by-frame as img2img (the "AI video morph" workflow).
- Interpolation - render sparse keyframes and let interpolation fill the gaps. Works hand-in-hand with the cadence/FILM nodes.
- None - no motion transforms; useful for pure prompt-evolution animations.
- max_frames (INT, default 120) - how many frames the animation runs. Bigger = longer and more expensive. This gets read by the Iterator and the Integrated Pipeline, so it's the number you'll bump constantly.
- border -
wrap,replicate, orzeros: how the frame's edges are filled when the camera moves and reveals empty space.wrapis the classic trippy wrap-around;replicatesmears the edge pixels (looks more "filmic");zerosshows black edges. For most 2D work,wraphides the seams best.
Output:
- deforum_data - the accumulated parameters dict, chained forward to the next parameter node or straight to the Iterator / Integrated Pipeline.
How it works
Like every (deforum) ... Parameters node, this one is built on the pack's DeforumDataBase: it merges its fields into the shared deforum_data dictionary that flows through the graph. Chain several parameter nodes and they layer their keys on top of each other - last writer wins. So the chain order matters: a (deforum) Diffusion Parameters node placed after this one can override values, and that's fine as long as you know it's happening.
Installing this pack
Part of Deforum Nodes by XmYx. ComfyUI Manager: search Deforum Nodes, or:
cd ComfyUI/custom_nodes
git clone https://github.com/XmYx/deforum-comfy-nodes
Restart and let install.py install the deforum-studio backend from GitHub plus its scientific-Python stack (numpy pinned below 2.0; Python 3.10 required). The node itself is pure plumbing - no models - but the pack's install is all-or-nothing.
Common issues
- Animation is static despite setting 2D/3D. If no translation parameters (zoom/pan/angle) are feeding into the chain, motion schedules default to zero and nothing visibly moves. Add a
(deforum) Translate Parametersnode - its defaults already include a gentle zoom. - max_frames mismatch. The Integrated Pipeline and the Iterator read
max_framesfromdeforum_data; if you're also setting it somewhere else, the last writer wins. Trace the chain if the length is surprising. - Black edges in 3D mode. That's
zerosborder doing its job at high warp. Switch towraporreplicate.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| animation_mode | COMBO | 5 options: None, 2D, 3D, Video Input, Interpolation | |
| max_frames | INT | 120 | — |
| border | COMBO | 3 options: wrap, replicate, zeros | |
| deforum_dataopt | deforum_data | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| deforum_data | deforum_data | — |