Frame Rate Mismatch in Your Editing Timeline
Recording at 24fps and editing on a 30fps timeline causes judder. The editor has to repeat or drop frames to reconcile the two rates, and the result plays back with an uneven cadence. The reverse also causes problems: 60fps footage dropped into a 24fps timeline plays back fast unless you properly interpret it as slow motion.
The fix is to match your recording frame rate to your export frame rate from the start. If you're editing in 30fps and posting to YouTube, shoot at 30fps (or 60fps for slow motion). If you're targeting a cinematic 24fps look, shoot at 24fps and cut in a 24fps timeline. Changing frame rate in post without deliberately using it as a slow-motion effect produces stutter.
Note: NTSC (US, Japan) uses 30fps or 60fps. PAL (Europe, Australia) uses 25fps or 50fps. Mixing NTSC footage in a PAL timeline or vice versa causes a slight judder from 3:2 pulldown. Match your system to your region's standard.
Slow or Failing SD Card
4K/60fps video at full bitrate requires sustained write speeds of 100 MB/s or more. An SD card that can't keep up drops frames mid-recording. The result is stutter that appears consistently at the same points in each clip because the card falls behind during high-motion segments (fast panning, turbulent air) where bitrate spikes.
Minimum card specs for drone video:
- 4K/30fps: UHS Speed Class 3 (U3) or Video Speed Class V30, minimum 90 MB/s write
- 4K/60fps or D-Log: V60 or V90 rated card, 250+ MB/s write
- Always format the card in-camera, not on a computer, to maintain filesystem alignment
- Replace cards that show inconsistent write speeds (test with H2testw or SD Association's SD Memory Card Formatter)
Tip: If your footage is choppy in the same place every time you play it, but other clips from the same flight look fine, suspect SD card write failure at that specific timestamp. The card is fine for low-motion shots but drops frames during bitrate spikes.
Underpowered Playback and Editing Hardware
4K H.265 (HEVC) footage is computationally expensive to decode. An older laptop that struggles to play 4K footage in real time will show the footage as choppy even when the source file is perfectly recorded. This is a playback problem, not a recording problem. The raw file is fine; the computer can't keep up.
The fix is to create proxy files: lower-resolution versions of your footage that your editor uses during editing, then switches back to the originals for export. Premiere Pro, Final Cut Pro, and DaVinci Resolve all support proxy workflows. Alternatively, transcode the H.265 files to ProRes (on Mac) or DNxHD (on Windows) before importing, which trades file size for much faster decode performance.