FromBasicPipe_v2

Impact Pack's "pipe" nodes exist to tame the spaghetti. A BASIC_PIPE bundles the five things almost every sampler needs - model, clip, vae, positive conditioning, negative conditioning - into a single wire, so you route one cable across your graph instead of five. FromBasicPipe_v2 is the node that unbundles it back into those five outputs. The _v2 twist: it also re-emits the pipe itself, so you get the parts and the intact bundle in one node.

That extra output sounds trivial and is genuinely handy. When you're using EditBasicPipe to swap, say, the model inside a pipe, it's convenient to unpack the pipe, look at or use the pieces, and still pass the whole pipe onward without threading a second wire around the unpack node. v2 saves you that routing.

How it works

It takes the BASIC_PIPE apart into its constituent members and hands each back as its native type, plus the original pipe untouched. Nothing is transformed - a pipe is just a tidy container, and this reverses the ToBasicPipe that packed it. The only difference from the original FromBasicPipe is that pass-through basic_pipe output; the five extracted members are identical. Use it as a drop-in whenever you'd reach for FromBasicPipe but also want the bundle to keep flowing.

The input and outputs

• basic_pipe (BASIC_PIPE, required) - the bundle to unpack. Only input.

Outputs: basic_pipe (the same bundle, passed straight through - the v2 addition), then the five members - model (MODEL), clip (CLIP), vae (VAE), positive (CONDITIONING), negative (CONDITIONING). Feed the members wherever they belong; carry the pass-through pipe onward to the next pipe-aware node.

How to install it

Comes with Impact Pack. ComfyUI Manager: search ComfyUI Impact Pack, Install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ltdrdata/ComfyUI-Impact-Pack

then pip install -r requirements.txt in ComfyUI's Python env (portable: python_embeded\python.exe -m pip ...), restart. Pack's by ltdrdata, the ComfyUI-Manager author - a safe, standard install. Pipe nodes need no models.

Common issues & troubleshooting

A BASIC_PIPE only accepts a basic pipe - don't confuse it with DETAILER_PIPE, which bundles more (the detailer's sampler settings on top of the basics) and has its own FromDetailerPipe / FromDetailerPipe_v2. Feed the wrong pipe type in and the socket won't connect. The pack also notes that if you have some other custom node's pipe that happens to share BASIC_PIPE's internal structure but isn't typed as one, there's an "Any PIPE → BasicPipe" converter for that - forcing an incompatible pipe through will throw runtime errors, so convert deliberately. Otherwise this node is about as safe as they come: it just unpacks and passes through, changing nothing about the values inside.