SP_SupirSampler

This node only makes sense alongside SP_Supir and its companion sampler-builder nodes, so if you landed here without already knowing what SUPIR is, start with the SP_Supir article first - this one's a small supporting piece, not a starting point.

What it does

SP_SupirSampler takes one input - supir_sampler, typed SP_SupirSampler - and breaks it apart into four separate outputs: dpmpp_eta (float), edm_s_churn (int), restore_cfg (float), and sampler (string, presumably the sampler's name). In other words, it's a splitter. Something else in the pack - SP_SupirSampler_DPMPP2M is the one covered elsewhere in this series - builds an SP_SupirSampler bundle; this node takes that bundle apart into its individual pieces.

Notice that the four fields it exposes don't map one-to-one onto what SP_SupirSampler_DPMPP2M's own inputs are (that node only takes dpmpp_eta and a tiled toggle). That's a signal the SP_SupirSampler type is meant to be generic across more than one sampler variant - edm_s_churn and restore_cfg are parameters that belong to SUPIR's EDM sampler path rather than its DPM++2M one, which lines up with how SUPIR's own ComfyUI implementation is organized: two sampler families under one config shape, DPM++2M and EDM, sharing a restore_cfg restoration-strength knob and a named sampler field, with each family populating only the fields relevant to it.

Why you'd use it

Mostly for two reasons: inspecting what's actually inside a sampler bundle someone else built (useful while debugging a workflow you didn't author), or pulling out just one field to feed somewhere else - say, wiring restore_cfg into a display node to confirm it's set the way you expect, without having to unwind the whole bundle by hand. If you're just running SP_Supir end to end with SP_SupirSampler_DPMPP2M feeding it directly, you won't need this node at all - it's a diagnostic and composition tool, not a required link in the chain.

Installing it

Ships as part of the SP-Nodes pack, same as everything else here:

• ComfyUI Manager: search "SP-Nodes", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/bananasss00/ComfyUI-SP-Nodes, restart ComfyUI.

No models or extra dependencies for this node specifically - it's pure data unpacking.

Troubleshooting

If a field comes back as an unexpected default rather than the value you thought you set, check which sampler-builder node actually produced the SP_SupirSampler bundle feeding this node. Since only some fields are relevant to any given sampler variant, a field this node exposes that your upstream builder never populated will come back as whatever that builder's own default happens to be - that's expected behavior given the config shape is shared across sampler types, not a sign this node is malfunctioning.