🏝️ Sliced Commons

The Shima "sliced" ecosystem is a group of nodes that split a big image into overlapping strips, process each one, and stitch them back - the whole point being VRAM management. The danger with that design is obvious: four nodes each carrying their own slices, overlap, and feather_size widgets means changing one setting in four places, and the first time you forget one you get seams. Sliced Commons is the single source of truth that fixes it.

It's a configuration node, pure and simple. You set the parameters once here, and it emits a SLICED_COMMONS bundle (a plain dict under the hood) that every other node in the ecosystem - Sliced Upscaler, Sliced Image Hub, Slice Combiner Hub - accepts as an optional input. When that wire is connected, the consumer overrides its own widgets with the Commons values. It's the same "one authoritative value, many consumers" pattern the plumbing layer lives on, applied to a group of settings instead of one value.

The inputs

• orientation - Vertical or Horizontal. In this pack "vertical" means slicing along the X axis into vertical strips; pick whichever matches how you want to cut.
• slices - how many segments, 2–10, default 4.
• overlap - pixels of overlap between neighboring slices, default 64. Overlap is what lets the feathering blend seams instead of leaving a visible line.
• feather_size - width of the alpha-blend gradient, default 32.
• feathering - the master toggle. Turn it off and the node forces overlap and feather_size to 0, giving hard edges. This "feathering off zeroes the other two" behavior is propagated to every consumer, which is a nice touch - you flip one switch and the whole chain knows to stop blending.

Output is the single sliced_commons bundle.

Installing it

Part of KDB-USJP/shima_wf:

cd ComfyUI/custom_nodes
git clone https://github.com/KDB-USJP/shima_wf

Restart ComfyUI. No special dependencies for this node itself - it's a dict in, dict out - though the ecosystem it feeds expects the rest of the pack.

Why you'd bother

If you're only slicing a single image once, skip it and set the widgets directly - this node is overhead. The moment you're running a workflow with an upscaler and a combine hub, though, it earns its keep: change slices in one place and the whole chain re-syncs. The one thing to remember is that wired Commons overrides widgets silently, so if you set slices to 8 on the Upscaler and nothing happens, an old Commons node upstream is almost certainly the reason. Check the wire first.