14
5
I was shooting video with a Canon EOS 7D, and it was telling me the battery (I thought) was getting hot, so I opened the battery cover and it promptly shut off. It was a battery pack, and the batteries stayed in place even though it shut off. So now I have a 1.4 GB file that even ffmpeg cannot read. I have plenty of other files shot with the exact same format that I could look off of to read the data if I needed to, but how do I do that.
ffmpeg -i on the bad file:
[mov,mp4,m4a,3gp,3g2,mj2 @ 000001572b9fa3a0] moov atom not found
MVI_3891.MOV: Invalid data found when processing input
ffmpeg -i on a good file:
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'MVI_3892.MOV':
Metadata:
major_brand : qt
minor_version : 537331968
compatible_brands: qt CAEP
creation_time : 2016-01-28 12:04:16
Duration: 00:12:10.86, start: 0.000000, bitrate: 46897 kb/s
Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuvj420p(pc, smpte170m/bt709/bt709), 1920x1080, 45357 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 60k tbc (default)
Metadata:
creation_time : 2016-01-28 12:04:16
Stream #0:1(eng): Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 1536 kb/s (default)
Metadata:
creation_time : 2016-01-28 12:04:16
7Close voters: just because the situation was created by a camera (not a general purpose computer) doesn't mean that trying to repair the file is off-topic. I'm voting to Leave Open. – Ben N – 2016-01-30T01:56:30.857
See the other question which explains how to use
untrunc
to recover the file. – slhck – 2016-01-30T18:00:56.957@slhck, will this work with MOV? – Arlen Beiler – 2016-01-30T18:07:43.907
I think the key bit is the phrase "Missing moov atom". Have a look at this post which talks about Untrunc According to this post AtomicParsley may be able to fix it as well.
– davidgo – 2016-01-30T05:51:51.243MOV and MP4 are very closely related. MP4 is historically based on MOV. This should work for MOV files as well. If not, let me know. – slhck – 2016-01-30T18:30:34.300