From 50f112c91535b2f1fca1f5e96aa434a08af54633 Mon Sep 17 00:00:00 2001 From: Peter Cordes Date: Mon, 2 Mar 2015 22:57:30 -0400 Subject: avfilter/vf_mpdecimate: debug logging of threshold stats It's often really helpful to know why a frame wasn't decimated (lo or hi), and how much you exceeded the threshold by, if you're trying to tweak the thresholds to get what you want. mpdecimate already prints a line per input frame with -v debug, this just makes it longer. Signed-off-by: Peter Cordes --- libavfilter/vf_mpdecimate.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'libavfilter/vf_mpdecimate.c') diff --git a/libavfilter/vf_mpdecimate.c b/libavfilter/vf_mpdecimate.c index 5c41de7992..429121d33d 100644 --- a/libavfilter/vf_mpdecimate.c +++ b/libavfilter/vf_mpdecimate.c @@ -84,15 +84,21 @@ static int diff_planes(AVFilterContext *ctx, for (x = 8; x < w-7; x += 4) { d = decimate->sad(cur + y*cur_linesize + x, cur_linesize, ref + y*ref_linesize + x, ref_linesize); - if (d > decimate->hi) + if (d > decimate->hi) { + av_log(ctx, AV_LOG_DEBUG, "%d>=hi ", d); return 1; + } if (d > decimate->lo) { c++; - if (c > t) + if (c > t) { + av_log(ctx, AV_LOG_DEBUG, "lo:%d>=%d ", c, t); return 1; + } } } } + + av_log(ctx, AV_LOG_DEBUG, "lo:%d<%d ", c, t); return 0; } -- cgit v1.2.3