Nodes/H3 Studio/H3 Basic Scheduler (wired denoise)
ComfyUI Node

H3 Basic Scheduler (wired denoise)

The H3 denoise dial that tells you the truth

By shootthesound·Created about a month ago·Updated 25 days ago· 29
H3 Basic Scheduler (wired denoise)
  • model
  • SIGMAS
scheduler
steps20
denoise1.00
denoise_modeslice (core)

H3 Basic Scheduler (wired denoise) is a small node that fixes a genuinely infuriating bug in the way stock schedulers treat denoise. It's core's BasicScheduler with one change: denoise is a socket, not a widget you type into. That lets the H3 Studio node's v2v_denoise output drive the restyle amount over a wire - the editor's v2v slider becomes the schedule, live. Wire it Guide.v2v_denoise → here → SamplerCustom's sigmas and you never touch a denoise field again.

Why the extra denoise_mode dial exists

Here's the thing nobody tells you about stock schedulers. "Denoise 0.9" doesn't mean "denoise 0.9". The stock recipe builds a denser int(steps/denoise)-step schedule and keeps its tail - and because int() truncates, any denoise above steps/(steps+1) is silently identical to 1.0. At 3 steps (turbo territory) that's everything above 0.75. At 20 steps it's everything above 0.95.

So on H3's shifted flow schedule, your "0.9" v2v is actually starting at sigma 0.97 - a near-full regeneration running on too few steps. That's the under-resolved, flickery v2v you've been fighting, and it's not H3's fault or yours. It's the dial lying.

  • slice (core) - the stock maths exactly, truncation dead zone and all. Pick this if you want byte-identical behaviour to a normal KSampler.
  • rescale - keeps 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 means what it says at every step count, and a distilled/turbo trajectory keeps its spacing. Recommended for few-step/turbo v2v and any denoise above ~0.85.

The inputs

model and scheduler come from your loader, steps is your step count, denoise is the float socket (wire the Guide's v2v_denoise, or any float - a plain widget works too), and denoise_mode is the two-way switch above. The single output, SIGMAS, feeds a SamplerCustom (or any custom sampler that takes a sigmas socket). If denoise is 0 it returns an empty schedule, so a fully "off" wire doesn't break the graph.

Install and notes

Same as the rest of the pack: Manager (search "H3 Studio") or cd ComfyUI/custom_nodes && git clone https://github.com/shootthesound/ComfyUI-H3Studio, restart, hard-refresh (Ctrl+Shift+R). Needs a ComfyUI build with MiniMax H3 support (v0.30.0+). No extra Python dependencies.

When you'd actually use it

If you only ever do plain text-to-video at full denoise, you can skip it. The moment you do v2v restyling - especially with the H3 Studio node's wired v2v_denoise - this is the node that makes the dial honest. The README's framing is right: leave slice (core) on to match stock behaviour exactly, flip to rescale when the footage comes out under-resolved or flickery at high denoise. It's the quietest, most useful fix in the pack.

Categorysampling/custom_sampling/schedulers

Inputs (5)

NameTypeDefaultDescription
modelMODEL
schedulerCOMBO9 options: simple, sgm_uniform, karras, exponential, ddim_uniform, beta, +3
stepsINT201–10000
denoiseFLOAT1.000–1Wire the Guide node's v2v_denoise output here (or any float).
denoise_modeCOMBOslice (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)

NameTypeDescription
SIGMASSIGMAS