ConditioningAverageScheduler

RES4LYF's README talks a lot about modulating things over time rather than leaving them fixed for a whole run - regional and temporal conditioning, changing the prompt "on a frame-by-frame basis," that kind of thing. ConditioningAverageScheduler is the two-way version of that idea applied to a straightforward blend: instead of averaging two conditionings at one fixed ratio for the entire sampling run, you feed in a schedule and the blend ratio changes step by step.

How it works

You give it two conditionings and a ratio input - but unlike a normal blend node, ratio here isn't a float widget, it's a SIGMAS-typed input, meaning it expects the output of an actual schedule-building node elsewhere in your graph. That schedule defines how much of conditioning_0 versus conditioning_1 is present at each step. A common use: let composition lock in early on one conditioning, then let detail finish under a different one later in the run - or ramp a style conditioning in gradually over the back half of sampling instead of having it present (or absent) all at once.

The inputs and outputs that matter

• conditioning_0 / conditioning_1 (CONDITIONING) - the two you're crossfading between.
• ratio (SIGMAS) - the schedule controlling the blend over the run. This has to come from a schedule node; it's the entire reason this node exists instead of the stock ConditioningAverage.

Output: conditioning (CONDITIONING), wired into your sampler like any other conditioning.

How to install it

Via ComfyUI Manager, search "RES4LYF". Or:

cd ComfyUI/custom_nodes
git clone https://github.com/ClownsharkBatwing/RES4LYF/
cd RES4LYF
pip install -r requirements.txt

then restart.

Common issues & troubleshooting

If you just want a fixed blend ratio for the whole run, this is the wrong node. ratio has to be wired from a schedule, not typed in as a number - for a constant 50/50 (or any fixed ratio), ComfyUI's stock ConditioningAverage is simpler and does the same job with a plain float widget. Reach for this one specifically when you want the blend to actually change over the course of sampling.

A red link on the ratio input means you tried to feed it a plain number. It wants a SIGMAS-typed schedule output, the same kind of curve RES4LYF's sampler nodes use elsewhere for step-varying parameters.

Think in terms of "what should dominate early vs. late," not "what percentage overall." Because the ratio moves during the run, the useful way to design the schedule is around when in the process each conditioning should be doing the work - composition tends to be decided in the earlier, higher-noise steps; fine detail resolves later.