EasyUse/Pipegenerated
Pipe Out(pipeOut)
The Pipe Out node unpacks a PIPE_LINE object into its individual components while also passing the original pipe through unchanged.
pipe Out
pipe
pipe
model
pos
neg
latent
vae
clip
image
seed
Easy Use
The Pipe Out node unpacks a PIPE_LINE object into its individual components while also passing the original pipe through unchanged. It is the counterpart to the EasyUse pipe-packing nodes: feed in a pipe and get back the model, conditionings, latent, VAE, CLIP, image, and integer value individually so they can be connected to ordinary nodes.
Inputs
pipe
PIPE_LINE required. Any pipe created by an EasyUse pipe node. Pipe Out reads the components from this pipeline object and exposes them as separate outputs.
Outputs
Outputs are returned in the order below.
- pipe (
PIPE_LINE): The unchanged input pipe. This lets you continue the pipe to other pipe-aware nodes while also unpacking it. - model (
MODEL): The model stored in the pipe. - positive (
CONDITIONING): The first conditioning stored in the pipe, normally the positive/guiding conditioning. - negative (
CONDITIONING): The second conditioning stored in the pipe, normally the negative conditioning. - latent (
LATENT): The latent image or latent samples stored in the pipe. - vae (
VAE): The VAE stored in the pipe. - clip (
CLIP): The CLIP model stored in the pipe. - image (
IMAGE): The image tensor stored in the pipe. - batch_size (
INT): The integer batch size carried by the pipe. If no batch size was stored, this is typically1.
Usage Notes
- Because the original pipe is passed through as the first output, you can wire a single Pipe Out into both pipe-aware nodes and ordinary node inputs without losing the pipeline.
- The two
CONDITIONINGoutputs follow the standard order used by samplers: positive, then negative. - Pipe Out only exposes the contents of the pipe; it does not transform them. The pipe output is the same object as the input pipe, and the extracted outputs are references to the components stored inside it.
Comments
Sign in with GitHub to join the discussion.