2-Way Muxer for Conditioning

This is a two-way switch for conditioning. You feed it two CONDITIONING inputs, set a selector to 0 or 1, and it passes exactly one of them through to the output. That's it - a multiplexer ("muxer") for choosing between two prompt conditionings without rewiring your graph. Handy when you've got two prompt setups and want to flip between them with a single number instead of dragging cables.

Note the category: _deprecated_/FlowControl. Searge keeps it so older workflows still load, but it's not the recommended way to do flow control in a fresh graph. Modern packs (rgthree's switches, for example) do this more flexibly and are actively maintained.

How it works

A muxer routes one of several inputs to its output based on a selector value. Here there are two inputs, input0 and input1, and the input_selector (0 or 1) picks which one gets passed along. The unselected input is simply ignored. Both branches still have to be valid connections - you're choosing which to forward, not which to compute - so wire up both, then let the selector decide.

The inputs and outputs that matter

• input0 and input1 (CONDITIONING) - the two conditionings to choose between.
• input_selector (INT, 0 or 1, default 0) - which input to pass through. 0 picks input0, 1 picks input1.
• Output output (CONDITIONING) - the selected conditioning.

The whole node is the selector plus two inputs. There's nothing else to set.

How to install it

Manager: search SeargeSDXL, install, restart. Manual, opencv dependency 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

Selector out of range. The valid values are 0 and 1 - that's it. The node clamps the selector to that range, so any higher number just lands on input1. If you want to choose among more than two conditionings, use the 5-way sibling, SeargeConditioningMuxer5, instead.

Wrong branch selected. It's zero-indexed. Selector 0 is the first input (input0), selector 1 is the second. If you're getting the wrong prompt, you've probably got the off-by-one in your head - 1 does not mean "the first one."

Prefer a maintained switch. Since this is deprecated, and since it only handles CONDITIONING specifically, most people use a general-purpose "any switch" from a current utility pack for this kind of branching - those route any type, not just conditioning, and keep getting updates. Reach for this only inside an existing Searge workflow that already uses it.