[FFmpeg-devel] [PATCH] lavf/mov.c: Fallback to finding non-keyframe in fix_index, if keyframe search fails.
derek.buitenhuis at gmail.com
Sat Nov 5 18:55:54 EET 2016
On 11/4/2016 9:53 PM, Sasi Inguva wrote:
> So, if I am not wrong, the only case when that would happen is, if edit
> list media time was < 0 . And that would be a corrupt MOV file, unless edit
> list media time = -1.
> I tried to create such a file with AtomInspector but it doesn't let me.
FWIW, this also used 'work'. I made an example file in a hex editor:
https://transfer.sh/OPAkZ/out.mp4.xz (URL is good for 14 days.)
Near as I can tell, negative entries in .mov are actually allowed,
since mov timestamps are signed (ISOBMFF's are unsigned).
My opinion is that this failure should go under explode mode (AV_EF_EXPLODE),
and by default adjust to the first timestamp, as long as it's possible/makes
sense. This is, of course, just my opinion. I hope someone else from FFmpeg
will reply and chime in with theirs.
More information about the ffmpeg-devel