[Ffmpeg-cvslog] CVS: ffmpeg/libavcodec vp3.c,1.64,1.65
Sat May 21 18:03:03 CEST 2005
Michael Niedermayer wrote:
> i can, and the md5 of the output changes which is what matters, the md5 must
> not change due to optimizations unless its fully understood why
> if this rule is ignored you quickly end up with a deeply broken mess which is
> very hard to debug and fix
This reminds me: When you deployed the loop filter, how did you even
know that the output was correct?
>>but performance actually seems
>>to go down with the optimizations enabled...
> you mean with this one too? the unconditional change to decoding all 3 planes
> at once instead of sequantially even if the user app doesnt support slices
> did already reduce the speed ...
Can I use the standard FFmpeg/MPlayer excuse and blame it on the compiler?
More information about the ffmpeg-cvslog