[FFmpeg-user] Problem recovering MOV recording from SSD

Dave Rice dave at dericed.com
Mon Nov 25 18:19:17 CET 2013

Hi Jarrod,
It sounds as though the file is truncated and missing the usual mov indexing from the end of the file. If its feasible to access an earlier copy of the file that may work well. Else I've had some luck piping a data stream starting from the offset of the moov atom's data payload into ffmpeg while providing codec, size, and frame rate as input options. The idea here is to pipe the video data stream of the mov into ffmpeg and ignore the broken container format.
Dave Rice

On Nov 25, 2013, at 10:33 AM, Jarrod Maloley <jarrod.maloley at gmail.com> wrote:

> Good morning,
> I was wondering if someone would be able to help with an odd issue I'm
> experiencing. Basically a client came to me with a recording(ProRes422, MOV
> container) from a blackmagic hyperdeck that I can't seem to open. The MOV
> is about 24 GB in size so it seems there is information there. I have tried
> some basic hex editing as well as trying ffmpeg to convert the file with no
> success. Here is a link to a .txt of the actual
> hexcode<https://dl.dropboxusercontent.com/u/66298336/Capture0001.txt>.
> Any insight at all would be greatly appreciated. Thank you!!
> Jarrod
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

More information about the ffmpeg-user mailing list