🚌 CR 8 Channel Out

This is the other end of the bus. CR 8 Channel In bundles up to eight connections into one PIPE_LINE; this node takes that pipe and unpacks it back into eight separate wires so you can plug them into whatever needs them. One tidy wire crosses your graph; here it fans back out.

It's part of Comfyroll Studio's bus system (Suzie1 / RockOfFire), the same organizational pattern as rgthree's Context nodes. No generation, no processing - it just splits the bundle apart again.

How it works

The pipe carries eight positional channels. This node reads the incoming PIPE_LINE and exposes each channel on its own output pin - ch1 through ch8, each typed * so it can hand back a model, a latent, a string, anything you packed in. Position is everything: whatever went into ch3 on the In node comes out of ch3 here.

It also re-emits the pipe itself on an output, which is the useful bit for chaining. You can unpack the channels you need at this point in the graph and pass the same bus along to another Channel Out node further downstream. The bus keeps flowing; you tap it wherever you need it.

The inputs that matter

• pipe - the PIPE_LINE to unpack, from a CR 8 Channel In (or an upstream Channel Out passing the bus through). This is the only input.

Outputs: the pipe passed through (so you can keep routing it), ch1–ch8 (your unpacked connections), and the show_help link. Wire each channel to its destination - the model channel to your sampler, the latent channel to the sampler's latent input, and so on.

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, then restart.

Pure plumbing, nothing to download.

Common issues

The channel map has to match the In node exactly. If you packed the VAE into ch4 upstream, unpack it from ch4 here - grabbing ch5 instead hands the wrong value to the wrong socket, and you'll get a type error somewhere downstream that doesn't obviously point back to the mismatch. A consistent, written-down channel convention across your whole graph is the fix.

Two more things. An empty channel comes out empty - if a slot wasn't filled on the In side, its output here is nothing, and plugging that into a required input errors out. And because the channels are untyped *, ComfyUI won't catch a crossed wire at connect time; the problem only shows up where the value is actually consumed, so trace from the crash back to which channel you tapped. If the node's missing from the menu, that's the Comfyroll pack failing to load, a pack-level issue rather than this node.