Priority Selector
One dropdown that decides which Wan expert gets the steps
- priority
Priority Selector is a helper node, and it's honest about being one: one dropdown in, one dropdown out, zero computation. Its job is to make the "priority" choice in your Wan 2.2 workflow easy to see, share, and switch - without editing a widget buried inside the Sampling Plan node. If you've ever tried to rewire a big workflow and lost track of which node owns which setting, this is the pattern: pull the one choice you care about out to the surface.
What the priority actually controls
Wan 2.2 splits denoising between a high-noise expert (motion, structure) and a low-noise expert (detail). Priority decides how much of the denoising range each expert owns - more range for high means more steps spent on composition and motion; more for low means more spent on refinement and texture.
The four options, in the author's own framing:
- Balanced - follows the profile's native allocation (the default, and the one to leave it on)
- 50/50 Split - forces an even high/low range split regardless of profile
- Motion / Structure - shifts roughly 10% of the range to the high-noise expert
- Detail / Refinement - shifts roughly 10% to low-noise refinement
The planner guarantees at least one step per expert either way, so you can't zero one stage out by accident.
Wiring it
The node takes one priority input (the same four-value combo) and outputs it as a type-compatible value for the Sampling Plan's priority input. It uses a custom output type, so ComfyUI only lets it connect where a priority value belongs - which is the point of these combo helpers: the type system catches the wiring mistake before you run the graph.
Why bother, when the Sampling Plan has the same dropdown on it? Same reason you'd pull task and acceleration into selectors too: when one mode switch drives several branches, you wire them all from one visible control instead of remembering to sync four widgets. It also plays nicely with grouping - mute the group, and the priority choice travels with it.
Install
Installs with the whole pack via ComfyUI Manager (search Sampling Planner) or:
cd ComfyUI/custom_nodes
git clone https://github.com/boobkake22/ComfyUI-SamplingPlanner
Restart, and it appears under sampling / Sampling Planner / Helpers. No models, no dependencies.
The take
Is it essential? No. It's a quality-of-life nicety, and the pack's real value lives in the Sampling Plan node and its breakouts. But if you're building a Wan 2.2 workflow you plan to share or revisit, extracting priority (and task, and acceleration) into selectors is the cheapest way to make the interesting decisions legible at a glance. I keep the priority on Balanced for general use and flip to Detail / Refinement when a render comes back muddy on textures - that's the two-option workflow that covers most of what this dropdown is for.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| priority | COMBO | Balanced | Balanced follows the profile, 50/50 forces an even split, Motion favors high noise, and Detail favors low-noise refinement. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| priority | Balanced,50/50 Split,Motion / Structure,Detail / Refinement | — |