Preprocess Settings

Preprocess Settings is the "which ControlNet condition am I using today?" switch. Video workflows often generate several control maps at once - depth, canny, pose - and let you pick which one actually drives the generation. This node is the selector: an on/off toggle plus a dropdown that emits a PREPROCESS_SIGNAL for the pack's PreprocessSwitch to consume. The switch then routes the matching preprocessed image through, and nothing else runs.

It's the full-fat version in a family of three. PreprocessSettingsSimple drops the toggle; PreprocessSettingsSingle drops both the toggle and the combo options. This one keeps both, so it's the one you use when you sometimes want preprocessing off entirely.

How it works

Mechanically it's almost nothing - a boolean and a string. The activate toggle and method dropdown are combined into a signal: if activate is off, the signal is "none"; if on, it's the selected method, e.g. "depth" or "depth + canny". That signal is a PREPROCESS_SIGNAL, a pack-defined type that only the pack's own PreprocessSwitch understands. The method list covers the standard ControlNet conditioners - depth, canny, pose - plus the combos (depth + canny, depth + pose, canny + pose) that tell the switch to emit a batch of both maps.

So think of it as a label emitter. All the real work - which preprocessed image gets routed - happens in the switch on the other end of the signal wire.

The inputs and outputs

• activate (default false) - master on/off. Off = "none" signal = original image passes through.
• method (default depth) - which condition, including the three combo options.

The single output, signal (PREPROCESS_SIGNAL) - wire it into a PreprocessSwitch.

Installing it

Part of the Mickmumpitz pack - ComfyUI Manager, search "Mickmumpitz", install, restart:

cd ComfyUI/custom_nodes
git clone https://github.com/mickmumpitz/ComfyUI-Mickmumpitz-Nodes.git

No models; this node only emits a string. The heavy lifting lives in the preprocessors you wire into the switch.

Common issues

The one real gotcha is the custom type. PREPROCESS_SIGNAL is not a string, even though it behaves like one - the output only plugs into the pack's PreprocessSwitch (and friends). If you try to feed the signal into a text node or compare it to a string, ComfyUI will refuse the connection. If that frustrates you, the workaround is the PreprocessSettingsSimple/Single variants with the same constraint, or just accepting that this node is half of a two-node pair. Use them together and it's painless.