Nodes/CFE_comfyui/CFE Sigma Sampler Strings
ComfyUI Node

CFE Sigma Sampler Strings

Turn two dropdowns into the exact pair the Flux pipe wants

By CpreForEver·Created 2 years ago·Updated 2 years ago· 0
CFE Sigma Sampler Strings
    • sampler
    • scheduler
    sampler
    scheduler

    CFE Sigma Sampler Strings is the pack's little conversion node, and it exists to solve a wiring problem the pack itself created. Remember how CFE Flux In Pipe expects a SAMPLER object on one port and a scheduler as a plain string on the other? That's an awkward pairing to source from stock nodes - ComfyUI's scheduler dropdowns usually hand you a scheduler object, not text. This node bridges the gap: you pick a sampler and a scheduler from two dropdowns, and out comes (SAMPLER object, scheduler string), ready to drop straight onto the pipe.

    That's the whole job. No model, no steps, no denoise, no noise schedule math. If the pack's CFE Sigma Sampler (the one that builds sigmas) is the muscle, this is the adapter cable.

    How it works

    It reads two ComfyUI-native enums - 34 sampler names and 9 scheduler names (normal, karras, exponential, sgm_uniform, simple, ddim_uniform, beta, linear_quadratic, kl_optimal) - and returns:

    • sampler - the real SAMPLER object, via ComfyUI's sampler_object lookup.
    • scheduler - the plain string you selected, passed through unchanged.

    So the typical setup is: this node feeds CFE Flux In Pipe the sampler object and scheduler string it demands, the pipe carries them through the bus, and the sampler end uses the scheduler string to build its sigmas. The commit history even shows the author changed the scheduler handling specifically so strings worked better with their pipeline - this node is the visible scar from that decision.

    When you'd reach for it

    If you're running the pipe system, this is the natural front-end: it's the most direct way to get the (SAMPLER, scheduler-string) pair into CFE Flux In Pipe. If you're not running pipes, skip it - stock ComfyUI's own sampler/scheduler nodes already produce objects the stock KSampler accepts, and a raw scheduler string is only useful to this pack. It's genuinely thin, and I won't pretend otherwise. Also bear in mind the whole pack is Flux-flavored: if you set Karras here and feed a flow-matching model, you'll get the classic "why is my Flux output mushy" experience.

    Install

    Same as everything else in the pack - zero dependencies:

    cd ComfyUI/custom_nodes
    git clone https://github.com/CpreForEver/CFE_comfyui
    

    Restart, find it under CFE/sampling. Or ComfyUI Manager → CFE_comfyui. It's a two-dropdown node in a one-person pack; it does its one job, and the rest of the pipeline decides whether that job is worth having.

    CategoryCFE/sampling

    Inputs (2)

    NameTypeDefaultDescription
    samplerCOMBOThe name of the sampler being used
    schedulerCOMBOThe name of the scheduler being used

    Outputs (2)

    NameTypeDescription
    samplerSAMPLER
    schedulerSTRING