AD Block 🎭🅐🅓

This is about as deep into AnimateDiff-Evolved's advanced tuning as it gets. The README's feature list mentions "merging motion model weights/components, including per block customization" in passing, with no further elaboration - and that one line is essentially the entire public documentation for this node and its sibling, AD Block+. If you're a beginner reading this hoping for a node you'll actually reach for, the honest answer is: probably not, and that's fine - most AnimateDiff workflows never need this.

What it's for

Like a UNet, a motion module is organized into blocks - structural groupings of layers, roughly corresponding to different depths/stages of the network (the kind of down/mid/up block structure diffusion models are typically built from). The Motion Model Settings nodes elsewhere in this pack let you scale a motion module's influence globally, or split by weight type (positional encoding vs. attention vs. other). AD Block is a different axis: instead of "which type of weight," it's "which block." effect and scale - the same multival types used for global motion control elsewhere - apply here to one specific block, letting you turn a block's contribution up, down, or off independently of the rest of the module.

The output, AD_BLOCK, is presumably meant to be combined across multiple AD Block nodes (one per block you want to control) into a full per-block configuration, though the exact combination mechanism isn't documented beyond the node schema itself.

Inputs and output

• effect (optional, MULTIVAL) - how much this block's motion contribution applies at all.
• scale (optional, MULTIVAL) - motion intensity for this block specifically.

Output is AD_BLOCK.

How to install it

Comes with the base pack - no separate download.

• ComfyUI Manager - search AnimateDiff Evolved by Kosinkadink, install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/Kosinkadink/ComfyUI-AnimateDiff-Evolved, restart.
• Needs a motion module loaded in the same graph - this node has nothing to act on by itself.

Common issues & troubleshooting

There is essentially no community documentation for this node. Zero GSC impressions, no meaningful discussion out in the wild - this is about as niche as the pack gets. If you're here, you're likely reverse-engineering behavior from the schema and the README's one-line mention, same as this article is. Treat any specific tuning advice (including this article's) as a starting hypothesis to test, not settled guidance.

Not sure this is the right tool for your problem. If you want to globally dampen or boost motion, the scale/effect multivals on the standard model-application nodes are the well-trodden path and almost certainly what you actually want. Reach for per-block control only after you've confirmed a global adjustment doesn't get you where you need to be, and you have a specific reason to believe one structural part of the motion module is the culprit.

Wired it in and nothing visibly changes. Confirm the AD_BLOCK output actually reaches wherever the pack expects per-block configuration to be consumed in your model-application chain - a disconnected AD Block node has no effect on generation.