My Secret To Smooth Speed Ramping Transitions in Davinci Resolve

Most tutorials hand you a recipe. This one hands you the why behind the recipe... and that changes everything.

Jamie Fenn opens with a confession that sounds simple: "It's just speed ramping." But then he spends the next eight minutes proving that the gap between just speed ramping and buttery smooth speed ramping is where craft lives.

And that gap? It's not where you think it is.

The Math Nobody Talks About

Before a single creative decision gets made, there's arithmetic. Shooting at 120 frames per second on a 30fps timeline means 25% is your floor. That's as slow as the footage can go before DaVinci Resolve starts guessing... interpolating frames that don't exist. Below that threshold, you're asking software to invent reality.

This is the kind of constraint most creators skip past. But constraints aren't limitations. They're architecture. Knowing your floor means every speed choice above it is intentional, not accidental.

Speed Points Are Just the Skeleton

The Retime Controls workflow is straightforward. Add speed points. Drag a segment to 25%. But the raw result looks mechanical... because it is. Linear speed changes hit the eye like a staircase when your brain expects a ramp.

The real work happens in the Retime Curve editor. Fenn clicks on each speed point and applies curve handles, converting hard angles into gradual eases. This is the difference between a cut that says "I edited this" and a transition that breathes.

Small detail, massive impact. Smoothing those curves is where the footage stops being arranged and starts being composed.

Stabilization: Choosing the Right Kind of Correction

Gimbal footage carries its own quirks. Fenn flags something most tutorials skip entirely: DaVinci Resolve's default stabilization mode, Perspective, can introduce visual distortion on gimbal shots. His recommendation is Similarity mode... smoothness at about 50%, cropping ratio all the way down.

It's a small settings change. But it's earned knowledge. The kind you only get from stabilizing dozens of clips and watching them warp in ways that make you curse.

The Part Before Post: Shooting for the Edit

Here's where Fenn does something I deeply respect. He stops the software tutorial and walks outside.

Because the truth is... no amount of Optical Flow magic fixes bad footage. He breaks down the physical craft:

- FPV mode on the gimbal. The DJI Ronin RS2 follows wherever you point it. No robotic corrections fighting your creative intent. - Big, smooth arcs. Not jerky pans. Not dramatic whips. Wide, consistent, sweeping movements around the subject. - Consistent speed. Your hands set the tempo. The edit amplifies it.

He even draws it out on a whiteboard... a simple top-down diagram showing smooth arcs versus erratic zig-zags. The smooth arcs become cinematic. The zig-zags become garbage, no matter how much post you throw at them.

This is the unsexy truth about creative work. The flashy result is downstream of the disciplined input.

Matching Movement: The Invisible Edit

Transitions don't happen between clips. They happen between movements. Fenn demonstrates how the outgoing clip's direction and momentum must match the incoming clip's direction and momentum. If clip one twists backward and left, clip two needs to pick up that same backward-left energy.

This is editing theory that applies far beyond speed ramps. It's the principle behind every seamless transition in every film you've ever watched without noticing. The best edits are the ones your eyes never catch.

The Secret Sauce: Fusion Nodes That Actually Work

Now... the thing everyone clicked for.

Fenn's technique uses an Adjustment Clip dragged over the transition point, then opened in DaVinci Resolve Fusion Page|Fusion. Two nodes:

1. Optical Flow — analyzes the motion between frames 2. Vector Motion Blur — applies blur based on that analyzed motion

This combination produces motion blur that's informed by actual pixel movement, not just a directional smear. The result looks organic because the blur follows the footage's real vectors.

He also shows what standard motion blur looks like in comparison... and the artifacts are visible. Weird warping between clips. Edges that don't quite resolve. His method handles those transitions with noticeably more grace.

Two more practical details that matter:

- Fade the adjustment clip edges. Don't slam the motion blur on and off. Ease it in and out so the effect breathes with the speed change. - Keep the nodes deactivated while editing. Optical Flow is computationally expensive. Activate right before delivery. Your CPU will thank you.

What This Is Really About

Fenn never says this explicitly, but the entire tutorial is a lesson in layered craft. No single technique makes the transition smooth. It's the math of frame rates. The physical discipline of gimbal movement. The editorial eye for matching motion. The curve smoothing. The stabilization settings. The Fusion nodes. The faded edges.

Every layer matters. Skip one, and the whole thing feels slightly off in a way most viewers can't articulate but absolutely feel.

That's the difference between someone who knows a tool and someone who understands a craft. The tool is the speed ramp. The craft is everything around it.

So here's your invitation: next time you're editing, don't just look at the flashy technique. Look at the five quiet decisions that made the flashy technique possible. The constraint you respected. The movement you planned before you hit record. The curve you smoothed. The artifacts you refused to accept.

The smooth transitions in your work... and in your life... rarely come from one dramatic move. They come from all the invisible disciplines layered underneath. ✨

Quietly working. Always.

--- Source: https://www.youtube.com/watch?v=ley0hp5__tY