Manual Feature Pipe ⚡🅡🅞🅣🅘

This one's front matter lists its category as plain sd rather than the pack's usual RyanOnTheInside/... path - an odd label to notice if you go digging through the node browser looking for it, but not something that affects how it behaves. Functionally it still belongs squarely with the pack's other FlexFeatures Manual-source nodes.

This node does one small thing: it bundles a frame rate, frame count, and width/height into a single FEATURE_PIPE value. On its own that's not very exciting - the pack's own description of it is refreshingly blunt: "Create a feature pipe with the specified frame rate, frame count, width, and height. Probably want to use this with manual feature." That's the author telling you exactly how it's meant to be used, hedge word included.

Why you'd reach for it (and when you probably shouldn't)

The point of a separate pipe node is consistency across multiple feature sources. If you're building several manual feature curves that all need to describe the same sequence - same frame rate, same frame count, same resolution - defining those dimensions once in a ManualFeaturePipe and feeding that pipe into several ManualFeatureFromPipe nodes keeps them in sync. Change the frame count in one place and every curve derived from that pipe updates with it, instead of you hunting down and editing four separate nodes by hand.

If you only need one manual curve, though, skip this node entirely. The pack's ManualFeatureNode bundles the same frame rate/count/width/height fields directly, no separate pipe required - it's the simpler, self-contained option, and per the author's own hint above, this pipe node exists specifically to pair with a downstream feature node rather than to stand alone.

The inputs and output

• frame_rate (default 30, minimum 1) - the timeline's frame rate.
• frame_count (default 100, minimum 1) - total frame length.
• width / height (default 1920 / 1080, minimum 1) - the pipe's associated resolution.

Output is a single FEATURE_PIPE - feed it into ManualFeatureFromPipe (or any other pack node that accepts a FEATURE_PIPE) rather than a direct effect input; on its own it produces no visible or numeric result.

How to install it

The README came back empty when I checked for install-specific notes, so use the standard path for the pack:

ComfyUI Manager: search "RyanOnTheInside", install, restart.

Manual:

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

Restart ComfyUI afterward.

Troubleshooting

If you wire this in and nothing downstream seems to react, that's expected on its own - a FEATURE_PIPE isn't a feature curve, it's just the shared dimensions one is built against. You need a node like ManualFeatureFromPipe consuming it to actually get keyframed values out. And if you find yourself only ever feeding this into a single downstream feature node, you've built more graph than you need - swap both nodes out for a standalone ManualFeatureNode and simplify. If you're hunting for this node in the ComfyUI node browser and it's not where you expect, search by its display name rather than trying to guess the category it's filed under - that sd category label above is a good example of why searching beats browsing in this pack.