Floats To Ints (mtb)

The pack's own description keeps this one short: "Conversion utility for compatibility with frame interpolation." That's the whole story - some frame-interpolation nodes (the kind that generate in-between frames to smooth out or slow down a video, RIFE-style tools being the common example in the ComfyUI ecosystem) want their frame indices or counts as integers, not floats. If whatever's upstream in your graph is handing you a FLOATS list - say, a schedule of values from another mtb node or a batch operation - and the interpolation node downstream is refusing the connection because it wants INT/INTS, this is the bridge.

What it does

It takes a FLOATS list and converts each value to an integer. There's no rounding-mode setting exposed in the node, so you don't get a choice between round-up, round-down, or round-to-nearest - it's a plumbing node, not a math node: no creative decisions, just making sure the numbers arrive at the next node in a type it'll accept.

Inputs and outputs that matter

• floats - the FLOATS list you're converting. That's the only input, and there's nothing else to configure.
• Two outputs: INTS (the converted list) and INT (also present as a separate output). Wire INTS into anything downstream that wants a list of integers; the INT output is there for cases where you just need a single integer value out of the pipeline rather than the whole list.

Installing it

• ComfyUI Manager - search "MTB Nodes", install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/melMass/comfy_mtb, restart. A manual clone needs pip install -r requirements.txt run inside the comfy_mtb folder first.

Pure conversion logic, no models or heavy dependencies attached to this node specifically.

Common issues & troubleshooting

Values come out one off from what you expected. With no rounding-mode control exposed, a float-to-int cast landing on the "wrong" side of .5 (rounding 2.9 down to 2 instead of up to 3, or vice versa) is the first thing to check if your downstream frame counts are consistently off by one. If you need a specific rounding behavior, run your values through Fit Number (mtb) first with a small offset to nudge them across the boundary before they hit this node.

Downstream interpolation node still complains about the type. Double check whether it wants INTS (a list) or a single INT - this node gives you both as separate outputs, and wiring the wrong one in is an easy mistake to make since they're right next to each other in the node.

A handful of mtb's other nodes fail to load at startup. That's normal for this pack given how many nodes it ships at once - check the console output for [comfy_mtb] STATUS and visit http://127.0.0.1:8188/mtb (your own ComfyUI address) for what didn't load and why. This particular node has no optional dependencies, so it's essentially never the one missing.