Animated Feature Preview ⚡🅡🅞🅣🅘

Once you've built a FlexFeature curve - say, an audio-reactive signal you're about to use to drive a ControlNet strength over an animation - you generally have no idea what it actually looks like until it's already driving something and you're staring at the output trying to work out why it doesn't spike where the kick drum hits. This node closes that loop: it renders the curve itself as an image, before it touches anything downstream.

Part of ryanontheinside's FlexFeatures preview tools, built to sit between "I made a feature" and "I trust this feature."

How it works

It plots the FEATURE as a scrolling line graph inside a sliding window, so long sequences don't get squashed into an unreadable line - you see a chunk of it at a time, moving.

The inputs and outputs that matter

• feature - the FEATURE you want to inspect.
• window_size - default 60 frames. How much of the curve is visible at once; this is a viewing window, not the total length, so a longer feature scrolls past rather than compressing to fit.
• top_label / bottom_label - default "Max"/"Min", labeling the graph's vertical extremes.
• width / height - output image size, defaulting to 960×540.
• low_color / high_color - RGB tuples as literal strings, e.g. (255,100,100) for low values and (100,255,100) for high - a simple gradient across the curve's value range.
• title_override - set a custom title if the default isn't descriptive enough.

Output is a plain IMAGE - feed it into any Preview Image or Save Image node like you would anything else.

How to install it

Via ComfyUI Manager, search RyanOnTheInside. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ryanontheinside/ComfyUI_RyanOnTheInside

then restart. No model downloads - this is a rendering utility on data you've already generated.

Common issues & troubleshooting

Color field errors. low_color/high_color are literal string tuples, not a color picker - get the parentheses or commas wrong and you'll hit an error rather than the node quietly ignoring it. Copy the default format exactly if you're editing them.

"Why did the graph scroll past the part I care about." window_size controls a moving viewport, not the whole feature - if you need to see the full curve at once rather than a sliding chunk, increase window_size past the feature's total frame count.

Blank or flat-looking graph. Check that feature is actually connected and that the upstream node producing it (an AreaFeatureNode, a combiner, or similar) has real variation in it - a genuinely flat feature will render as a flat line, which is correct behavior, not a bug in this node.