✈️ CR Module Input

The read side of Comfyroll's "module pipe" pattern: hand it a PIPE_LINE (built upstream by CR Module Pipe Loader) and it unpacks that single bundled wire back out into its individual pieces - model, positive and negative conditioning, latent, VAE, CLIP, ControlNet, image, and seed - nine separate outputs from one input wire. It also re-outputs the original pipe unchanged, so you can tap a value mid-graph without breaking the chain for whatever comes after.

How it works

This is the same idea as CR Image Pipe In/Out - Comfyroll's other, smaller pipe pair, scoped to just image/width/height/scale - applied to a much bigger bundle: the full set of things a typical sampling graph juggles at once. Comfyroll credits Efficiency Nodes and tinyterra's pipe nodes directly in its own README as the inspiration for this pattern, and it's the same underlying problem rgthree's Context nodes solve today: once a workflow has more than a handful of stages, running nine separate wires (model, conditioning ×2, latent, vae, clip, controlnet, image, seed) in parallel across the same physical distance makes the graph far harder to read than one wire carrying all nine.

You'd typically drop a CR Module Input node wherever you need to actually use one or more of those values - say, right before a KSampler that needs model, pos, neg, and latent - while leaving the pipe output free to keep traveling to whatever's further downstream.

Inputs and outputs that matter

• pipe - the only input, type PIPE_LINE.
• Outputs: pipe (passed through unchanged), model, pos, neg, latent, vae, clip, controlnet, image, seed, and show_help - eleven outputs from one input.

How to install it

ComfyUI Manager: search "Comfyroll Studio", install, restart. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git, restart. Pure graph plumbing - nothing to download.

Common issues

PIPE_LINE is a Comfyroll-specific type - it only connects to other Comfyroll pipe nodes, not to a generic ComfyUI socket, so you can't shortcut around building the pipe with CR Module Pipe Loader first. That's by design, not a bug.

If a value you expect out of this node is empty or default (an image socket producing nothing, a seed sitting at 0), check whether that field was actually set upstream when the pipe was built - this node only unpacks what was packed in; it can't produce a value that was never loaded into the pipe in the first place.

And as with every node in this pack: if CR Module Input doesn't show up in your search at all, that's the shared Comfyroll registration file failing somewhere else - check your ComfyUI startup console for an import error before assuming this node specifically is broken.