Create Incrementing Number List ♾️Mixlab

Sometimes you don't want one number, you want a range of them - 0, 1, 2, 3... or 0.0, 0.25, 0.5... - so you can batch a parameter across a spread and compare. This node builds that list of numbers for you and hands it out as both an integer list and a float list. Wire it into anything that batches and you've got an X/Y-style sweep: same workflow, one value marching up each run.

What it's for

The everyday use is a parameter sweep. Want to see denoise at 0.3, 0.4, 0.5, 0.6? Generate that list here and feed it into a batched denoise. Same for CFG, LoRA strength, a frame index for animation, or a seed offset. It turns "render this five times with a slightly different number each time" into a single wired list instead of five manual runs. The Video category placement hints at the animation use - driving a value that changes frame to frame.

The inputs that matter

• min_value - where the list starts.
• max_value - the upper bound of the range.
• step - how much each number increases by.
• count - how many numbers to produce. This is your batch size.
• seed (optional) - for when you want a reproducible list; leave the default if you don't need it.

The interplay of min/max/step/count is what shapes the list - set the start, the spacing, and how many you want, and you get an evenly-marching sequence between your bounds. (Those enormous max limits, ~1.8e19, are just the numeric ceiling, not a value you'd ever set.)

Two outputs: int_list and float_list - the same sequence in both forms. Use int_list for things that want whole numbers (frame indices, seeds), float_list for continuous parameters (denoise, strength, CFG). Wire whichever matches the socket you're driving.

Installing it

Get the pack via ComfyUI Manager (search mixlab, install comfyui-mixlab-nodes, restart), or clone it:

cd ComfyUI/custom_nodes
git clone https://github.com/shadowcz007/comfyui-mixlab-nodes

then install requirements and restart. No downloads.

Common snags

• The list isn't as long as you expected. count controls how many numbers come out - it's the batch length. If you set count to 1 you get a single value, which defeats the point.
• Feeding a float into an int socket (or vice versa). That's exactly why the node gives you both outputs. Match the output type to the parameter - int for frame/seed, float for strength/denoise - instead of forcing a conversion downstream.
• Nothing batches. This produces a list; the node you feed has to actually iterate a list input. If the receiver only takes a single value, it'll grab the first item and ignore the rest. Pair it with a node (or workflow mode) that runs once per list item.