Hi Carl,
Thanks for your reply. Setting strict_std_compliance to 2 could help in
this case. However, as it is a global flag, it could influence other parts
in demuxers. It is preferable if we can have control of whether to use moov
in free with one separate flag.
Thanks,
Zhenni
On Mon, Oct 24, 2016 at 2:54 PM, Carl Eugen Hoyos <ceffm...@gmail.com>
wrote:
> 2016-10-24 23:11 GMT+02:00 Zhenni Huang <zhennihuang-at-google.com@
> ffmpeg.org>:
>
> [...]
>
> Does the following inlined patch help you?
>
> Carl Eugen
>
> diff --git a/libavformat/mov.c b/libavformat/mov.c
> index 357d800..ed099fc 100644
> --- a/libavformat/mov.c
> +++ b/libavformat/mov.c
> @@ -4884,6 +4884,7 @@
> a.type = avio_rl32(pb);
> if (a.type == MKTAG('f','r','e','e') &&
> a.size >= 8 &&
> + c->fc->strict_std_compliance < FF_COMPLIANCE_VERY_STRICT
> &&
> c->moov_retry) {
> uint8_t buf[8];
> uint32_t *type = (uint32_t *)buf + 1;
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
