ComfyUI Node
H3 Basic Scheduler (wired denoise)
Core's BasicScheduler with denoise as a SOCKET, so the Guide node's v2v_denoise output can drive the restyle amount over a wire: Guide.v2v_denoise -> here -> SamplerCustom's sigmas. 'slice' is core's maths exactly; 'rescale' fixes core's dead zone at high denoise and suits distilled/turbo schedules.
H3 Basic Scheduler (wired denoise)
- model
- SIGMAS
◄scheduler▾►
◄steps20►
◄denoise1.00►
◄denoise_modeslice (core)►
Categorysampling/custom_sampling/schedulers
Inputs (5)
| Name | Type | Default | Description |
|---|---|---|---|
| model | MODEL | — | |
| scheduler | COMBO | 9 options: simple, sgm_uniform, karras, exponential, ddim_uniform, beta, +3 | |
| steps | INT | 201–10000 | — |
| denoise | FLOAT | 1.000–1 | Wire the Guide node's v2v_denoise output here (or any float). |
| denoise_mode | COMBO | slice (core) | How denoise becomes a schedule. 'slice (core)': what every stock scheduler does — build a denser int(steps/denoise)-step schedule and keep its tail. Because int() truncates, ANY denoise above steps/(steps+1) is silently identical to 1.0 (at 3 steps that's everything above 0.75; at 20 steps, above 0.95), and the step waypoints move — which distilled/turbo LoRAs, trained for one exact trajectory, tend to undershoot (residual noise, flicker). 'rescale': keep the schedule's own shape and step count, compressed into [denoise, 0]. In flow matching sigma IS the noise fraction, so starting at sigma=denoise is exact. The dial then means what it says at every step count, and a turbo trajectory keeps its distilled spacing. Recommended for few-step/turbo v2v and for denoise above ~0.85. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| SIGMAS | SIGMAS | — |