Ok. i'll drop this patch . Does outputting stream DURATION values in matroskaenc.c as string tag's , (same as mkvmerge does ) seem ok? Atleast then, I can parse those string metadata in our own video pipeline which will solve my use case.
On Sat, Aug 1, 2015 at 11:42 AM, wm4 <nfx...@googlemail.com> wrote: > On Sat, 1 Aug 2015 11:11:14 -0700 > Sasi Inguva <is...@google.com> wrote: > > > Also I can check if the stream duration values are sane, by checking that > > they are less than the total duration of the file. > > Wouldn't change much - they could be too short too, and we couldn't > detect this situation. > > This is simply an unreliable value. (I'm not even sure if we should > export it as stream duration at all, but on the other hand the file > duration can be unreliable anyway.) > _______________________________________________ > 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
