Float to Floats 🎭🅐🅓

This is the smallest node in the whole pack, and it does exactly one thing: it takes a single FLOAT widget value and wraps it into a FLOATS (list) output. That's the entire job. It exists because ComfyUI, and this pack specifically, distinguishes between a scalar float and a list of floats as separate types, and plenty of inputs across AnimateDiff-Evolved's scheduling nodes want the list type even when you only care about one value.

You won't reach for this often, but when you do, it's usually because a node wants a FLOATS input and all you have is a plain number - this is the adapter that bridges the two.

How it works

There's no transformation logic here beyond the type conversion itself. Whatever value you set on the widget becomes the sole entry in the output list. If you need a genuine multi-value list rather than a single wrapped number, this node alone won't build it - you're looking at a different node (or several ADE_FloatToFloats combined through whatever list-building mechanism the target input expects) for that.

The inputs and outputs that matter

There's exactly one input and one output, and neither has a hidden catch: FLOAT (default 39, no listed min/max on this node) is the value you set, and FLOATS is the wrapped list output. The default value of 39 is arbitrary - the node ships with a placeholder number rather than something meaningful like 0 or 1, so don't read anything into it; you'll be changing it to whatever value you actually need.

How to install it

Standard for the pack - ComfyUI Manager, search AnimateDiff Evolved by Kosinkadink, or:

cd ComfyUI/custom_nodes && git clone https://github.com/Kosinkadink/ComfyUI-AnimateDiff-Evolved

No model download needed - this is a pure utility node, unrelated to motion modules or checkpoints.

Common issues & troubleshooting

Connected it to something that still complains about the type. Double-check the target input actually wants FLOATS (plural, list type) rather than a plain FLOAT. If the target wants a scalar, you don't need this node at all - just wire the number in directly, or convert the widget to an input on the target node itself.

Expected a list of multiple values and only got one. That's correct behavior for this node - it wraps exactly one number into a one-item list, it doesn't generate a sequence or range. If you need genuine multi-value scheduling (a value that changes across frames), you want one of the pack's actual scheduling nodes, like ADE_AnimateDiffKeyframe for motion strength over time, rather than this converter.

There's genuinely not much more to say about this one - it's a small plumbing node you'll use maybe once in a graph that needs it, and skip entirely otherwise.