Pipe In 12CH
The deprecated bundler — why it exists and what replaced it
- pipe
- any_1
- any_2
- any_3
- any_4
- any_5
- any_6
- any_7
- any_8
- any_9
- any_10
- any_11
- any_12
- pipe
Pipe In 12CH is the one-way predecessor of Pipe 12CH Any: it gathers up to twelve values of any type onto a single pipe, and that's it - one pipe out, no splitting. It's flagged DEPRECATED in the pack, and the honest headline is that you probably want Pipe 12CH Any instead. But if you've loaded an older workflow that uses this node, here's what it's doing and why it got replaced.
Mechanically it's simple: twelve optional any_1 through any_12 inputs, each accepting anything, plus an optional incoming pipe. Whatever's wired in gets merged onto the outgoing pipe; if an input isn't connected, the node carries over the corresponding value from the incoming pipe's context, so it can chain rather than always starting from scratch. That's the standard rgthree-style context pattern, and it's a perfectly good "bundle it up" tool. In its day, this was how you took a spread-out workflow's loose values and condensed them into one fat wire to route across the canvas.
So why is it deprecated? Because the pack later shipped Pipe 12CH Any, which does everything this node does and re-exposes every channel as an output - it bundles and splits, in both directions, in one node. Once you have that, a one-way bundler with no way to pull the values back out is strictly less useful; you'd need a matching splitter node (or a pass through the whole chain) to recover the values. The author's own pack marks it DEPRECATED, and the newer Pipe 12CH Any lives in the active Pipe category for exactly that reason. If you're building a workflow today, skip this node. If you're maintaining a saved one, leave it in place - it still runs - and only swap to Pipe 12CH Any when you're doing a real edit.
What's on it
pipe(optional) - an incoming context to chain from.any_1…any_12(optional, any type) - the values to bundle.- Output: a single
pipe.
Note the underscore in the input names (any_1) - cosmetic, but worth knowing so you can tell the two nodes apart at a glance.
Install
From ComfyUI-RvTools_v2. ComfyUI Manager → search "ComfyUI-RvTools_v2" → install, restart. Or:
cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI-RvTools_v2
Under RvTools II / DEPRECATED. No model downloads; standard pip deps.
Caveats
Beyond the deprecation, two things. The pipe type is the rgthree-style context type - it won't connect to Comfyroll's PIPE_LINE or other pipe-likes. And the whole pack is superseded by ComfyUI_Eclipse, so both this node and its replacement are frozen here. If you're new, use Pipe 12CH Any; if you're fixing an old workflow that references RvTools v1, remember that repo was pulled from GitHub and the v2 rename is what makes these nodes resolve.
Inputs (13)
| Name | Type | Default | Description |
|---|---|---|---|
| pipeopt | pipe | — | |
| any_1opt | * | — | |
| any_2opt | * | — | |
| any_3opt | * | — | |
| any_4opt | * | — | |
| any_5opt | * | — | |
| any_6opt | * | — | |
| any_7opt | * | — | |
| any_8opt | * | — | |
| any_9opt | * | — | |
| any_10opt | * | — | |
| any_11opt | * | — | |
| any_12opt | * | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| pipe | pipe | — |