(deforum) Noise Parameters
The fiddly knobs that shape your animation's motion
- deforum_data
- deforum_data
Of all the Deforum parameter blocks, this is the one people love to hate. The noise settings are where you fight flicker, grain, and the "why does it melt every five frames" problem - but they're also where a whole generation of tutorials got lost. The good news: you only need three of the knobs 90% of the time, and the node ships with sane defaults (0:(1.05) multiplier, 0:(0.1) amount, uniform noise).
Deforum animations are essentially per-frame img2img, and each frame starts from the previous one plus noise. The noise you inject - its type, strength, and how it changes over time - is the single biggest lever on how the animation moves and whether it holds together. This node writes all of that into the deforum_data dict as schedules.
The knobs that matter
noise_type-uniform(plain random noise, the default) orperlin(smooth, spatially coherent noise). Perlin is the "organic drift" option; it produces softer, more liquid motion instead of the sparkly grain of uniform noise. If your animation shimmers, try perlin.noise_multiplier_scheduleandenable_noise_multiplier_scheduling- the per-frame multiplier on noise strength. This is the flicker-fighting knob: raise it when frames are too similar (stuck, jittery), lower it when frames are too different (melting, warping). Default0:(1.05)is a mild nudge above baseline.amount_schedule- how much noise each frame gets (default0:(0.1), i.e. 10%). This is the coarse strength control. More noise = more change per frame = more motion and more chaos.
The perlin cluster
If you select perlin, four more inputs appear: perlin_w and perlin_h (the grid resolution of the noise field, both default 8 - lower is chunkier, higher is finer), perlin_octaves (detail layers, default 4), and perlin_persistence (how much each octave contributes, default 0.5). These are classic fractal-noise parameters; the defaults are a fine starting point, and the ones you'll actually tune are perlin_w/perlin_h.
The ones you can ignore
kernel_schedule (blur kernel, default 5), sigma_schedule (noise smoothing, default 1.0), and threshold_schedule (default 0.0) are legacy Deforum noise-shaping schedules. They exist for workflow compatibility and mostly sit at their defaults in the wild. Don't feel obligated to understand them before pressing play.
Output is deforum_data, chained into the sampler.
Installation
Part of Deforum Nodes:
cd ComfyUI/custom_nodes
git clone https://github.com/XmYx/deforum-comfy-nodes.git
Restart, or install "Deforum Nodes" by XmYx via ComfyUI Manager. This node itself is lightweight - a settings writer - but it feeds a loop that needs the full backend (Python 3.10, the deforum[comfy] packages) to run.
A quick tuning recipe
Flickery animation → switch to perlin noise. Still flickery → raise noise_multiplier_schedule slightly (1.05 → 1.1). Frames melting into mush → drop amount_schedule from 0.1 toward 0.05. That triangle covers most noise complaints without ever touching kernel, sigma, or threshold. The trap is over-tuning: change one schedule at a time, because they interact, and a combination of two "small" tweaks can wreck a render.
Inputs (12)
| Name | Type | Default | Description |
|---|---|---|---|
| enable_noise_multiplier_scheduling | BOOLEAN | true | — |
| noise_multiplier_schedule | STRING | 0: (1.05) | — |
| amount_schedule | STRING | 0: (0.1) | — |
| kernel_schedule | STRING | 0: (5) | — |
| sigma_schedule | STRING | 0: (1.0) | — |
| threshold_schedule | STRING | 0: (0.0) | — |
| noise_type | COMBO | 2 options: uniform, perlin | |
| perlin_w | INT | 8 | — |
| perlin_h | INT | 8 | — |
| perlin_octaves | INT | 4 | — |
| perlin_persistence | FLOAT | 0.50 | — |
| deforum_dataopt | deforum_data | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| deforum_data | deforum_data | — |