]> granicus.if.org Git - libvpx/commitdiff
Use zero motion vector in choose_partitioning
authorJingning Han <jingning@google.com>
Mon, 27 Oct 2014 19:03:47 +0000 (12:03 -0700)
committerGerrit Code Review <gerrit@gerrit.golo.chromium.org>
Tue, 28 Oct 2014 02:38:43 +0000 (19:38 -0700)
The zero motion vector was effectively used in the subsampled pixel
based variance calculation. This commit makes it directly use zero
mv to generate prediction.

Change-Id: Ica83dc843e9f8da2f89c3ef451e50f16214c0def

vp9/encoder/vp9_encodeframe.c

index 18a091220f377d8c072d8813694f3d6492fa0d0b..baa4908d445295e12d2ba7115c1e388ffbe493f6 100644 (file)
@@ -467,7 +467,6 @@ static void choose_partitioning(VP9_COMP *cpi,
   int sp;
   int dp;
   int pixels_wide = 64, pixels_high = 64;
-  int_mv nearest_mv, near_mv;
   const YV12_BUFFER_CONFIG *yv12 = get_ref_frame_buffer(cpi, LAST_FRAME);
   const struct scale_factors *const sf = &cm->frame_refs[LAST_FRAME - 1].sf;
 
@@ -488,11 +487,7 @@ static void choose_partitioning(VP9_COMP *cpi,
 
     xd->mi[0].src_mi->mbmi.ref_frame[0] = LAST_FRAME;
     xd->mi[0].src_mi->mbmi.sb_type = BLOCK_64X64;
-    vp9_find_best_ref_mvs(xd, cm->allow_high_precision_mv,
-                          xd->mi[0].src_mi->mbmi.ref_mvs[LAST_FRAME],
-                          &nearest_mv, &near_mv);
-
-    xd->mi[0].src_mi->mbmi.mv[0] = nearest_mv;
+    xd->mi[0].src_mi->mbmi.mv[0].as_int = 0;
     vp9_build_inter_predictors_sby(xd, mi_row, mi_col, BLOCK_64X64);
 
     d = xd->plane[0].dst.buf;