Flex Video Seek ⚡🅡🅞🅣🅘

Instead of playing your clip in order, Flex Video Seek uses a FEATURE signal to pick which frame plays at each output step - effectively scrubbing the timeline back and forth based on whatever's driving it, rather than advancing linearly. It's the pack's tool for non-linear video playback: audio-reactive stutter, jump-cut effects, or a clip that ping-pongs around a moment instead of just running through once.

How it works

The mechanism is minimal by design: images is your source sequence, reverse flips the base playback direction, and the FEATURE wired into opt_feature drives where in the sequence each output frame is pulled from. One detail worth knowing straight from the node's own tooltip: feature_mode "only supports 'relative' mode" for this specific node - unlike most Flex nodes that let you pick relative or absolute, seeking here is always centered around the current position rather than an absolute jump computed from zero. feature_threshold still applies as the gate below which the feature doesn't move the seek position at all.

Inputs and outputs that matter

• images (required, IMAGE) - the source sequence to seek through.
• reverse (default off, BOOLEAN) - flips the base playback direction.
• feature_threshold (default 0, 0–1) - minimum feature value before seeking kicks in.
• opt_feature (optional but load-bearing, FEATURE) - the signal that actually drives the seek position; feature_param is fixed to seek.
• Output - a single IMAGE batch.

Installing it

Via ComfyUI Manager: search "RyanOnTheInside," install, restart. Manually:

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

then restart. No model downloads - it's frame selection driven by your feature curve.

Common issues & troubleshooting

Without opt_feature connected, seeking effectively does nothing. Like Flex Video Direction, this node's whole purpose depends on a wired feature signal - there's no static "seek to frame N" control exposed here. If you just want a plain reversed clip, reverse alone covers that without needing a feature at all.

Seeking looks jittery or repeats frames oddly. A raw, spiky audio feature translated directly into seek position will jump around unpredictably - smoothing the feature upstream (or using one of the pack's shaped extractors instead of a raw signal) usually produces a more musical, less chaotic result.

Trying to set feature_mode to absolute and it's not taking effect. That's expected - per the node's own tooltip, relative is the only supported mode here, so there's nothing to switch.