Curve From String

Here's the honest pitch: the whole point of ComfyUI-Keyframed is to escape keyframe notation - the 0:(1), 16:(0.5) string soup that Deforum and FizzNodes made you write. And then this node lets you paste that exact notation back in. Which sounds like a betrayal of the pack's philosophy and is actually one of its smartest moves, because it's a bridge for people who already have schedules.

If you've been doing Deforum or A1111 animation and you have a hard-won curve written in that syntax, you don't want to rebuild it node by node. You want to paste it, verify it draws the way you expect, and carry on. That's this node: chigozie_string in, KEYFRAMED_CURVE out.

How it works

The string is parsed by curve_from_cn_string from the keyframed library's DSL - the same "Chigozie notation" the pack's README points at (see chigozie.co.uk/keyframe-string-generator, which is a handy web tool for writing these by eye). The syntax is time:(value) pairs separated by commas:

0:(1), 10:(0.5), 20:(0.25)

Interpolation methods can be tacked on per keyframe - Deforum-style entries like 0:(1.0). with easing suffixes work too, because the parser handles the notation that ecosystem already speaks. The output is a real keyframed Curve, which means you can immediately do curve arithmetic on it, plot it, or feed it into a Parameter Group alongside curves you built visually.

The input

• chigozie_string (required, multiline) - the curve notation. The default is 0:(1), a single keyframe at time 0 with value 1, which is a fine sanity check.

The output

KEYFRAMED_CURVE - same type every curve node in this pack emits, so it plugs into the operators, Apply Curve to Conditioning, and the drawing nodes without friction.

How to install it

Standard pack install: ComfyUI Manager → search ComfyUI-Keyframed, or

cd ComfyUI/custom_nodes
git clone https://github.com/dmarx/ComfyUI-Keyframed

then restart ComfyUI. No models, no heavy downloads - just the keyframed library (plus toolz), auto-installed on import if missing.

Troubleshooting

The failure mode is a parse error on your string, and the pack will tell you - you'll get a traceback naming the offending pair rather than a silent wrong curve, which is more than some DSL parsers give you. Watch out for a subtle one: if your string evaluates to a curve but the plot looks wrong, check that the easing suffix on a keyframe is one the parser recognizes. And since curve arithmetic operates on the union of keyframes, a curve built from a dense string can produce unexpectedly busy results when you multiply it with a sparser visual curve - worth remembering before you wonder why your weights are jagged.