Settings Select ⚙

Settings Select is Model Select minus the loading: it picks a saved preset and emits its sampler_settings, width, height, label, info and gen_extra_info - and never touches a model. That's the investigating case, and it's more useful than it sounds. When you want to run one model at several different settings and seeds and compare them side by side, two Model Selects would each want to own the model. Settings Select gives you N cheap recipe emitters hanging off one model instead.

The inputs

• model - whose presets to offer. Ignored when model_id is wired.
• preset - a saved preset for the model above (its own, plus any shared with its families). Saved via Settings Save.
• seed_override - the field to sweep. -1 means "use the seed stored in the preset"; anything else replaces the seed on every stage. When you want the same settings at several seeds to see how stable the look is, this is the input you sweep, not the sampler.
• width / height - fallback size, used only when the chosen preset carries no size of its own (which is why Settings Save stores the latent size with the preset).
• model_id - wire Model Select's model_id output here and the preset list follows that node's pick. The model gets chosen in exactly one place, and every Settings Select hanging off it re-narrows when you switch.

The outputs

sampler_settings (the recipe, into Ouroboros/Phantas/Chimera/Siren's sampler input), width and height, label - a ready-made caption like anc4+euler4 · seed 999 for Image Compare via a Set/Get Accumulator - info (what the preset is for), and gen_extra_info. Two details the docs flag: unlike Model Select it does not jump to the model's default preset (choosing presets is the point), and if the preset carries bundle overrides, info says they don't apply here - overrides retune the model, and this node never builds one.

When it earns its keep

The canonical setup: one model, a Settings Select per candidate recipe (with seed_override swept across them), each feeding a sampler, each output wired into Image Compare. That turns "which settings actually worked for this model?" into a single run with labelled candidates. It's also how a stored per-model recipe drives Siren (Music Sampler), which accepts a Sampler Settings bundle in place of its own widgets.

Installing it

Part of Kinburg/Kinburg-Nodes - ComfyUI Manager search "Kinburg-Nodes", or cd ComfyUI/custom_nodes && git clone https://github.com/Kinburg/Kinburg-Nodes, restart. No dependencies. Nothing works here until you've saved presets, so if the preset dropdown is empty, that's a Settings Save problem, not this node's - go capture a model and save a recipe first.