5-Way Muxer for Conditioning

Same idea as the 2-way muxer, scaled up: this one picks one of five CONDITIONING inputs and passes it through based on a selector. Five prompt setups, one output, one number to switch between them. It's a flow-control convenience for when you've built several conditioning branches and want to flip which one feeds your sampler without unplugging anything.

As with its 2-way sibling, it's in the _deprecated_/FlowControl category - kept so older Searge workflows keep loading, not the recommended tool for a new graph. A maintained general-purpose switch node does the same job for any type and stays updated.

How it works

A five-input multiplexer. input0 through input4 are your five conditionings, and input_selector (0 to 4) chooses which one reaches the output. The other four are ignored on that run. All five inputs still need valid connections - you're selecting which to forward, not gating which to build - so wire them all and let the selector do the choosing.

Where this earns its place is A/B/C-style comparison inside one graph. Build five different prompt or style conditionings once, feed them all in, and then sweep the selector from 0 to 4 across runs to see each variant come through the same downstream sampler and settings. It's a poor-man's version of the batch-comparison workflows people miss from A1111 - cruder, but it keeps everything else identical so the only thing changing is the conditioning branch.

The inputs and outputs that matter

• input0–input4 (CONDITIONING) - the five conditionings to choose among.
• input_selector (INT, 0 to 4, default 0) - which input to forward. 0 is input0, 4 is input4.
• Output output (CONDITIONING) - the selected conditioning.

That's the node. Five inputs, a selector, one output.

How to install it

Manager: search SeargeSDXL, install, restart. Manual, opencv first:

python -m pip install opencv-python
cd ComfyUI/custom_nodes
git clone https://github.com/SeargeDP/SeargeSDXL.git

Restart ComfyUI. No model files.

Common issues & troubleshooting

Off-by-one on the selector. Zero-indexed: selector 0 forwards input0 (the first), selector 4 forwards input4 (the fifth). If the wrong prompt is coming through, it's almost always this. The selector clamps to 0-4, so a 5 or higher just sticks on input4.

Only need two branches? Use SeargeConditioningMuxer2 instead - no point wiring five inputs when two will do, and you'd have to feed all five valid connections here regardless.

Consider a modern switch node. This is deprecated and conditioning-only. Current utility packs offer "any-type" switches that route conditioning, latents, images, models - anything - through one maintained node, which is usually the better call for new work. Keep using this only where an existing Searge workflow already depends on it.