Generated at sixteen, delivered at twenty-four

The frame rates you are actually dealing with

A video model has a native frame rate baked into training. Common values are 16, 24 and 30. A model trained at 16 fps that hands you a 24 fps file did not generate 24 frames per second: something interpolated the extra ones.

This is a good trade and worth understanding rather than resenting. Generating more frames costs quadratically through attention. Interpolating them costs a small, separate network run at a tiny fraction of the price. For most footage the result is indistinguishable.

The interpolators you will meet: RIFE (fast, free, open, the default in most pipelines), FILM (Google’s, handles large motion better, slower), and the optical-flow retimer inside DaVinci Resolve. All three estimate motion between two real frames and warp pixels along it.

Where interpolation gives itself away

Motion estimation fails in three specific places, and once you can name them you will see them in other people’s work constantly.

1. Occlusion boundaries. Where one object passes in front of another, some pixels exist in frame A and not in frame B. There is nothing to warp, so the interpolator smears or invents. You see a soft halo hugging the moving edge.
2. Fast motion. If something moves more than the estimator’s search range between frames, the match is wrong and the intermediate frame tears. A hand crossing the frame quickly gets a ghost.
3. Anything appearing or disappearing. A flash, a spark, a blink, a hard cut inside the clip. Interpolating across an event produces a half-existing frame.

The practical rule: interpolate calm footage freely, and be suspicious of interpolated fast action. If a clip has one difficult second, interpolate the rest and let that second run at native rate rather than fixing it everywhere.

Motion blur, which generated footage often lacks

A real camera exposes each frame for a fraction of the frame interval: the classic 180-degree shutter means the sensor is open for half of it. Anything moving smears across that exposure. Your eye expects it.

Generated frames are frequently too clean. Every frame is crisp, so motion reads as a sequence of sharp positions rather than as movement. The effect is subtle and it is one of the things that makes footage feel synthetic without anyone being able to say why.

Two fixes, both cheap:

• Add a small amount of motion blur in the editor. Resolve, Kdenlive and most compositors have it. Keep it light; overdone blur is worse than none.
• Interpolate up and then conform down, blending frames. Generating at 16, interpolating to 48, then rendering to 24 with frame blending gives a natural smear for free.

Conform the project rate before you import a single clip

This is the mistake that costs an afternoon.

Mixed frame rates on one timeline judder, because frames are being duplicated or dropped to fit the project rate. A 30 fps clip on a 24 fps timeline drops one frame in five, and on a slow pan that reads as a stutter you cannot un-see.

Decide the project rate first:

• 24 for anything meant to read as film.
• 25 if you are delivering for broadcast in a PAL region.
• 30 for most social platforms, which is also where 60 shows up for fast content.

Set it before importing. In DaVinci Resolve, changing project frame rate after media is on the timeline ranges from awkward to blocked depending on version, and re-conforming a finished cut is a genuine nuisance.

If a clip arrives at the wrong rate, retime it properly with optical flow rather than letting the timeline drop frames.

Odd durations

Models hand back clips at 5.1 or 4.8 seconds, because the latent frame count divided by the frame rate does not land on a round number. Nothing is wrong. Trim to what you need; you were going to trim the head and tail anyway.

The free path

Everything here is free. RIFE ships inside ComfyUI and inside Flowframes on Windows. FFmpeg will interpolate, conform and blend from the command line on any machine, including a very old one:

# conform 30 fps source to 24 fps with frame blending
ffmpeg -i in.mp4 -filter:v "minterpolate=fps=24:mi_mode=blend" out.mp4

Resolve’s free tier includes optical-flow retiming. Kdenlive and Shotcut handle conforming. On a phone, CapCut will change frame rate on export, though with less control.

Today: find out your model’s native frame rate from its documentation, then look at one of your own clips frame by frame at an occlusion edge and see whether the halo is there.