Double-speed tutorials, half-speed replays, dreamy 0.5× B-roll, a 40-minute timelapse squeezed into 15 seconds. Changing playback speed is one filter — getting it to look right, with audio that doesn't chipmunk and motion that stays smooth, is the craft part.
The basic speed filter
```bash # 2x faster ffmpeg -i input.mp4 -filter_complex "[0:v]setpts=0.5*PTS[v];[0:a]atempo=2.0[a]" -map "[v]" -map "[a]" output.mp4 ```
Two halves must change together:
- **Video**: `setpts=0.5*PTS` — each frame's timestamp halves → playback runs 2×. For slow motion, `setpts=2.0*PTS` (factor >1 = slower). Speed factor = 1/your setpts multiplier. - **Audio**: `atempo=2.0` — audio tempo. Crucially, `atempo` changes speed **without** changing pitch (naive approaches make voices chipmunk). Range is 0.5-2.0 per instance; chain for more (`atempo=2.0,atempo=2.0` = 4×).
The common speeds
| Effect | Video | Audio | |---|---|---| | 2× speed-run | `setpts=0.5*PTS` | `atempo=2.0` | | 1.5× | `setpts=0.667*PTS` | `atempo=1.5` | | 0.5× slow-mo | `setpts=2.0*PTS` | `atempo=0.5` | | Timelapse 8× | `setpts=0.125*PTS` | usually drop audio |
Timelapse: the frame-dropping path
Long-duration timelapses (photo intervals sequences, hour-long recordings) compress better by dropping frames than by stretching timestamps:
```bash ffmpeg -i long.mp4 -vf "fps=24,setpts=0.25*PTS" -an timelapse.mp4 ```
`fps=24` first decimates to a fixed rate (from a 300-photo interval shoot or a 2-hour recording), then `setpts` maps the survivors into real-time pacing. File sizes shrink proportionally — an 8× timelapse is genuinely 1/8 the frames.
Slow motion that doesn't stutter
Digital slow-down repeats frames: 0.5× shows each frame twice — acceptable; 0.25× shows each four times — visibly choppy. Two remedies:
1. **Shoot at high frame rate** — the real fix. 60fps source at 0.5× still plays 30 effective fps; 120fps source at 0.25× stays buttery. This is why phones record "slo-mo" at 120/240fps. See our frame-rate guide for capture strategy. 2. **Interpolation** — `minterpolate` synthesizes in-between frames:
```bash ffmpeg -i in.mp4 -vf "minterpolate=fps=60:mi_mode=mci,setpts=2.0*PTS" slow.mp4 ```
Slow to render and occasionally invents artifacts on complex motion — but for 30fps sources it converts stutter into smoothness.
Audio below 0.5× — the limit and the workaround
`atempo` bottoms out at 0.5. Slower audio needs chaining (`atempo=0.5,atempo=0.5` = 0.25×), and quality degrades — below ~0.5× voices smear. Extreme slow-mo usually mutes audio anyway; `-an` and a music bed (see our add-music guide) is the standard treatment.
Ramps: speed that changes mid-clip
Editor territory — a clip that eases from 1× to 0.5× into the action beat. DaVinci Resolve and CapCut do drag-handle speed ramps natively; FFmpeg's route is cutting the clip into segments, applying a constant speed to each, and merging (see our merge guide). For occasional ramps, the GUI is genuinely the right tool.
The takeaway
`setpts` for video, `atempo` for audio — always both, never one. Shoot 60/120fps for slow-mo worth watching, drop frames for timelapse, chain `atempo` past 2×, and let timeline editors handle ramps. One command covers 90% of cases; craft covers the rest.
No comments yet