✍ Int Input

Int Input [DVB] is a number in a box. That's it. You type an integer, it outputs that integer. It is the least glamorous node in the entire Dream Video Batches pack, and it's the one you'll reach for constantly once you understand why it exists.

ComfyUI already lets you type a number directly into any node's input field. The problem is that number lives in that one spot. Int Input exists to make the value a wire - a single source of truth you can route to a dozen nodes at once. Change it once and everything downstream updates. No more retyping "16" on eleven different inputs and discovering you missed one. That's the whole use case, and it's more useful than it sounds.

There's a second, sneakier use: thread a value from a computation. The pack's math nodes (Multiply [DVB], Divide [DVB], Calculation [DVB]) all output INT alongside FLOAT, and Int Input is the clean way to take one of those results and feed it somewhere a literal would be awkward. It's also the pack's own idiom - its nodes expect integers in places like frame counts and dimensions, and having them on a wire keeps the whole graph consistent.

The interface

• value (default 0) - the integer you want on the wire.
• Output: INT - the same value, now a connectable output.

Nothing else. No conversion, no math, no validation tricks. The sibling nodes Float Input and String Input do the identical pass-through for their own types, so the pattern is consistent across the pack.

Installing

It's part of Dream Video Batches (Alt Key Project / Dream Project). One install gets the whole pack:

cd ComfyUI/custom_nodes
git clone https://github.com/alt-key-project/comfyui-dream-video-batches.git
cd comfyui-dream-video-batches
pip install -r requirements.txt

Or find "Dream Video Batches" in ComfyUI Manager, install, and restart. No models, no downloads beyond the pack.

Where people get burned

Honestly, the only real trap is overuse - dozens of disconnected int nodes clutter a graph fast. ComfyUI has gotten better at node inputs over time, so for a value used in one place, just type it in the input field and skip the node entirely. Reach for Int Input when the value is reused or computed, not for every number in your workflow. And since it outputs plain INT, it plugs into anything, anywhere - there's no frame-set unwrap dance to worry about with this one.