On 12.06.2015 22:03, Hendrik Leppkes wrote: > On Fri, Jun 12, 2015 at 10:01 PM, Andreas Cadhalpun > <andreas.cadhal...@googlemail.com> wrote: >> That's not currently documented, so it would effectively be an API change. >> And since the h264 decoder is the only one misbehaving in this way, >> fixing it is the better alternative. >> > > If you would have actually fixed it. But you didn't. You're hiding the > problem under a layer of hacks.
It is fixed for the API users, who don't care about the way it's implemented. If you know of a better/simpler way to fix it, please go for it. But letting the problem persist is no good alternative. Best regards, Andreas _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel