DJI / FPV / dashcam .ts won't play right or import? Here's why.

DJI goggles, FPV DVRs and most dashcams record MPEG-TS — a broadcast container built to survive signal drops, not to sit on an editing timeline. That's why VLC kind of plays it, but Premiere, Resolve and Final Cut choke.

What's actually wrong with these files

• Timestamps start at a random offset and can jump after dropped packets (FPV signal loss, dashcam power dips).
• Variable frame rate — editors expect constant fps; VFR causes audio drift and stuttering on the timeline.
• Broken packets mid-stream make strict players bail out entirely.
• No fast-start index — scrubbing and thumbnails are slow or broken.

The fix: rebuild it into a clean .mp4

ClipMend's REPAIR mode (macOS) does this in one pass, locally:

1. Drop the .ts file → Analyze. The free diagnosis lists exactly what's wrong with this specific file — timecodes, VFR, start offset, broken packets.
2. ClipMend auto-builds the repair plan: rebuild timecodes · constant fps · zero the start offset · skip broken packets · fast-start · keep color tags. You can toggle any step off.
3. Press Repair — out comes a clean .mp4/.mov (H.264, H.265 or ProRes — your choice) that imports into any editor.

Crash clip cut off mid-recording?

Dashcam accident clips often end abruptly — power cut at the moment you need the footage most. The frames up to the cut are recoverable: ClipMend salvages the playable part. And because everything runs locally on your Mac, evidence footage never touches anyone's server.

FAQ