How to get telemetry off your GoPro, DJI, or Insta360

Overspeed reads embedded GoPro telemetry straight from the clip, and also imports CSV, Garmin FIT, and RaceLogic VBO logs that you sync to your footage. For a GoPro you do not need to do anything extra. For other action cameras the goal is to end up with a separate data file. Here is how to get one from the most common cameras.

GoPro

A GoPro records GPS and motion data inside the video as a GPMF metadata track, and Overspeed reads it automatically. Add the clip and it pulls out GPS, speed, altitude, and motion as a telemetry source you can sync on the timeline. No extractor, no separate file. If you would rather use a different log, you can still pair the clip with a lap timer CSV, a Garmin FIT file, or a phone GPS export instead.

DJI

DJI drones and Osmo cameras write a flight log, and many also lay an SRT subtitle track alongside the video that carries altitude, speed, and GPS. Export the flight record to CSV with a DJI log reader, or convert the SRT track to CSV. Either way you get a data file with the standard channels.

Insta360

Insta360 cameras record GPS when paired with the GPS action remote or a phone. Two things come out of Insta360 Studio: the flat, reframed video clip you plan to publish, and a telemetry export. Save the telemetry as a standard log you can bring in as CSV, and reframe the clip first so your overlay matches the footage you actually post.

Then build the overlay

1. Import the CSV, FIT, or VBO file. Overspeed maps speed, GPS, and the common channels automatically.
2. Load your video clip as a reference so you can see what you are syncing to.
3. Line the data up to a sharp event on the timeline, like a launch or a braking zone.
4. Style your gauges, then export the overlay on a chroma-key background.
5. Key the background out in your editor and the gauges sit on your footage.