SP_Pipe_ToBasicPipe

This is a one-job node, and the job is right there in the name: it takes SP-Nodes' own pipe type and turns it into Impact Pack's pipe type. If you don't run Impact Pack, you don't need this node - skip straight to the plain SP_Pipe article instead.

What it does and why it exists

SP_Pipe (SP-Nodes' bus node for bundling model, clip, vae, conditioning, latent and image into one wire) uses its own SP_PIPE type. Impact Pack - the FaceDetailer, wildcards, and detect-crop-refine pack that's close to a standard install in the ComfyUI ecosystem - has its own bundle type, basic_pipe, and a lot of its nodes expect input in that exact shape. The two types aren't interchangeable; ComfyUI's type system won't let you plug an SP_PIPE wire straight into a basic_pipe input even though they're carrying the same five things underneath.

SP_Pipe_ToBasicPipe closes that gap. It takes one required input, sp_pipe, and produces one output, basic_pipe. Wire your SP_Pipe bundle in, and what comes out is exactly the format FaceDetailer and friends want. No manual re-wiring of five separate connections, no losing track of which VAE or conditioning was supposed to go where.

How you'd actually use it

The typical shape: build your generation graph with SP_Pipe carrying model/clip/vae/positive/negative/latent through the early stages, run this converter node once right before you hand off to an Impact Pack detailer, and connect the basic_pipe output straight into whatever Impact Pack node is asking for one. It's a single-purpose adapter, so there's really only the one thing to configure - plug in sp_pipe, take basic_pipe out.

Installing it

Two things to install, not one, since this node is a bridge between two packs:

1. SP-Nodes itself - via ComfyUI Manager (search "SP-Nodes") or cd ComfyUI/custom_nodes && git clone https://github.com/bananasss00/ComfyUI-SP-Nodes, then restart.
2. Impact Pack - if you don't already have it, install ComfyUI-Impact-Pack the same way (Manager search, or clone). This node's output is only useful once you have something downstream that consumes basic_pipe, and that's Impact Pack's job, not SP-Nodes'.

Note that Impact Pack's YOLO-based detectors (the ones FaceDetailer typically pairs with) live in a separately-installed Impact Subpack as of Impact Pack v8.0 - worth knowing if you install Impact Pack and don't see a detector model in a dropdown where you expected one, though that's an Impact Pack detail rather than anything SP_Pipe_ToBasicPipe itself needs.

Troubleshooting

If the basic_pipe output isn't accepted somewhere you expect it to be, check the Impact Pack version you're on - basic_pipe is a stable, long-standing type in that pack, so a mismatch here is far more likely to be a missing Impact Pack install than a version incompatibility. And remember this node only converts the container: if your SP_Pipe was missing one of the five fields Impact Pack expects (say you never wired in a VAE upstream), that gap carries straight through to the basic_pipe output - SP_Pipe_ToBasicPipe doesn't fill in anything for you, it just repackages what you gave it. Trace back to the SP_Pipe node feeding it if a downstream Impact Pack node complains about a missing piece.