DJI gyro data missing? The settings that make or break telemetry sync

Why DJI is different

Auto-sync does not watch your video for scenery. It reads a stream of motion samples — accelerometer and gyroscope — that the camera writes inside the MP4, and cross-correlates that against the motion your logger recorded: same bumps, same cornering forces, lined up in time. No motion stream, nothing to correlate.

A GoPro writes that motion track to almost every clip, under almost any setting. DJI does not. On a DJI camera the gyro is recorded only when the camera is set up a specific way — and the default, looks-great-out-of-the-box settings are exactly the ones that switch it off.

The rule is documented by Gyroflow, the open-source stabilizer that reads the same motion data: in-camera stabilization has to be disabled, and the field of view has to be set to Wide. Otherwise the camera records no gyro data at all. It is spelled out on Gyroflow's DJI camera page, and it is the single most common reason a DJI clip will not sync.

The pre-record checklist

Set these before the session. None of them can be fixed afterward — if the gyro was not written, it is not in the file.

1. Turn in-camera stabilization off. That means RockSteady, HorizonSteady, and any other EIS mode — all of it counts as the stabilization the rule refers to. (You add it back later; see the note below.)
2. Set the field of view — the lens or FOV setting — to Wide. Not Ultrawide, not Normal, not “Natural Wide.” Those lens modes do not give you usable gyro.
3. Check your camera can write gyro at all. Per Gyroflow's current list that includes the Osmo Action 4, Action 5 and Action 6, the Action 2 (on firmware v01.04.0510 or newer), the Osmo Nano, the Avata / Avata 2 / Neo drones, and the O3 / O4 Air Units. The Osmo Action 3 is the notable miss — it cannot embed gyro, and Gyroflow says it will not be supported. The original DJI FPV and the Osmo 360 are out too.
4. Update the camera's firmware. This matters most on the Action 2, where gyro recording only arrived in firmware v01.04.0510 — an older Action 2 writes nothing no matter how you set it up.
5. If you have done all of the above and a clip still comes back empty, some users report that shooting 16:9 rather than 4:3 gets the gyro to record. Worth checking, but treat it as a community workaround, not a documented rule.

How to check a clip you already shot

Three ways, fastest first.

Drop the clip into LapLift. In a modern browser the extractor reads the motion data straight off the file on your device — only the byte ranges it needs, so the video itself is never uploaded — and it tells you right away if there is no IMU data to find.

Run ExifTool from a terminal against the file:

exiftool -ee -G3 -api LargeFileSupport=1 YOURFILE.MP4

On a DJI clip that has gyro you will see sensor tags named dvtm_ac203, ac204 or ac206 (Action 4 / 5 / 6). If those tags are not there, the gyro was not recorded — no setting on the computer can add it back.

Or open it in Gyroflow. If Gyroflow cannot find gyro to stabilize with, a sync engine cannot either — it is reading the same data.

If you joined or edited the clips first

There is a second way to lose the gyro, and it has nothing to do with your camera settings: putting the footage through software before you bring it to LapLift. A DJI camera splits a long recording into several files, and it is a natural instinct to join them into one before uploading. That join re-encodes the video — and a re-encode writes a new file containing the picture and the sound, and nothing else. The gyro track is not copied across. Neither is anything else the camera embedded.

The result is a clip that plays perfectly and carries no motion data at all. This catches people out because every visible property of the file looks right: full length, full quality, correct frame rate. The part the gyro sync reads is the part you cannot see, and it is gone. Trimming, color grading, exporting a proxy and rendering out of any editor all do the same thing for the same reason. It is no longer a dead end, though — one thing a re-encode does keep is the sound, and if your session's data has an RPM channel, auto-sync falls back to matching the engine note against it (more below).

One clue that a file has been through an editor: the camera's own filename is usually lost with it. DJI writes names beginning DJI_, and an export from editing software typically arrives as something generic instead. A generic name is not proof — you can rename a file without touching its contents — but on a clip that will not sync it is a strong hint that the re-encode, not the camera settings, is what removed the gyro.

The ExifTool check above tells you for certain. Run it against the joined file and then against one of the originals: if the dvtm sensor tags appear on the original and not on the joined version, the software stripped them, and the originals are still good. Nothing can put the gyro back into the exported file, but you do not need to — sync the originals and edit afterwards.

What LapLift does — with the data and without it

When the gyro is there, sync is one click. LapLift pulls the camera's motion out in your browser, resamples it and your logger's motion to a common rate, and cross-correlates the two to find the offset. It scores how confident the match is on a 0–100 scale: at 60 or above it applies the offset for you, and at 80-plus it locks automatically. A weaker match is flagged as low-confidence so you can eyeball it before trusting it.

When the gyro is not there, LapLift listens instead. If your session's data includes an RPM channel, auto-sync falls back to matching the engine note in the video's audio against the RPM trace — an engine's pitch is physically locked to its revs, so the sound carries the same timing signal the gyro would have. This works on stabilized clips and edited exports precisely because sound survives the re-encode that strips the telemetry. Only the audio is sent for matching — a compact, downsampled stream, never the picture — and it is discarded as soon as the offset is found. The same confidence scale applies.

And if neither is available — no gyro and no RPM channel in your data — you place the sync by hand. Line up one obvious event (lights out, a hard braking marker), then fine-tune with the −0.1s / +0.1s nudge buttons or type an exact offset into the field, and lock it. Manual sync does not care what the camera or logger recorded; it only needs you to match a single moment.

Questions

Keep reading