Flake Animate Preset Combo

This one is a variant node, and it's honest about it. The Python class is literally class FlakeAnimPresetCombo(FlakeAnimPreset): pass - same backend, same inputs, same single flake_anim_data output. The difference lives in the frontend, and it's all about queueing.

What it actually does differently

A normal Flake Animate Preset node holds one preset. Queue once, you get one video. The Combo version holds a list of presets and rotates the preset widget over that list while your batch is being queued. Flakes computes the run count for the whole graph before queueing - for a combo of this type it's the number of active presets - and then fires off one prompt per preset, each one a real job with its own flake_anim_data.

So the point isn't "more nodes", it's that the comparison happens inside a single queue action. You set up your graph once, tell the node "these four presets", and walk away. That's the same idea as the image side's Flake Model Combo, and it's the right shape for a medium where a single clip can take minutes and you want the comparison running while you do something else.

What you'd actually compare

The useful cases are the ones where rewiring is annoying:

• One preset at 4 steps versus one at 6, on the same start image and seed, to see whether the extra compute is buying anything.
• Wan 2.2 versus MiniMax H3 on the same shot. Different families, same node, same output pin - the downstream animate nodes don't care which one arrives.
• Two Wan 2.2 presets with different refiner_step or shift values, when you're chasing the point where motion stops looking soupy.

Because the two families load different model files entirely, mixing them in one combo also means the base models get unloaded and reloaded between jobs. Correct, but slow - and if VRAM is tight, budget for it.

Inputs, outputs, install

Identical to Flake Animate Preset: family, preset, optional overrides_json ("JSON override of steps/cfg/sampler/scheduler/filename_prefix. Managed by the Flake widget.") and one flake_anim_data output that goes into Flake Animate Stack / Combo, or directly into Flake Generate Animation.

Install is the pack install, no separate step:

cd ComfyUI/custom_nodes
git clone https://github.com/JeyzerMC/comfyui-flakes

Restart, then search for ComfyUI Flakes in Manager if you'd rather click. There are no dependencies beyond the pyyaml ComfyUI already has.

Traps

The one that bites: your job count multiplies. Presets × flakes × start images. Four presets and three start images on a combo-fed chain is twelve clips, and each of those is a full video generation. Check the queue count before you commit a GPU-hour to a typo.

The other: a preset must exist on disk in models/flakes/model_presets/video/<family>/ before this node can list it, and the placeholder entries (Select a preset..., No model preset is selected) aren't presets - selecting one raises No animate preset is selected - pick one from the dropdown.

And if you're only testing one thing, use the plain Preset node. A combo with one active preset is a longer way to write the same request.