CMK SEGS CONCAT

CMK SEGS CONCAT takes one authoritative image plus up to 32 SEGS collections and gives you back a single composited image. If you've ever run two FaceDetailer passes over the same picture and watched source and processed pixels interleave into a salt-and-pepper mess, this node exists specifically to prevent that, and it says so in the pack's own notes.

Two kinds of input, two strategies

The interesting part is that it detects what it's been handed.

Ordinary SEGS - Impact Pack's container, or anything shaped like it - get native sequential paste semantics. In plain terms: each segment already identifies its own contribution, so paste it into place as-is. The pack is emphatic that a pixel-difference mask is the wrong tool here, because comparing source and result pixelwise is exactly what interleaves them into a speckled mess.

CMK stable branches - the ones produced inside this pack's parallel detailer, FaceProcess and FaceSwap modules - come with three things: a precomposed branch image, a spatial support mask covering only the SEG crop regions that branch actually processed, and a source signature. The branch image is copied in only inside that support. Everything outside stays as the authoritative image. If the branch's stored signature doesn't match the image you're merging onto, you get a loud runtime error - "the branch cache must be recomputed" - rather than a silently wrong composite. That's a cache-integrity check, and it's the kind of failure you want to be loud.

Where two genuinely processed branches overlap, input order is priority and the later input wins. Unchanged sibling segments don't overwrite anything.

Inputs: image (the authoritative full image), segs (required), feather (5) and alpha (255) - both advanced, and they tune the soft-mask edge and opacity used when pasting. Then segs_2 through segs_32, all optional. There's also an optional VISUAL.

Outputs: IMAGE and VISUAL. The node inspects its upstream wiring to work out whether it's merging a Detailer, FaceProcess or FaceSwap family, and registers itself with the visualizer under the right label and sequence so the before/after pair lands in the correct module register. If no branch has actual content, the authoritative image passes through untouched.

Installing

Manager: search CMK Flow → install the CMKFlow entry → restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/CMKFlow/cmk_nodes.git cmk_nodes
python3 cmk_nodes/scripts/install_cmk_requirements.py

You don't need Impact Pack to use this node - it reads and writes the SEGS container format but ships its own pasteback engine. Bringing your own SEGS from Impact Pack works fine; the paste path just switches to sequential. Enable Vue Nodes / Nodes 2.0, which CMK requires.

Practical notes

Every input has to be valid SEGS or the node raises, naming which slot failed - so a None is fine (skipped), but a malformed tuple isn't.

The pack's architecture notes make one rule explicit that's worth repeating here: this node only ever composites complete branch images over their real crop support. There is no per-pixel blending of source and result, on purpose. If you're merging SEGS from an arbitrary third-party pipeline and getting speckle anyway, the SEGS probably carry a branch artefact this node can't interpret - feed the raw detector SEGS instead of a post-processed collection.

And the honest framing from the wider detailing discussion: three parallel detailers only beat one if they're doing genuinely different work - faces, hands, eyes with different detectors and prompts. Run three passes over the same region and you'll spend three times the time rearranging the same pixels.