Pipe Out 12CH

Pipe Out 12CH is the twelve-slot version of Pipe Out 8CH: one pipe in, a pass-through pipe plus twelve any_1…any_12 outputs out. It exists for the same reason all the RvTools pipe nodes exist - to bundle a pile of unrelated values into one wire on the way into a group and split them back out where they're actually consumed. If eight slots weren't enough, this is the grown-up version.

There's not much mechanism to explain, because there isn't much mechanism. The execute unpacks the incoming tuple positionally - any_1, any_2, …, any_12 = pipe - and hands every slot to its own output while forwarding the original pipe. All twelve outputs are *-typed, so anything rides along: models, images, ints, strings, whatever. The slots aren't named or typed, which is the trade-off for flexibility: the pipe is just an ordered list, so the order is the entire contract between the In side and this Out side.

Install. ComfyUI Manager → "Install Custom Nodes" → search "RvTools" → install ComfyUI-RvTools_v2 and restart. Or:

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

No models, no keys. If cloning manually, pip install -r requirements.txt (opencv-python, pynvml, piexif, Pillow, pilgram) before restarting.

The catches. Three, and they're all worth having in your head before you drop this into a shared workflow. First, the twelve-slot layout has to match whatever produced the pipe - same positional slot order, same number of slots. Feed it a pipe with a different length and execute will throw an unpacking error right on the canvas; ComfyUI will give you a red node and the stack trace will say something about "too many values to unpack." Second, everything is *-typed, so you get zero type safety - swap two slots upstream and your image silently becomes your batch size. Third, it's flagged DEPRECATED, and the pack README says the whole RvTools v2 set has been superseded by ComfyUI_Eclipse. It still loads and runs in existing workflows, but if you're building something new, Eclipse is where the author moved the action.

Also be aware the community's shared RvTools workflows historically break on install because the old v1 repo was deleted - nodes that show up as plain "RvTools" without the [RvTools] suffix are from that dead lineage and Manager can't fetch them anymore. This v2 pack is the one that survives.