Flux ReduxFloat Ramp

Flux Redux is BFL's image-guidance model for Flux - you feed it a reference image and it steers the generation toward that style or composition. It's genuinely good at style transfer, but it has one maddening property: the strength knob is a blunt instrument. Too low and the reference does nothing; too high and Redux overfits - you get a copy of the reference and the prompt is basically ignored. The community fix, discovered in late 2024, is to ramp the strength through the denoise steps instead of holding it constant: start at 0 so the prompt establishes the subject, then let the style pour in. That's exactly what Flux ReduxFloat Ramp does - it's a little eased float generator whose whole job is to feed that strength slot.

Where it came from

A reddit user, Total-Resort-3120, posted "Optimize Redux as a style transfer tool with this custom node" in November 2024 explaining the trick and sharing a FloatRamp node via a catbox .rar - a genuinely fiddly install. The glif team bundled it into this pack (the code credits the reddit user), which is the only reason it survived as an installable thing. Good outcome for everyone.

How it works

You give it a start float (default 0), an end float (default 1), a steps_threshold (default 20), and a ramp_type from a menu of seven easing curves: linear, ease_in, ease_out, ease_in_out, exponential, smoothstep, bounce. Each execution it computes progress as current_step / steps_threshold, runs it through your chosen curve, and returns start + (end - start) * curve. Once past the threshold it pins to end. The output is a single value FLOAT - wire it into Redux's strength input (or honestly any strength slot; the author himself noted it'll drive Canny or depth strength too).

The gotcha you need to know: the step counter lives on the node instance, and in the shipped source that counter is read but never incremented. In a plain single ComfyUI queue run, each execution builds a fresh node and you get the same early-step value every time - it does not visibly animate. It makes sense when whatever is driving the workflow (like glif's own editor) keeps the instance alive and steps it, or when you're iterating inside a loop that re-invokes per step. So: test what it actually outputs in your setup before you trust it, and don't be surprised if a stock ComfyUI run just hands you a constant.

Install

Part of ComfyUI-GlifNodes. ComfyUI Manager → "ComfyUI-GlifNodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/glifxyz/ComfyUI-GlifNodes

Restart ComfyUI. No models, no extra downloads - the whole node is a handful of easing functions.

The takeaway

Ramping Redux strength 0→1 over the first handful of steps is one of those "why didn't I think of that" tricks that makes Redux actually follow your prompt and carry the style. This node is the cleanest way to do it that survived, even if its step counting assumes a friendlier executor than stock ComfyUI. Start linear, 20 steps, and see if the style transfer finally behaves.