(deforum) Hybrid Schedule

Every parameter in a Deforum animation can be a schedule - a value that changes per frame - and the hybrid video's flow strength is no exception. This node sets exactly one of those schedules: hybrid_flow_factor_schedule, the per-frame multiplier that decides how strongly the reference video's motion warps your generated frames.

In practice it's the difference between "the animation follows the video" and "the animation is being dragged around by the video." The default is 0:(1), meaning a constant factor of 1.0 - full-strength warp on every frame. Lower it and the influence fades; schedule it over time and you can ease into a video or ease back out of it.

How it works

It's a plain parameter node: it takes the optional deforum_data dict (or starts a fresh one), writes hybrid_flow_factor_schedule into it, and passes it downstream to whatever actually reads it - the Hybrid Motion node resolves the schedule to the current frame index and uses the result as its warp strength. You're writing keyframe data, not applying anything directly.

The schedule syntax is the pack-standard Deforum format:

0:(1)          # constant 1.0
0:(0), 30:(0.5), 60:(1)   # ramp up over 60 frames
0:(sin(2*3.14*t/max_f))   # oscillate across the whole animation

t is the current frame and max_f is the total frame count, so expression-based schedules are legal too. When in doubt, write explicit keyframes - they're easier to debug than trig.

Installation

It ships with Deforum Nodes:

cd ComfyUI/custom_nodes
git clone https://github.com/XmYx/deforum-comfy-nodes.git

Restart ComfyUI, or install "Deforum Nodes" by XmYx from ComfyUI Manager. No extra downloads beyond the pack's standard backend; this node itself is a settings writer.

Practical notes

• Start a hybrid session at 0:(0.5) or lower if you're using RAFT with fast reference footage. Full-strength warping on high-motion video tears frames; easing in from a low factor looks intentional instead of broken.
• Tear-artifact troubleshooting lives here, not in Hybrid Motion. If the warp is too strong, the schedule is where you fix it.
• If you don't use hybrid video at all, this node is dead weight - skip it. It only matters once a Hybrid Motion node is in your image path.

That's the entire node: one schedule, one job. It's about as thin as Deforum Nodes gets, but it's the knob you'll actually reach for when a hybrid render is fighting you.