Ideogram 4 Quad Split

The whole point of the quad workflow is one render, four panels - but nobody wants to show up at a review with a single 2656×1504 image. Ideogram4QuadSplit is the cleanup step: it crops the four finished panels back out of the rendered canvas so each one can be saved, reviewed, or fed onward on its own.

What it does

You give it the rendered image and the same geometry the keyframe used - width, height, frame_width, frame_height, gutter, margin - and it returns five outputs:

• top_left, top_right, bottom_left, bottom_right - the four panels as individual images, each one ready for its own SaveImage
• all_frames - the same four stacked into a single batch, handy if you want to save them as one contact-sheet pass or run them through a batch processor

The mechanism is deliberately boring, which is the point. It computes each cell's top-left pixel with the same margin/gutter math as the keyframe node, crops, and hands them out in reading order. One detail worth knowing: it rescales the crop geometry to match the actual input image size, so if an upstream node resized the canvas, the crops still land in the right places rather than drifting off into the gutter.

What to wire

The image input is whatever comes out of your VAEDecode. The geometry inputs should come from the pack's Ideogram4QuadLayout node rather than being typed by hand - this node, the keyframe, and the keyframe release node all take the same six numbers, and shared ints are the only thing keeping them from drifting apart. If you didn't use Layout, just match the keyframe's values exactly.

Installing

Same as the whole pack:

cd ComfyUI/custom_nodes
git clone https://github.com/reality-comes/comfyui-ideogram4-quad-storyboard

Restart ComfyUI and it appears under image/ideogram4 (or search "Ideogram 4 Quad Storyboard" in ComfyUI Manager). No extra Python dependencies, no model downloads - the pack runs entirely on ComfyUI's bundled torch and comfy. The model you actually render with is Ideogram 4 (fp8 or nf4 checkpoint), which you load the usual way.

Where people get burned

Geometry mismatch is the one real trap. If the Split node's numbers don't match the keyframe's, your crops will be off by the difference - a shifted margin means panels that are a few pixels too small or that clip a neighbor's edge. The all_frames output only stacks the panels when all four crops share an identical shape, which they always do if the geometry matches; if it ever doesn't, that output falls back to a single frame so the workflow still runs instead of erroring.

Other than that, this is the rare node that just works. It's the "collect the result" half of the storyboard, and there's not much to configure beyond feeding it the right numbers.