SchedulerSelector

The KSampler already has a scheduler dropdown, so why would you install a node that just gives you another one? Because this one - SchedulerSelector - comes with the extras. It's a pure passthrough: pick a scheduler, it hands the name to whatever you connect, and it does nothing else. But the list it exposes is ComfyUI's standard nine plus five you don't get in the stock dropdown: AYS SDXL, AYS SD1, AYS SVD, GITS[coeff=1.2], and LTXV[default].

Those extras are the whole reason to bother. AYS (Align Your Steps, from NVIDIA) is the schedule people used with SDXL to hit good images in noticeably fewer steps - there was a stretch in 2024 where "just try the AYS scheduler" was the standard reply to any SDXL quality complaint. GITS is the schedule a chunk of the Flux crowd reaches for over the plain normal default, and LTXV[default] is exactly what it says: the schedule LTX-Video's own pipeline uses. For video, where every step is an entire image and the model is finicky about its schedule, having that default selectable in a plain widget beats remembering the magic string.

Inputs and outputs

One input: scheduler, a dropdown of the 14 names above. Two outputs, and this is where it gets slightly cute:

• scheduler - the name, typed so it plugs straight into a KSampler's scheduler input.
• scheduler_name - the same string, as a plain STRING, for logging, text nodes, or any node that wants the name as readable text.

The node is a descendant of the equivalent in alexopus's ComfyUI-Image-Saver (the source credits it directly), which is where the scheduler list and its extra implementations originally came from. It costs literally zero compute - no math, no state, just a string passed along.

Installing it

cd ComfyUI/custom_nodes
git clone https://github.com/ARZUMATA/ComfyUI-ARZUMATA

Restart, or search ComfyUI-ARZUMATA in ComfyUI Manager. No dependencies beyond what ComfyUI already ships.

Where people get burned

The one real gotcha is the passthrough nature of it. This node selects schedulers, it doesn't implement them. If you pick GITS or LTXV and whatever you connect to doesn't know that name, you get an error at queue time - and it's not this node's fault, it's that nothing downstream registered that scheduler. The extra names come from the Image-Saver lineage, so they tend to work in environments where that pack (or a ComfyUI build that has them) is present. If you get "scheduler not found," that's your hint to check versions, not to file a bug against this node.

Also worth saying straight: the standard list is exactly the standard list. This won't give you RES4LYF's beta57 or bong_tangent - those live in a different pack entirely, and if you're tuning flow-matching models you want that pack, not this node. And per the perennial advice: on Flux, whatever you pick here, don't pick Karras. Euler with normal or beta is the reliable combination; the scheduler doesn't make the mistake, but it will happily let you.

It's a small utility, and honestly most people are fine with KSampler's own dropdown. It earns its place in workflows you share - a clearly-labeled, separate scheduler widget that survives round-trips through someone else's ComfyUI without getting lost in the sampler node.