MixMod High Res Guider

The name says "High Res," so the reasonable assumption is this node adds a high-resolution pass to your MixMod mix. I checked the source before writing this, and the honest version is: in the current build, the High Res guider runs the same team-mode mixing as the plain MixMod Guider, and its ratio, start_step, and end_step inputs aren't wired into the blending path. The guider's step-window logic reads from each component's Options, not from this node's own step fields. So it's effectively a team-mode guider wearing a fancier label - with dead inputs, at least for now.

That's not necessarily a reason to avoid it; it's a reason to know what you're getting. If you were reaching for this node to do a two-pass hires fix inside one sampler, that's not what this is, and you'll be confused when ratio changes nothing. If you just need a second team-mode guider (say, to branch a workflow into two samplers), it works fine - it's a working MixModGuider in mode="team".

Inputs and output

• component (required) - the COMPONENT chain.
• ratio (default 0.5, 0–1) - documented as a high-res blend ratio; in the current source it doesn't reach the team-mode mixing math.
• start_step / end_step (default 0 / -1) - an intended step window for the high-res behavior; in the current source, step gating comes from Options Scheduler nodes on the components instead.
• Output: GUIDER, into a guider-accepting sampler (SamplerCustomAdvanced and friends).

If you actually want to schedule a model's activity, attach a MixMod Options Scheduler to the component - that's the wiring the code honors. If you want different resolution behavior per model, the MixMod Options Scale node (which genuinely downscales a component's model) is the real lever.

Installing

Part of ComfyUI-MixMod. ComfyUI Manager → search "ComfyUI-MixMod" → install and restart, or:

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

No requirements.txt, no model downloads.

Troubleshooting

The most likely "problem" with this node is expectation mismatch: you set ratio to 0.8 expecting a sharper output and nothing changed. That's the current build being honest about its TODO status, not your wiring. File it under "experimental pack, experimental node" - the author explicitly labels this stuff experimental, and this is one of the spots where the README's promise (scheduling everything) hasn't fully caught up with every node's inputs yet. Use the plain Guider, the Options nodes, or the FFT guiders for behaviors that actually execute, and treat High Res as a placeholder that happens to sample.