FromBasicPipe

A BASIC_PIPE is Impact Pack's way of shoving the five things almost every sampler needs - model, clip, vae, positive conditioning, negative conditioning - into one wire, so you're not dragging five separate cables across your graph. FromBasicPipe is the node that reverses that: feed it a pipe, get the five pieces back out as their native types, ready to plug into whatever downstream node actually wants a bare MODEL or CONDITIONING instead of a bundle.

You reach for it any time something in your graph isn't pipe-aware - a node that predates Impact Pack's pipe convention, or one from a completely different pack that just wants a plain MODEL input.

How it works

There's nothing transformative happening - a pipe is just a tidy container, and this simply reverses whatever built it (ToBasicPipe, or any node that outputs a BASIC_PIPE). It reads the five members out and hands each back unchanged.

The input and outputs

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

Five outputs, each unpacked directly: model (MODEL), clip (CLIP), vae (VAE), positive (CONDITIONING), negative (CONDITIONING).

How to install it

Ships with the 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. No models needed - pure unpacking.

Common issues & troubleshooting

Type mismatch feeding the pipe in. This node only accepts a genuine BASIC_PIPE. A DETAILER_PIPE (which carries more - detector, hook, wildcard) won't connect here directly; use DetailerPipe -> BasicPipe first if you're starting from a detailer pipe, or FromDetailerPipe if you want the detailer pipe's pieces unpacked directly without going through a basic pipe at all.

You also want the pipe to keep flowing downstream. This node only outputs the five unpacked members - the pipe itself is consumed. If you need both the individual pieces and the intact bundle continuing on (say, because EditBasicPipe further down needs the whole pipe while an earlier node needs just the model), use FromBasicPipe_v2 instead - same unpacking, plus a pass-through basic_pipe output.

A custom node's pipe won't connect even though it "looks like" a basic pipe. If it's not actually typed as BASIC_PIPE, ComfyUI's type checker will refuse the connection regardless of internal similarity. The pack ships an "Any PIPE -> BasicPipe" converter for exactly this case - forcing an incompatible type through without it risks a runtime error rather than a clean refusal.