Ideogram 4 Scheduler (Presets)

Ideogram 4 has become the default "just make me a nice picture" model for a lot of people, and its sampling is finicky about step counts. The docs publish five recommended schedules - Quality, High, Default, Fast, Turbo - and this node is those five numbers baked into a drop-down. Pick one, tell it your output size, and you get the exact sigma schedule Ideogram expects, wired straight into a Sampler Custom.

This is a preset wrapper around ComfyUI core's own Ideogram 4 scheduler. Under the hood it maps your choice to the published parameters: Quality=48 steps, High=34, Default=20, Fast=16, Turbo=12, each with the right mu and std for that preset. It then calls the core scheduler with those values and your width/height. So it's not doing anything a core scheduler can't - it's saving you from typing the recipe and getting a number slightly wrong.

The inputs that matter

• preset - Quality, High, Default, Fast, Turbo. The step counts are the real difference: 48 steps for the "quality" look versus 12 for the turbo-style fast path. Start at Default (20) unless you have a reason not to.
• width / height - the latent dimensions you're sampling at. They feed the scheduler's resolution-dependent math, so keep them in sync with your Empty Latent.

The output

One SIGMAS output. It plugs into the sigmas input of a Sampler Custom (or any custom-sampling rig that takes a sigma chain). From there it's a normal schedule - you can chain Sigma Rescale after it for image-to-image if you need a different start noise, since this preset has no built-in denoise control.

Installing it

Part of silveroxides/ComfyUI-UtilsCollection. Install via ComfyUI Manager (search ComfyUI-UtilsCollection), or:

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

Then restart. Its dependencies are just opencv-python and typing-extensions; the scheduler itself relies on ComfyUI core's nodes_ideogram4, which ships with any recent ComfyUI. No models to download. Note this node's name has no "(Legacy)" tag - it's a first-class scheduler preset in the pack.

Where people get burned

The usual failure here is mixing the wrong sampler with the wrong preset. The Turbo/12-step schedule is tuned for fast sampling; if you run it through a plain euler sampler expecting Default-quality output, you'll get fast, rough results. And remember the schedule is resolution-aware - if you change your latent dimensions, this node needs the new width/height too, or the sigmas will be computed for the wrong size. Otherwise it's one of the least fiddly scheduler nodes around: pick a preset, connect SIGMAS, sample.