ClipMergerSettings

Some nodes exist to hold settings so other nodes don't have to. ClipMergerSettings is that node: it exposes the four parameters ComfyUI's CLIP merge functionality cares about - ties, rescale, ratio, iterations - as actual output wires, so you can control a text-encoder merge from a tidy panel, from another node's output, or from a place in the graph that makes sense to you rather than buried inside the merge node itself.

It's part of artyclaw/artyclaw-comfy. The pattern - a "settings" node that just emits values for a merge node's inputs - is a real ComfyUI idiom, and it's the same one this pack's ModelMergeRatios uses for checkpoint merges.

What the parameters mean

If you've never touched CLIP merging, a one-line primer: CLIP merges blend the text encoders of two checkpoints so the merged model understands both token vocabularies. ties controls how conflicting values are resolved (sum adds them, count averages, off disables the mechanism), rescale renormalizes the result, ratio is the blend weight, and iterations is how many passes the merge runs.

The node itself does no merging - it's a dressed-up pass-through. The source clamps ratio to 0–1 and iterations to 1–100 "just in case," then returns the values. That's the whole mechanism, and it's honest about it.

Inputs and outputs

• ties - dropdown: sum, count, or off.
• rescale - dropdown: off or on.
• ratio - float slider, 0–1, default 0.5.
• iterations - int 1–100, default 10.

All four come out as outputs of matching types - ties (STRING), rescale (STRING), ratio (FLOAT), iterations (INT) - ready to wire into the corresponding inputs of your CLIP merge node. If a merge node's inputs are wired from here, you get the dropdowns where they're comfortable and can even drive ratio from a keyframe or another calculation.

Install

ComfyUI Manager → search ArtyClaw Comfy Nodes, or:

cd ComfyUI/custom_nodes
git clone https://github.com/artyclaw/artyclaw-comfy

Restart. No dependencies beyond math.

Where people get burned

The failure mode is thinking this node does the merge. It doesn't - it just feeds values to whatever node actually merges the CLIPs, and if you wire only this node into a graph without a real CLIP merge node, nothing happens. Second, the enum choices are fixed by the source, so you can't add a ties mode that doesn't exist in the list. And third, because it's a pass-through, a stale value is always a graph-cache problem, not a node problem: if you changed the slider and the output didn't update, force re-execution. For its intended job - remote-controlling a CLIP merge - it works exactly once you understand it's a control panel, not the machine.