summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJingning Han <jingning@google.com>2019-05-08 13:16:10 -0700
committerJingning Han <jingning@google.com>2019-05-08 13:16:10 -0700
commit0df9a18edfe5969a3981ac65b7034480f36e8fe9 (patch)
tree0985b94d6987385ac59f997fc5b6c3e805583852
parent1e2cfa3f0f75c971ccceb9be0e818b207c86303b (diff)
downloadlibvpx-0df9a18edfe5969a3981ac65b7034480f36e8fe9.tar
libvpx-0df9a18edfe5969a3981ac65b7034480f36e8fe9.tar.gz
libvpx-0df9a18edfe5969a3981ac65b7034480f36e8fe9.tar.bz2
libvpx-0df9a18edfe5969a3981ac65b7034480f36e8fe9.zip
Fix key frame detection
This solves the regression issue seen in certain animation clips. BUG=b/132108583 Change-Id: Ib28413c95160a5f15fbcf9ea6a322fd4f69a57ce
-rw-r--r--vp9/encoder/vp9_firstpass.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/vp9/encoder/vp9_firstpass.c b/vp9/encoder/vp9_firstpass.c
index d8c6da113..2d0860247 100644
--- a/vp9/encoder/vp9_firstpass.c
+++ b/vp9/encoder/vp9_firstpass.c
@@ -2827,7 +2827,7 @@ static int test_candidate_kf(TWO_PASS *twopass,
// See above for an explanation of the test criteria.
// If so, then examine how well it predicts subsequent frames.
if (!detect_flash(twopass, -1) && !detect_flash(twopass, 0) &&
- (next_frame->pcnt_second_ref < SECOND_REF_USEAGE_THRESH) &&
+ (this_frame->pcnt_second_ref < SECOND_REF_USEAGE_THRESH) &&
((this_frame->pcnt_inter < VERY_LOW_INTER_THRESH) ||
(slide_transition(this_frame, last_frame, next_frame)) ||
(intra_step_transition(this_frame, last_frame, next_frame)) ||