If your footage jitters when you slow it down, Optical Flow mode is likely turned off or acting up. Here’s how to get it working again:
Quick Fix: Enable Optical Flow in your editor’s retiming panel, turn off any “auto speed ramps,” and render with 100% CPU priority. Still glitchy? Fall back to Frame Blending or manually tweak the speed with keyframes.
What’s Happening
Optical Flow isn’t magic—it’s a motion-estimation algorithm that invents new frames between existing ones rather than just blending them. By analyzing neighboring frames and tracking pixel movement, it creates smooth motion even when you slow footage down. The catch? It’s a CPU hog because it has to process every single pixel. Low-contrast or noisy footage often trips it up. (And yes, most editors still rely on 1980s-era methods like Lucas–Kanade or Farneback.)
Step-by-Step Solution
- Open the retiming panel
- Final Cut Pro X: Pick your clip → Modify → Retime → Retime Editor (or hit ⌘ + R).
- Adobe Premiere Pro: Select your clip → Clip → Speed/Duration → Retime Speed → click the wrench icon in the timeline.
- DaVinci Resolve: Highlight your clip → Inspector → Retime Controls → open the Curve editor.
- Choose Optical Flow
- In FCPX, click the clip in the retime editor and switch from “Smooth” to Optical Flow in the dropdown.
- In Premiere, dig into the Time Interpolation section and pick Frame Sampling or Optical Flow—the exact wording changes with updates.
- In Resolve, open the Timewarp node → select Optical Flow from the algorithm menu.
- Remove conflicting speed ramps
- In the retime editor, look for red speed-ramp handles on your clip. Right-click each one → Delete Speed Segment.
- If your editor keeps auto-adding “Auto Speed Ramps,” disable Enhance Retime in the project settings.
- Render at full CPU power
- Before exporting, go to Preferences → Playback & Performance and set Renderer to Mercury Playback Engine GPU Acceleration (NVIDIA/AMD) or Metal.
- In export settings, crank Performance to 100% and turn off Background Rendering.
If This Didn’t Work
- Fall back to Frame Blending
- In FCPX: Open the Retime Editor → switch from Optical Flow to Frame Blend.
- In Premiere: Go to Retime Speed → Frame Sampling → Frame Blend.
- Frame Blending repeats and cross-dissolves frames—it’s not perfect, but it almost never crashes.
- Keyframe the speed manually
- Add a Timewarp or Speed effect to your clip, set keyframes on the speed graph, and ease the motion curve to avoid jarring jumps.
- Pre-process the footage
- Apply a subtle Gaussian Blur (1–2 px radius) to cut down on noise before running Optical Flow.
- Give contrast a slight boost with Levels or Curves so edges stay sharp.
Prevention Tips
- Shoot at higher frame rates—footage at 60 fps or 120 fps slows down more naturally and needs less help from interpolation.
- Keep contrast and focus consistent—Optical Flow gets confused when pixels disappear or blend into flat areas.
- Update your GPU drivers—as of 2026, NVIDIA’s 570-series and AMD’s Adrenalin 25 drivers include tweaks for OpenCV-based Optical Flow shaders.
- Use proxy media for previews—Optical Flow runs faster on 1280×720 proxies, but always switch to full-resolution files for the final export.
I once wasted two hours on a 2-second clip that stuttered every time I slowed it to 50%. After updating drivers, deleting an auto speed ramp, and switching to Optical Flow, the render finally finished without a single dropped frame. (Moral of the story? The algorithm’s only as good as the footage you feed it.)
Using After Effects? Optical Flow hides under Layer → Time → Timewarp → choose Pixel Motion. Adobe just rebranded it—same math, different name.
Sources: Apple Support, Adobe Help Center, Blackmagic Design Support