🪢 Pipe Out

This is the other half of Pipe In. Pipe In bundles model/clip/positive/negative/vae/latent/image/mask into one PIPEIN cable so a busy graph has one wire crossing it instead of eight. Pipe Out is how you get one specific value back out of that bundle at the point in your graph where you actually need it.

Why a single-value unpacker, separate from Pipe Out All

The pack also ships Pipe Out All, which unpacks everything in the bundle at once into nine separate output sockets. Pipe Out is the leaner version of that: you pick exactly one type from a dropdown, and you get exactly one output. That matters because ComfyUI charges you a little visual clutter for every output socket a node exposes, even the ones you don't use - if a given point in your workflow only needs the latent back out of the bundle, wiring up all nine of Pipe Out All's sockets just to use one of them is more mess on the canvas than the Pipe In/Out pattern was supposed to solve in the first place. Drop a Pipe Out wherever you need a single piece back, and keep Pipe Out All for the points where you genuinely need everything at once.

The inputs and outputs that matter

• pipe_in - the PIPEIN bundle, wired from an upstream Pipe In node.
• type - which value to pull out: model, clip, positive, negative, vae, latent, image, mask, or any.

One output, pipe-out, typed * - it takes on whatever type you selected. Wire it into whatever downstream input expects that value; ComfyUI resolves the wildcard type at connection time.

Installing it

ComfyUI Manager: search SDVN_Comfy_node, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/StableDiffusionVN/SDVN_Comfy_node

Then pip install -r custom_nodes/SDVN_Comfy_node/requirements.txt from your ComfyUI root, and restart. Pure plumbing - nothing to download.

Where people get burned

Pulling a type that was never bundled. Pipe In only carries what you actually wired into it - leave latent unconnected upstream and picking type: latent here gets you an empty/None result, not an error that tells you why. If a downstream node is complaining about a missing input, check the Pipe In end of the cable before assuming Pipe Out is broken.

One Pipe Out, one value. Each instance of this node only unpacks the single type you've selected in type - it's not a fan-out node. Need three different values out of the same bundle at three different points in the graph? That's three separate Pipe Out nodes (or one Pipe Out All), not one Pipe Out reused.

It's cosmetic, same as Pipe In. Nothing about bundling and unbundling changes your actual generation - it's the same data, just routed through fewer visible wires. If a workflow produces the wrong result, the bug is somewhere else; Pipe Out only affects how tidy the graph looks.