Shift Override

Shift is the flow-matching knob everyone argues about and almost nobody fully controls. Sampling Plan's Auto profile picks a sensible one for you - Wan native, LightX2V 4-step, or ComfyUI/YAW depending on your setup - but sometimes you just want your own number. Shift Override is that: one field, one forced value, and a full rebuild of the plan around it.

What it does

Inputs: plan and shift (default 8, range 0.01 to 100). Set your shift, and the node rebuilds the complete plan from the original planner controls - full sigmas, the high/low sigma slices, the step split, the boundary handoff - all revalidated with your shift as the anchor. It's order-independent with Step Split Override: both store their request in the plan and rebuild from the original controls, so you can chain them in either order and get the same result.

The important nuance the README spells out: shift replaces the Auto profile's anchor, it does not redefine the expert boundary. The boundary (0.875 T2V / 0.900 I2V) is a property of the trained Wan 2.2 architecture. Shift just controls where the scheduler concentrates its evaluations - more effort on composition or more on detail - and the planner solves a boundary-safe curve at your chosen anchor. A bounded adjustment is only applied when the anchored curve can't produce a valid boundary crossing; otherwise your anchor is preserved and the curve is built around it.

Why the companion node matters

Shift alone on the sigma curve is only half the story. ComfyUI also patches the model object with the same shift, and if the model doesn't get the patch, curve and model disagree. That's why the README pairs this node with Model Pair Breakout - it's the node that applies the rebuilt plan's shift to both expert models:

Sampling Plan → Shift Override → Model Pair Breakout → samplers

Use that chain and your model shift and sampling curve cannot diverge, which is the standard way "I set shift but nothing changed" failures actually start.

Where to begin with the number

The pack's evidence notes give you the landmarks: Wan's own configs use shift 12 (T2V) / 5 (I2V); ComfyUI's official templates use 8; LightX2V's 4-step accelerated recipes use 5. If you're overriding, start near one of those depending on your recipe and move in small steps - shift is subtle, and big jumps mostly just move the curve's resolution around rather than transform your render.

One scheduler gotcha that will waste your evening: some schedulers (notably bong_tangent-style ones) apply their own sigma shift and ignore the workflow's. If Shift Override seems to do nothing, check the scheduler first - that's a known ComfyUI behavior, not a bug in this node.

Install

Pack-standard:

cd ComfyUI/custom_nodes
git clone https://github.com/boobkake22/ComfyUI-SamplingPlanner

or ComfyUI Manager (search Sampling Planner), restart. It's under sampling / Sampling Planner / Wan 2.2. No dependencies.

Verdict: if you trust the Auto profile, you don't need this node. If you're a shift tweaker who's ever wanted to dial in a value and have the whole plan - models included - follow you, it's the correct way to do that in this pack.