Frame Rates and Slow Motion - How Capture and Playback Rates Work

What You Need to Know

Frame rate is the number of discrete images (frames) captured or shown per second. Slow motion is not magic in post: it’s usually the result of capturing more frames per second than you play back.

Two rates matter:

• Capture frame rate (camera acquisition, e.g., $120\,\text{fps}$)
• Playback (delivery/timeline) frame rate (what the viewer sees, e.g., $24\,\text{fps}$)

Core rule:

• If capture fps > playback fps, the footage can be played back slower with real frames, i.e., smooth slow motion.
• If capture fps = playback fps, you get real-time motion.
• If capture fps < playback fps, you must speed up playback or create/interpolate frames to fill gaps.

Why this matters in video production:

• It controls motion portrayal (cinematic “strobing” vs smooth motion).
• It determines whether slow motion will be clean (true HFR) or artifact-prone (interpolated).
• It interacts with shutter speed/angle, affecting motion blur (often the #1 thing students forget).

Critical reminder: Slow motion quality is primarily decided on set (capture fps + shutter + lighting), not fixed later.

Step-by-Step Breakdown

A. Planning slow motion (the reliable workflow)

1. Lock your delivery/playback frame rate

   • Choose based on project requirements (common: $23.976$, $24$, $25$, $29.97$, $30$, $50$, $59.94$, $60$).

2. Decide your target slow-motion amount

   • Example: “I want $4\times$ slower than real time.”

3. Choose a capture frame rate that supports that slow-down

   • Use the slow-motion factor formula (below).
   • Prefer capture fps that is an integer multiple of playback fps when possible (cleaner conforming).

4. Set shutter speed (or shutter angle) appropriately

   • For “natural” motion blur, approximate the 180° shutter rule:
     $t_{shutter} \approx \frac{1}{2\,f_{capture}}$
     Example: at $120\,\text{fps}$, use about $\frac{1}{240}\,\text{s}$.

5. Check flicker risk (lighting + screens)

   • Your shutter time and capture fps must play nicely with mains frequency:
     • Regions with $50\,\text{Hz}$ power: common safe shutter times $\frac{1}{50}$, $\frac{1}{100}$, $\frac{1}{200}$, …
     • Regions with $60\,\text{Hz}$ power: common safe shutter times $\frac{1}{60}$, $\frac{1}{120}$, $\frac{1}{240}$, …
   • High fps often forces short shutter times that can reveal flicker.

6. In post, conform/interpret footage to the timeline fps

   • Conform/Interpret (true slow motion): treat the clip as if it was shot at playback fps.
   • Speed change (retime): explicitly set speed percentage; can be equivalent if done correctly, but interpret/conform is often cleaner.

B. Worked mini-example (end-to-end)

• Delivery: $24\,\text{fps}$
• Desired: $5\times$ slow motion
• Choose capture fps:
  $f_{capture} = 5\times 24 = 120\,\text{fps}$
• Shutter (180° look):
  $t_{shutter} \approx \frac{1}{2\times 120} = \frac{1}{240}\,\text{s}$
• Post: interpret/conform $120\,\text{fps}$ footage as $24\,\text{fps}$ to get smooth $5\times$ slow motion.

Key Formulas, Rules & Facts

A. The slow-motion math (must-know)

B. Shutter speed/angle essentials (slow motion’s best friend)

Practical consequences:

• Higher capture fps usually means less light per frame (shorter shutter time), so you often need more light or higher ISO.
• Too slow a shutter at high fps can make slow motion look smeary.
• Too fast a shutter can make motion look choppy/staccato (sometimes desired).

C. Common real-world frame rates (know the landscape)

Tricky but important: $23.976$, $29.97$, and $59.94$ are **not** the same as $24$, $30$, and $60$. Small mismatch, big sync headaches.

D. “True” slow motion vs “fake” slow motion

Examples & Applications

Example 1: Classic slow motion (integer multiple)

You deliver at $24\,\text{fps}$ and shoot at $120\,\text{fps}$.

• Slow-motion factor:
  $S = \frac{120}{24} = 5$
• Result: $5\times$ slower than real time.
• Equivalent speed setting:
  $\%\text{speed} = 100\times\frac{24}{120} = 20\%$
  Key insight: This is “clean” slow motion because every playback frame is a real captured frame.

Example 2: Broadcast-friendly slow motion

You deliver at $29.97\,\text{fps}$ and capture at $119.88\,\text{fps}$ (many cameras label this as $120\,\text{fps}$ in NTSC mode).

• If your camera is truly shooting $119.88$:
  $S = \frac{119.88}{29.97} = 4$
• Result: exact $4\times$ slow motion.
  Key insight: Match fractional with fractional (NTSC family) to avoid drift.

Example 3: Duration planning (how long will the slow-mo clip be?)

You record $6\,\text{s}$ of real action at $240\,\text{fps}$ for a $24\,\text{fps}$ timeline.

• New duration:
  $T_{new} = 6\times\frac{240}{24} = 60\,\text{s}$
  Key insight: High fps rapidly creates very long clips. Plan performance/action length accordingly.

Example 4: When you didn’t shoot HFR (what can you realistically do?)

You shot at $24\,\text{fps}$ but want $50\%$ speed (i.e., $2\times$ slower).

• Needed capture fps for clean slow motion would have been:
  $f_{capture} = 2\times 24 = 48\,\text{fps}$
• Since you only have $24\,\text{fps}$, you must use frame blending or optical flow.
  Key insight: You can slow down, but you’re now trading off artifacts vs stutter.

Common Mistakes & Traps

1. Mixing up capture fps and playback fps

   • Wrong move: using timeline fps when calculating shutter or frame counts.
   • Why wrong: motion blur and exposure are determined by capture timing.
   • Fix: use $f_{capture}$ for shutter decisions; use $f_{playback}$ for delivery math.

2. Assuming “120 fps” always means true $120\,\text{fps}$

   • Wrong move: shooting “120” in an NTSC project but treating it as exactly $120$.
   • Why wrong: many systems use $\frac{120}{1.001} \approx 119.88$.
   • Fix: verify the camera/project is in $23.976/29.97/59.94$ vs $24/30/60$ family and match accordingly.

3. Forgetting shutter speed/angle when going HFR

   • Wrong move: shooting $120\,\text{fps}$ at $\frac{1}{50}\,\text{s}$ because it “exposes nicely.”
   • Why wrong: that’s effectively a very large shutter angle, causing excessive blur per frame.
   • Fix: start near $\frac{1}{240}\,\text{s}$ for $120\,\text{fps}$ if you want the conventional look, then adjust intentionally.

4. Creating flicker by choosing a shutter time that fights your lighting

   • Wrong move: picking arbitrary shutter times at high fps under LED or fluorescent lights.
   • Why wrong: many lights modulate intensity; certain shutter times sample that modulation badly.
   • Fix: test and choose shutter times aligned to local mains frequency (common safe sets: multiples of $\frac{1}{50}$ or $\frac{1}{60}$).

5. Thinking higher fps automatically looks “more cinematic”

   • Wrong move: shooting everything at $60\,\text{fps}$ and delivering at $60\,\text{fps}$ expecting a film look.
   • Why wrong: higher playback fps tends to look hyper-real; “cinematic” motion is often associated with $24$-ish playback and its motion blur/judder characteristics.
   • Fix: decide the look first (playback fps), then capture fps only as needed.

6. Retime in post without understanding what the NLE is doing

   • Wrong move: slowing footage and assuming it’s using real frames.
   • Why wrong: if $f_{capture}$ wasn’t high enough, the software may be duplicating frames or interpolating.
   • Fix: confirm whether you’re conforming HFR (best) or interpolating (artifact risk).

7. Audio expectations mismatch

   • Wrong move: expecting usable synced audio from extreme HFR modes.
   • Why wrong: many HFR/overcrank modes record no audio or audio becomes unusable when conformed.
   • Fix: plan separate audio or accept that HFR takes are often MOS.

8. Non-integer conversion surprises (judder/uneven cadence)

   • Wrong move: placing $30\,\text{fps}$ footage on a $24\,\text{fps}$ timeline without planning.
   • Why wrong: it requires uneven frame mapping (or interpolation), which can introduce cadence judder.
   • Fix: shoot to match delivery family when you can, or plan a proper conversion method.

Memory Aids & Quick Tricks

Quick Review Checklist

• You can explain the difference between capture fps and playback fps.
• You can compute slow motion using:
  • $S = \frac{f_{capture}}{f_{playback}}$
  • $\%\text{speed} = 100\times\frac{f_{playback}}{f_{capture}}$
• You remember that conformed HFR slow motion uses real frames (clean), while slowing normal fps often needs interpolation (artifacts).
• You set shutter using capture fps (often near $180^{\circ}$):
  $t_{shutter} \approx \frac{1}{2\,f_{capture}}$
• You watch out for flicker when shutter times clash with $50\,\text{Hz}$ or $60\,\text{Hz}$ lighting.
• You avoid accidental mismatches between $24$ vs $23.976$ (and $30$ vs $29.97$, $60$ vs $59.94$).
• You can predict duration changes:
  $T_{new} = T_{real}\times\frac{f_{capture}}{f_{playback}}$

You’ve got this: if you can do the ratio math and remember shutter is tied to capture fps, you’re exam-ready.