Preprocess Settings (Simple)

Preprocess Settings (Simple) is the middle child of the Mickmumpitz pack's preprocess selector trio. Where the full PreprocessSettings has an on/off toggle plus a method dropdown, this one keeps just the dropdown: pick a control condition - depth, canny, pose, or a combo - and it always emits that as a PREPROCESS_SIGNAL for PreprocessSwitch. No toggle means no "off" state; preprocessing is always on with whatever method you chose.

That's genuinely the right call for a lot of workflows. If you're running a control-driven pipeline and you never want to turn preprocessing off, an always-on selector is simpler to read than one with a dead toggle sitting at the default. The toggle only earns its keep when you're frequently comparing "conditioned" vs "unconditioned" output.

How it works

One input, one output. The method dropdown maps directly to the signal: select depth + canny and the node emits exactly that string as a PREPROCESS_SIGNAL. The downstream PreprocessSwitch reads the signal and routes only the matching preprocessed image(s) through - combos cause it to batch both maps together. Nothing is computed here; this node is just the label maker that tells the switch which branch to open.

The method list matches the full version: depth, canny, pose, depth + canny, depth + pose, canny + pose.

The inputs and outputs

• method (default depth) - the single dropdown.

Output: signal (PREPROCESS_SIGNAL) - feed 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, no extra deps.

Common issues

Same custom-type caveat as its siblings: PREPROCESS_SIGNAL only connects to the pack's switch nodes, so don't expect to splice it into text nodes. And because there's no toggle, "off" isn't an option - if you need to fall back to the original image for some runs, wire the original input on PreprocessSwitch and reach for the full PreprocessSettings version with activate instead. If you only ever use single conditions (never the combos), the even simpler PreprocessSettingsSingle trims the dropdown down to three options and is slightly less error-prone to look at.