🚌 CR Data Bus Out

Big ComfyUI workflows turn into spaghetti - a model wire, a VAE wire, a couple of conditionings all snaking across the canvas to some node three screens away. The "bus" pattern fixes that: you bundle several wires into one fat cable, run that single cable to wherever it's needed, and unpack it there. CR Data Bus Out is the unpack end. Its partner, CR Data Bus In, is where you load the cable up.

This is the same organizational idea rgthree's Context nodes are famous for - carry a bundle of connections down one wire so a workflow you can't read becomes one you can. Comfyroll's bus is the pipe-based flavor of it.

How it works

The bus is a PIPE_LINE - an opaque cable carrying up to four slots of arbitrary data. You feed the pipe into CR Data Bus Out and it splits back out into the individual values you packed in, in order. It also re-emits the pipe unchanged, so you can chain another Data Bus Out further along and tap the same cable at multiple points. Nothing is computed; it's pure routing, the whole value being cleaner graphs.

The inputs and outputs that matter

• pipe (PIPE_LINE) - the bus cable, from a CR Data Bus In or an upstream Data Bus Out.

Outputs:

• pipe (PIPE_LINE) - the same bus passed through, so you can keep chaining.
• any1 through any4 - the four unpacked slots, each a wildcard type. Wire each to whatever it actually is (model, VAE, conditioning, an int, whatever you loaded into that slot upstream).
• show_help - the wiki-link string, ignore it.

Installing it

Comfyroll Studio (Suzie1 / RockOfFire) is a large, established utility pack. Via ComfyUI Manager: search "Comfyroll Studio," install, restart. Or clone it:

cd ComfyUI/custom_nodes
git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git

then restart. No models, no dependencies.

Common issues

The thing to keep straight is slot order and type. The bus is untyped (any), so whatever you put into slot 2 at the In end comes out of any2 here - the node won't warn you if you wire the wrong output into the wrong consumer. Keep a mental (or note-node) map of which slot carries what, or you'll spend ten minutes wondering why your "VAE" is a conditioning.

Because outputs are wildcards, a mismatched connection fails downstream, not here, which makes the error message point at the wrong node. When a bus workflow breaks, check the In/Out slot assignments first. And if the whole pack won't load at startup with a traceback, that's an install issue - reinstall cleanly through Manager and restart.