Nodes/Light-x02 Nodes/🔗 Pipe 40CH Any
ComfyUI Node

🔗 Pipe 40CH Any

Forty channels on one wire — the pack's maximum pipe

By Light-x02·Created 11 months ago·Updated 9 months ago· 11
🔗 Pipe 40CH Any
  • pipe
  • any1
  • any2
  • any3
  • any4
  • any5
  • any6
  • any7
  • any8
  • any9
  • any10
  • any11
  • any12
  • any13
  • any14
  • any15
  • any16
  • any17
  • any18
  • any19
  • any20
  • any21
  • any22
  • any23
  • any24
  • any25
  • any26
  • any27
  • any28
  • any29
  • any30
  • any31
  • any32
  • any33
  • any34
  • any35
  • any36
  • any37
  • any38
  • any39
  • any40
  • pipe
  • any1
  • any2
  • any3
  • any4
  • any5
  • any6
  • any7
  • any8
  • any9
  • any10
  • any11
  • any12
  • any13
  • any14
  • any15
  • any16
  • any17
  • any18
  • any19
  • any20
  • any21
  • any22
  • any23
  • any24
  • any25
  • any26
  • any27
  • any28
  • any29
  • any30
  • any31
  • any32
  • any33
  • any34
  • any35
  • any36
  • any37
  • any38
  • any39
  • any40

The 🔗 Pipe 40CH Any is the top of the pack's fixed-channel pipe ladder: one pipe in/out plus 40 any channels. It's the "if you need this, you know who you are" node - for the rare workflow where a genuinely huge bundle of signals has to travel as a single wire.

How it works

Identical mechanics to the 5/10/20/30-channel siblings, just more slots. All 40 channels are * wildcard type, so anything flows through - IMAGE, LATENT, MODEL, MASK, CONDITIONING, STRING, VAE. The pipe input/output carries the bundle, unconnected channels inherit the upstream pipe's value, and downstream Pipe nodes pull the matching channels back out. The code is modeled on rgthree's context-utils pattern, so it interoperates cleanly with the same context-style ecosystem.

When does 40 make sense?

Honestly, rarely - this is the "Subgraph boundary for a monster workflow" or "batch pipeline with dozens of tracked intermediates" case. If you're running multi-model setups (several CLIPs, several control paths, per-stage latents, metadata strings, seeds) and crossing a Subgraph boundary, one 40-channel wire beats 40 dangling ports, and the fixed layout keeps slot N meaningful forever in a template.

But be honest with yourself about why you're here. If you've got 25 used channels and 15 empty ones, the empty slots flow through as None and can cause confusing downstream failures when something reads one by mistake. If you're using all 40 for real, ask whether the graph would be clearer as a few smaller bundles - this node is a legitimate tool, not a badge of honor.

Inputs and outputs

  • pipe (optional in/out) - the bundle to extend or forward.
  • any1 … any40 (optional) - values to inject or read out; each mirrors to its matching output.

Install

Ships in Light-x02 Nodes - ComfyUI Manager → search "ComfyUI-Lightx02-Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/Light-x02/ComfyUI-Lightx02-Nodes

Restart ComfyUI, find it under 💡Lightx02/Pipes. No extra dependencies or downloads. If you have older standalone Light-x02 node repos installed, remove them from custom_nodes before installing this pack to avoid duplicate-registration errors on startup.

Category💡Lightx02/Pipes

Inputs (41)

NameTypeDefaultDescription
pipeoptpipe
any1opt*
any2opt*
any3opt*
any4opt*
any5opt*
any6opt*
any7opt*
any8opt*
any9opt*
any10opt*
any11opt*
any12opt*
any13opt*
any14opt*
any15opt*
any16opt*
any17opt*
any18opt*
any19opt*
any20opt*
any21opt*
any22opt*
any23opt*
any24opt*
any25opt*
any26opt*
any27opt*
any28opt*
any29opt*
any30opt*
any31opt*
any32opt*
any33opt*
any34opt*
any35opt*
any36opt*
any37opt*
any38opt*
any39opt*
any40opt*

Outputs (41)

NameTypeDescription
pipepipe
any1*
any2*
any3*
any4*
any5*
any6*
any7*
any8*
any9*
any10*
any11*
any12*
any13*
any14*
any15*
any16*
any17*
any18*
any19*
any20*
any21*
any22*
any23*
any24*
any25*
any26*
any27*
any28*
any29*
any30*
any31*
any32*
any33*
any34*
any35*
any36*
any37*
any38*
any39*
any40*