LC Aspect Ratio Pipe (In/Edit)

Pipes exist to kill the noodle plate. Instead of dragging image, mask, width, height, latent, and a batch count across the graph as six separate wires, an LC_PIPE bundles them into one line, and each downstream node pulls off what it needs. That's the pattern the plumbing layer calls a context bus, and LC Aspect Ratio Pipe is the "pull off" end for the aspect-ratio half of it.

It's dead simple - one required input, the pipe (an LC_PIPE), and eight outputs. It takes whatever the Aspect Ratio Simplifier (pipe) or the pack's LC Pipe built, unpacks the aspect fields, and hands you image, mask, width, height, latent, batch, and resolution as individual sockets. And critically, it also passes the pipe through on its own output, so you can chain Get/Set nodes along the same line without the pipe dying at the first unpack. That's the "for further Get/Set chaining" in the description - a Get node that consumed its pipe would make it impossible to read two different fields off the same bundle, so every Get in this family re-emits the pipe.

The one thing to keep in mind is the stale-context trap that every pipe system shares. Because the bundle carries a snapshot, it's easy to pull image or width off a pipe that was assembled before something downstream replaced the actual values. The single wire that made the graph readable also hides which version of each value is inside it. In practice: if a node upstream of your unpack - an upscaler, a crop - changes the image after the pipe was built, the pipe still holds the old one. Read the pipe as close to the node that built it as you can, or rebuild it after a transform.

The tip field on the input tells you exactly what feeds it: "Pipe from LC Aspect Ratio Simplifier 📐(Pipe) or LC Pipe." So the typical pairing is the pipe-output version of the Aspect Ratio Simplifier upstream (it builds the bundle at the same time it resizes), and this node wherever you need the numbers as plain wires - a text overlay, a conditioning prep, a logging node. If you only need one field, you might be able to skip this entirely; but the moment you need three of the eight, the unpack pays for itself.

It's a tiny node with a narrow job, and that's fine - the whole category exists so you can decide, per graph, whether wires or a pipe are more legible. For big workflows the pipe wins; for a five-node test graph, just wire the raw outputs and skip the plumbing.

Install is the usual LC123 clone:

cd ComfyUI/custom_nodes
git clone https://github.com/lonecatone23/ComfyUI_LC123_nodes

Restart, no pip deps. And if you don't need the pipe output to continue, the plain unpack still re-emits it - there's no mode where the pipe disappears, so you can't accidentally break a downstream Get by unpacking too early.