By Lucas, founder of FixMyVideos · Updated

DJI Osmo Action 4 Corrupted Video: Why It Won't Play, and What Comes Back

An Osmo Action 4 gets used where electronics have a hard time: in water, in the cold, on a bike, on a helmet that hits the ground. When a recording goes wrong it nearly always goes wrong the same way. The camera stops before it has finished the file, and you are left with an .MP4 of a plausible size that no player will open.

This page explains what is actually missing from that file, what you can try for free, and what we measured when we recovered two damaged clips from one Osmo Action 4.

What the camera writes, and what goes missing

An MP4 has two parts. The pictures and the sound go into one big block as they are recorded. The index, which says where each picture starts, how long it is and how fast to play them, is written last, when you press stop. Cut the power before that (a battery dying in the cold, a crash, a card knocked loose, a housing that leaks) and the pictures are on the card while the index is not. Players need the index, so they refuse the file. Tools report it as moov atom not found.

The pictures are still there, but finding them without an index is harder on an Osmo Action 4 than on most cameras, because the camera writes other things between them:

  • A small telemetry record between every two pictures. On the clips we measured these were about 130 bytes or about 1 KB each, and they do not all start with the same byte.
  • Large blocks every so often. These are most likely the low resolution copy the camera keeps for previews. On our two clips they ranged from about 115 KB to 2.2 MB.
  • Each picture stored in two pieces (two slices), one after the other.

A recovery tool has to walk the raw data and decide, at each step, where the next real picture begins. The video on these clips is HEVC with a keyframe only every 30 pictures, and every picture in between depends on the one before it. So a tool that skips one picture does not lose one picture. Everything after it, up to the next keyframe, can no longer be decoded.

What to try first, for free

  1. Stop recording on that card. Every new clip can land on top of the data you want back.
  2. Copy the whole card to a computer before anything else, and work on the copy. Do not let the camera or a computer offer to format or repair the card.
  3. Put the card back in the camera and switch it on. Some cameras close an interrupted recording at power up. If the clip now shows in playback, copy it again.
  4. Try VLC. It is free and more forgiving than the players built into Windows and macOS. If VLC plays the clip from start to end, the file is not badly damaged.
  5. Try untrunc, which is free, if you have a healthy clip from the same camera in the same mode (same resolution, same frame rate). It rebuilds an index by copying the structure of the healthy clip. Check the result all the way through, not only the first seconds.

What we measured on two real Osmo Action 4 clips

Two clips came to us from the same Osmo Action 4, both cut off before the camera wrote the index: a short clip of about one second and a longer one of about eight seconds, recorded at 59.94 frames per second.

It took two passes to see everything that goes wrong on this camera. The first try delivered nothing: it stopped and asked for a reference clip. A later repair played, but stuttered. Between them, they hit the common traps:

  • About a quarter of the pictures were missed on the first try. The tool skipped any picture followed by a telemetry record whose first byte it had not met yet. On the short clip it found 51 of 67 pictures, on the longer one 361 of 480.
  • The later repair still missed every picture in front of a large block, because the search for the next picture did not reach past a block of a megabyte or more. On the longer clip that was 13 pictures, one of them a keyframe.
  • Missed pictures cost whole runs of frames. On the longer clip, those 13 missing pictures made 190 more undecodable. The file played, but stuttered: the player holds the last good frame each time it meets a picture it cannot decode, and ffmpeg reported no error at all.
  • The frame rate nearly came out wrong. The clip's own timing said 59.94 frames per second. A later step dropped that measurement, and the file would have played at half speed.

We fixed each of those in the engine. Measured afterwards, with no reference clip at all:

ClipPictures in the fileFrames that play, stuttering repairFrames that play now
About 1 second673652
About 8 seconds480277399

Both now match what you get by decoding every picture on the card in order, which is the most any tool can reach. The short clip is now complete. On the longer one, the 81 frames that still do not play were damaged on the card itself, inside the source, so no repair can bring them back. Both deliveries play at 59.94 frames per second.

The check that matters here is counting frames, not asking whether the file opens. The stuttering repair opened fine in every player and passed a standard ffmpeg decode test. Only comparing the frames that actually decode with the pictures in the file showed that 4 in 10 never appeared on screen.

When the clip cannot be recovered

  • The card only holds zeros where the clip should be. That happens after a format, or when the card failed while writing. There are no pictures left to find.
  • The clip is a few kilobytes, or shows a size but its content is empty. The recording never reached the card.
  • The damage sits inside the pictures themselves. Then you get back what survived, like the 81 lost frames above, and nothing more. The free preview shows you which case you are in before you pay anything.

If the card itself was damaged (water, a cracked card, a card the computer no longer sees), that is a card recovery job first. Run a card recovery tool such as PhotoRec, then send us the file it extracts.

Getting your clip back

Upload the Osmo Action 4 file, up to 150 GB. You get a free 5-second preview from your own footage within a few minutes, no reference clip needed. You pay only once the preview shows your footage, and the price for your file's size is shown before you pay. Uploads are deleted automatically after 48 hours.

FAQ

Does this apply to the Osmo Action 3 and Action 5 Pro too? They record to MP4 the same way, with the index written at the end, so an interrupted recording fails the same way. The two clips measured on this page came from an Action 4.

My repaired Osmo Action video plays but stutters. Why? Usually because the repair missed some pictures. Each missing picture makes the frames after it undecodable until the next keyframe, and the player freezes on the last good frame. Count the frames: if far fewer decode than the file holds, try another repair before you give up on the clip.

The repaired clip plays in slow motion, or too fast. Is the footage ruined? No. The pictures are fine and the playback speed is wrong, because the repair guessed the frame rate instead of reading it from the clip. Our page on video playing at the wrong speed explains it.

Do I need a reference clip from my camera? Not for these two clips: both came back without one. A healthy clip from the same camera and mode can still help a free tool like untrunc.

My clip was filmed underwater and the card got wet. Can it be saved? If the computer still reads the card, copy everything off it now and work on the copy. If it does not, the card needs recovering before the video can be repaired.

What happens to my file after upload? It is used only to analyse and repair your clip, and it is deleted automatically after 48 hours. The details are on the privacy page.

Related

Upload your Osmo Action 4 file →

Free preview · No commitment

Ready to recover your video?

Upload your file and get a free 5-second preview in about a minute. Pay only if the preview looks right.

Upload your file →