Curve (mtb)

Straight from the node's own description: this one is marked WIP. That's worth leading with, because it's rare for a node's own metadata to flag itself as unfinished, and it's honest of the pack to leave that label in rather than hide it. Curve is meant to be a basic FLOAT_CURVE input - draw a curve by hand in the node's UI rather than picking a preset easing function - and it's the raw building block behind Curve To Float. If you want a preset, mathematically-defined easing curve instead, Batch Float's easing dropdown is the more reliable path today; reach for Curve when you specifically need a shape no preset gives you and you're willing to accept it's still being finished.

What it's for, when it's what you want

Batch Float gives you 22 named easing functions - Linear, the Sine/Quart/Cubic/Circ families, and more - which covers most standard animation timing. But sometimes you want a curve that doesn't match any named preset: a custom ramp with a specific hold in the middle, an asymmetric ease that speeds up twice, anything hand-authored. Curve is the input node for that case - a FLOAT_CURVE widget you draw directly, which then feeds into Curve To Float to actually sample it into usable numbers.

The input and output

• curve (FLOAT_CURVE, required) - the drawn curve itself, edited directly in the node.

Output: a single FLOAT_CURVE - passed through, ready to wire into Curve To Float (which samples it at a chosen number of steps and gives you back a FLOATS list or a single FLOAT).

Installing it

ComfyUI Manager: search MTB Nodes, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/melMass/comfy_mtb

then restart ComfyUI. No models involved.

Common issues

The honest first troubleshooting step here is: it's WIP, by the pack's own admission. If the curve editor UI feels rough, doesn't save the way you expect, or a specific edit doesn't behave, that's plausibly the current state of an unfinished feature rather than something you're doing wrong - check the pack's GitHub issues for this node before spending a long time assuming user error.

For a production workflow where reliability matters more than a bespoke curve shape, Batch Float's preset easing functions are the steadier choice today - they cover a genuinely wide range of timing (linear, ease-in, ease-out, ease-in-out, across several curve families) without depending on a feature the pack itself hasn't finished.

And the pack-wide note that applies to every mtb node: it logs [comfy_mtb] Some nodes (N) could not be loaded at startup rather than crashing outright when something fails to import, with a pointer to http://127.0.0.1:8188/mtb for the actual reason - a real, confirmed behavior from other users' install logs. Check that line first if Curve doesn't show up after installing the pack.