FYI, Michael committed a better fix to FFmpeg: http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=64b98df38910bfb921988a0be89da3038274232e
On Sat, Dec 21, 2013 at 6:47 PM, Luca Barbato <[email protected]> wrote: > On 22/12/13 02:27, Mason Carter wrote: > > Fix https://trac.ffmpeg.org/ticket/3204 > > > > The problem was that intensity compensation was always used once it was > > encountered. This is because v->next_use_ic was never set back to zero. > > To fix this, when resetting v->next_luty/uv, also reset v->next_use_ic. > > > > This improved (restored) performance by 85% when decoding > > http://bit.ly/bbbwmv > > --- > > libavcodec/vc1.c | 4 ++++ > > 1 file changed, 4 insertions(+) > > I'd use > > vc1: Fix intensity compensation performance regression > > Introduced by 28243b0d35b47bbf9abbd454fc444a6e0a9e7b71 > > Intensity compensation is always used once it was encountered, because > v->next_use_ic is never set back to zero. > > Reset v->next_use_ic, when resetting v->next_luty/uv. > > > It looks fine to me, and FATE passes. > > I'll wait for Kostya before pushing. > > Thanks a lot! > > lu > > _______________________________________________ > libav-devel mailing list > [email protected] > https://lists.libav.org/mailman/listinfo/libav-devel > _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
