On Fri, Dec 02, 2016 at 01:51:24PM +0100, Timo Rothenpieler wrote: > These paths can be taken when the actual underlying codec is not h264, > but the user forces, for example via ffmpeg command line, a specific > input decoder that happens to be a h264 decoder. >
> In that case, the codecpar codec_id is set to h264, but the internal > avctx is the one of, for example, an mpeg2 decoder, thus crashing in > this function. Is it just me or is this completely inconsistent? the codec id told to the user is h264 while we internally use a mpeg2 decoder to analyze it ? If its h264 (as forced by the user) we should use a h264 decoder to internally analyze it [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Many things microsoft did are stupid, but not doing something just because microsoft did it is even more stupid. If everything ms did were stupid they would be bankrupt already.
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
