On Wed, Aug 13, 2014 at 04:02:57PM +0200, Michael Niedermayer wrote: > On Sun, Aug 10, 2014 at 10:09:02PM +0200, Clément Bœsch wrote: > > --- > > I have one or two little things to cleanup after this but I think I'm mostly > > done. The filter is now usable from a performance point of view (not for > > real-time, but it doesn't decades to process a normal sized image anymore): > > > > Stream #0:0: Video: png, rgb24, 1445x1080, 25 tbr, 25 tbn, 25 tbc > > > > ./ffmpeg-2.3 -i in.png -vf dctdnoiz=15 -f null - 38.34s user 0.01s system > > 98% cpu 39.124 total > > ./ffmpeg -i in.png -vf dctdnoiz=15 -f null - 5.06s user 0.02s system 621% > > cpu 0.817 total > > > > I will mention this stuff in the Changelog when this is accepted. > > > > Ideally, I'd really love to have a FATE test, but I see no such thing as > > "threshold" video tests for avfilter in FATE in order to support float-based > > filters. Another solution as already is to make dctdnoiz integer-only but > > I'm > > not planing to do that anytime soon. > > --- > > libavfilter/vf_dctdnoiz.c | 114 > > ++++++++++++++++++++++++++++++++++------------ > > 1 file changed, 84 insertions(+), 30 deletions(-) > > LGTM >
Thanks, applied -- Clément B.
pgpZreMmG9N9w.pgp
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
