Dynamic Image Batch(Eclipse-TJ)

Dynamic Image Batch (Eclipse-TJ) is the metadata-aware cousin of Dynamic Image Batch. Same idea - collect several IMAGE inputs into one batch - but each image slot now carries a paired files_N input, and the node tracks the original file paths alongside the pixels. If your workflow came from the Eclipse ecosystem, where file paths travel with images so you can save results back to their source folders, this is the batch node that doesn't destroy that linkage.

What "Eclipse" buys you

Plain batch nodes concatenate tensors and forget where anything came from. Eclipse-style workflows are built around metadata preservation: you load a dataset, process it, and want the outputs written back next to the originals with the original names. The image_N + files_N pairing is what makes that possible - the node reads both at once, so the downstream save chain knows which image in the batch maps to which file.

The mechanism is otherwise the same as the standard Dynamic Image Batch: it collects every connected image_N, verifies each is a 4D tensor with a non-empty batch, concatenates them along the batch axis, and resizes any odd-sized inputs to match the first connected image. The files_N inputs are wildcard-typed, so they'll accept whatever path or metadata object your Eclipse loader hands them; the node pairs them up by slot index.

Inputs worth knowing

• image_1 (and more you add) - the images to batch. Only connected slots count.
• files_1 (and siblings) - the matching file/metadata for each image slot. Wire these from your Eclipse loader or Multi Image Loader.
• setnode_name - wireless provider name; fill it in to publish the output via TJ's Set/Get system.

Output is a single IMAGE batch. Same silent 1×64×64 black placeholder if you connect nothing, same resolution-matching to the first image - same gotchas as the non-Eclipse version.

Install

ComfyUI Manager → Install Custom Nodes → search TJ_NODE, or:

cd ComfyUI/custom_nodes
git clone https://github.com/designloves2/ComfyUI-TJ_NODE

Restart ComfyUI. No model files or extra dependencies for this node. It's under ✨ TJ_Node/Image.

When to pick it

Choose this variant over the plain one only when you're actually in an Eclipse metadata workflow and you'll consume the files alongside the batch - for original-path tracking, dataset pipelines, and saving results back to their source structure. If you're just stacking a few generated images for a compare sheet, the plain Dynamic Image Batch is simpler and does exactly the same stacking. The files plumbing is only useful if something downstream is listening for it.