Nodes/ComfyUI-MakkiTools/ImageCountConcatenate(已弃用-mki-图像批次拼接)
ComfyUI Node

ImageCountConcatenate(已弃用-mki-图像批次拼接)

Merging batches, and why it's marked deprecated

By MakkiShizu·Created about a year ago·Updated 7 months ago· 9
ImageCountConcatenate(已弃用-mki-图像批次拼接)
    • IMAGE

    In ComfyUI, an "image" that comes out of a sampler is usually a batch - one tensor holding several images stacked along a dimension. ImageCountConcatenate_makki (display name "ImageCountConcatenate(已弃用-mki-图像批次拼接)") joins multiple such batches into one bigger batch, so you can take a 4-image batch and a 6-image batch and get a single 10-image batch for one pass through a preview or a batch processor.

    It's flagged deprecated in the pack, and the README says to use deprecated nodes with caution. So before you build on it, here's what it does and where it stands.

    How it works

    You feed it however many image batches you like - the node takes dynamic image inputs, adding a new slot each time you connect the last one. It then:

    1. Resizes everything to match the first input (bicubic, center-cropped) - batches of different resolutions get forced onto the first one's dimensions.
    2. Normalizes channel counts - RGB, RGBA, and grayscale inputs all get converted to match the reference, handling the alpha-flattening and channel-adding cases.
    3. Concatenates along the batch dimension, so each input batch stays intact and the result is one combined batch.

    Inputs and outputs

    There are no declared inputs in the schema - the images arrive through those dynamic slots. One output: IMAGE. If you feed it one batch of 4 and one of 6, you get a batch of 10.

    Why it's deprecated, and what to use instead

    Deprecated here mostly means "the author moved on." There's nothing broken about the code - the size-matching and channel handling are genuinely thoughtful, which is more than some core nodes do. But the ComfyUI ecosystem has since shipped first-class ways to manipulate batches, and newer utility packs (the WAS suite and Impact Pack are the usual answers) handle batch concatenation with more control over the resize behavior.

    If it's already in a workflow you run, it'll keep working - deprecated doesn't mean deleted. If you're building new, prefer a maintained alternative so you're not depending on a node that could vanish on a future update. (And note the pack's 2025 rename: if an old workflow references this node's pre-rename class, re-pulling the pack is the fix.)

    Installing

    cd ComfyUI/custom_nodes
    git clone https://github.com/MakkiShizu/ComfyUI-MakkiTools
    cd ComfyUI-MakkiTools
    pip install -r requirements.txt
    

    Restart ComfyUI. One behavioral warning regardless of which node you end up using: forcing different-resolution batches onto one size will distort them, since it's a plain resize rather than a crop-aware layout. If your batches come in different sizes, fix the sizes upstream before concatenating - or you'll get squished frames and wonder why.

    CategoryMakkiTools

    Inputs (0)

    No inputs

    Outputs (1)

    NameTypeDescription
    IMAGEIMAGE