Nodes/MultiModel/Denoise Selector
ComfyUI Node

Denoise Selector

A denoise knob that lives on its own node — no more hunting for the slider

By FaberVS·Created about a year ago·Updated about a year ago· 4
Denoise Selector
    • denoise
    denoise0.50

    Let's be honest about what this is: a float pass-through. One slider in, the same number out. The entire node is a FLOAT input called denoise (default 0.5, range 0–1, step 0.01) and a FLOAT output of the same name. If you're comfortable with ComfyUI, you could recreate it in about five lines. So why does it exist?

    Because denoise is a setting you want to see and share. In this pack it feeds KSamplerPipe, and without this node the denoise widget is buried in the sampler you may have several of. A DenoiseSelector puts the knob out in the open where you can read it at a glance, and it lets you wire the exact same value into multiple places at once. Build three parallel pipe workflows, connect one DenoiseSelector to all three samplers, and one slider controls all of them. That's a genuinely handy pattern for comparing how different models or settings respond to the same strength.

    What you're controlling

    Denoise is the "how much do we let the model redraw" dial. At 1.0 you're starting from pure noise - text-to-image. Below that you're starting from an existing image and letting the model only partially redraw it, which is the core of img2img, inpainting, and those two-pass "cleanup" workflows. There's a whole section of the ComfyUI troubleshooting folklore about it: change denoise one variable at a time with a fixed seed, or you can't tell what actually moved the needle. A dedicated node doesn't fix your methodology - but it does make the variable impossible to miss.

    The honest take

    If you have exactly one sampler and you never share values, skip this and use the widget already on KSamplerPipe. The DenoiseSelector earns its keep the moment you have multiple samplers, a workflow you share with people (an exposed knob is self-documenting), or you want to drive denoise from a single control that survives a graph restructure. It's a convenience node, and it knows it. There's no configuration, no hidden behavior - what you set is what comes out.

    Installing

    Same as the rest of the MultiModel pack - ComfyUI Manager, search MultiModel, install, restart:

    cd ComfyUI/custom_nodes
    git clone https://github.com/FaberVS/MultiModel
    

    No dependencies, no model files. It doesn't even need a pipe to do its job - it's a plain float wire, compatible with any FLOAT input in the graph.

    CategoryMultiModel

    Inputs (1)

    NameTypeDefaultDescription
    denoiseFLOAT0.500–1

    Outputs (1)

    NameTypeDescription
    denoiseFLOAT