Pipe Out 8CH

Pipe Out 8CH is the read side of the RvTools 8-slot pipe bus, and it does exactly one thing: it takes a pipe in and unpacks it into eight individually typed outputs (any_1…any_8), passing the original pipe through unchanged on its own output too. You pair it with Pipe In 8CH on the far side of a group, and suddenly a cluster of nodes that accepts eight scattered inputs only crosses your graph as one wire.

It's the kind of node that looks pointless until you have a group with half a dozen loose ends. Instead of dragging wires across the whole canvas, you gather everything into a bus on one side and split it back out right where it's needed. That's the same thinking behind rgthree's context nodes - bundle a bunch of data into one connection to keep a large graph readable - just with a bare *-typed slot for everything instead of a named context dict.

Install. ComfyUI Manager → search "RvTools" → install ComfyUI-RvTools_v2, or clone it:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI-RvTools_v2
# restart ComfyUI afterwards

It's a utility node with no models or keys. Manual installs should pip install -r requirements.txt from the repo (it needs opencv-python, pynvml, piexif, Pillow, pilgram) before restarting.

The catches. The bus is positional, so Pipe Out 8CH expects the incoming tuple to have its eight slots in the same order Pipe In 8CH wrote them. Mismatched slot order is the classic silent failure - the node won't error, your data just lands in the wrong outputs. The output types are all *, so there's no type safety to catch you; if a value lands in the wrong slot, it's on you. The code also flags this node DEPRECATED, and the pack README says RvTools v2 is superseded by ComfyUI_Eclipse, which carries most of these nodes forward. It still runs fine - plenty of shipped workflows use these - but treat it as legacy plumbing, not something to build a new workflow on.

One more thing worth knowing: if the pipe that arrives has fewer than eight slots (say you fed it from a different pack's pipe node with a different layout), the unpack will throw. RvTools pipes and other packs' pipes are not interchangeable just because they're both typed "pipe" - this node specifically expects the 8-slot RvTools layout. If you inherited a workflow with these, it works out of the box; if you're improvising, make sure the pipe was built by the matching RvTools Pipe In.