LC Pipe Out

Pipes are great until you need an actual value. You've threaded an LC_PIPE across the whole graph, and now the sampler needs a model, a conditioning, a seed, a denoise - real sockets, not a bundle. LC Pipe Out is the other end of the pattern: it takes one LC_PIPE in and fans it out to every individual socket it can carry, top to bottom, in the exact order the pack's pipe builders define. It's the decoder for the bus.

How it works

One required input, pipe (from LC Pipe Edit, a sampler-configure pipe, or a KJ Get). The outputs are the full slot list, in order: pipe (passed through, so you can chain another Get/Set or Pipe Out after it), then Model 1, Clip 1, VAE 1, Model 2, Clip 2, VAE 2, Image, Mask, Width, Height, Latent, Batch, Positive prompt, Positive conditioning, Negative prompt, Negative conditioning, Seed, total_steps, cfg_1, denoise, step_swap, cfg_2, sampler_name, scheduler, and detailer_steps. The pipe passthrough is the detail that makes chaining possible - you can unpack, grab one value, and keep the bundle flowing.

Any slot that wasn't packed comes out empty (None) rather than erroring, so a pipe with only models and a prompt still unpacks cleanly; you just wire what you need.

Why the order matters

The outputs are fixed top-to-bottom to match the builders - LC Pipe Edit and the sampler-configure pipes all pack in the same slot order, and LC Pipe Out unpacks in that same order. That consistency is the whole contract. It also means the socket labels match what the pipe's tooltips promised, so a pipe packed as "positive conditioning" at slot 14 unpacks at the same spot. No surprises, as long as you use the pack's pipe family end to end.

What you'll actually use it for

• Feeding the sampler - unpack at the end of the pipe chain and wire Model 1, positive/negative, seed, and sampler settings straight into a KSampler or the pack's LC Sampler Configure.
• Interop with KJ Get/Set - the pack positions these pipes as Get/Set friendly, so you can grab one slot (say, seed) with a KJ Get node mid-pipeline and edit it with a KJ Set without unpacking everything.
• Editing one value - unpack → change → re-pack through LC Pipe Edit is the explicit edit path if you prefer sockets to pipe surgery.

Install

Part of ComfyUI LC123 Nodes (MIT, 89 nodes). ComfyUI Manager → search "ComfyUI LC123 Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/lonecatone23/ComfyUI_LC123_nodes

Restart. No extra dependencies. On hosted platforms like RunningHub, request the pack and they install it for you.

The honest caveat

The type system treats LC_PIPE as a single opaque type, so nothing checks that the pipe you're unpacking actually contains a model - you'll find out at the sampler. And like every pipe family, this one doesn't interoperate with rgthree Context or another suite's pipe; commit to LC_PIPE and use it consistently, or you'll be unpacking a bundle that isn't there.