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.

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, you are not stuck — 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 whether the camera recorded motion; it only needs you to match a single moment.

Questions

Keep reading