Nodes/Deforum Nodes/(deforum) Big Bone Reset Node
ComfyUI Node

(deforum) Big Bone Reset Node

The reset switch that forces your animation back to frame zero

By XmYx·Created 3 years ago·Updated 3 months ago· 198
(deforum) Big Bone Reset Node
    • BOOLEAN
    reset_deforumfalse

    Deforum nodes carry state across queue runs. The sampler remembers frame counters, cached latents and images persist between executions, and the Save Video node accumulates frames until it decides the animation is done. Most of the time that statefulness is exactly what makes long animations work. But when you want to start over - fresh seed, fresh frame count, empty caches - you need something to flip the whole thing back to zero. (deforum) Big Bone Reset Node is that something: a single boolean input that, when enabled, sets the pack's global reset flag.

    How it works

    The node writes directly into the pack's global state object (gs.reset = reset_deforum). That flag is consulted throughout the pipeline: when it's true, the frame counter resets, the caches clear, and the Save Video node treats the incoming frames as the start of a brand-new clip (it even triggers a dump of whatever it was holding). It's a global lever rather than a per-node setting, which is why it's named like a cartoon skeleton - it resets the big bones of the pipeline at once, not just one piece of it.

    The node also marks itself to always re-evaluate, so toggling the checkbox reliably propagates even if ComfyUI would otherwise cache the result. Its output is the same boolean you set, passed through for wiring convenience.

    The inputs and outputs

    • reset_deforum - a boolean, default false. Flip it true (and keep the run going) to reset the pipeline state.
    • BOOLEAN - output, a pass-through of the reset value.

    When you actually need it

    This is a workflow-management node, and its moment is "I'm running the same animation repeatedly to iterate on settings." Without a reset, a second run can silently continue from where the last one left off - frame counters advance, caches hold stale data, and your "fresh" render isn't fresh. If you've ever hit "queue" a second time and gotten something weirdly different (or identical when you expected different), a missing reset is a prime suspect. Enable it before re-runs, or wire it to fire at the start of a loop that intentionally restarts the animation. It's a small node, but it's the difference between reproducible iterations and chasing ghosts.

    Installing it

    Part of Deforum Nodes (XmYx). ComfyUI Manager → "Deforum Nodes", or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/XmYx/deforum-comfy-nodes.git
    

    Restart ComfyUI; first boot runs install.py (librosa, opencv-contrib-python, moviepy, numpy<2.0.0, deforum-studio backend). Python 3.10 per the README.

    Where people get burned

    Two traps. The obvious one is leaving it enabled permanently - if reset_deforum stays true, every run wipes caches and the frame counter never advances, so your animation can never get past frame one; it's a reset switch, not a setting to leave on. The subtler one is expecting it to reset everything including things it doesn't own: it resets the Deforum pack's state, but caches in other packs (IPAdapter, ControlNet) are outside its reach. And note it can't reset the save node's on-disk frame cache if that node keeps state separately - when in doubt, clear caches in the Save Video node too.

    Categorydeforum/logic

    Inputs (1)

    NameTypeDefaultDescription
    reset_deforumBOOLEANfalse

    Outputs (1)

    NameTypeDescription
    BOOLEANBOOLEAN