> has the issue been fixed for all branches an cases or is something
> missing that needs this ?
> (if so this needs a null pointer check i think)

This was fixed in a diffrent way in 6d9a46e884d090a68069112a3b0436aa8b563967

It forces the h264 decoder to be used, so the assumption it is in use is
allways correct.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to