From 07436abb86b3e2a981d563ecd628c1781004ebb7 Mon Sep 17 00:00:00 2001 From: Jingning Han Date: Mon, 27 Oct 2014 12:03:47 -0700 Subject: Use zero motion vector in choose_partitioning 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 | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) (limited to 'vp9/encoder') diff --git a/vp9/encoder/vp9_encodeframe.c b/vp9/encoder/vp9_encodeframe.c index 18a091220..baa4908d4 100644 --- a/vp9/encoder/vp9_encodeframe.c +++ b/vp9/encoder/vp9_encodeframe.c @@ -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; -- cgit v1.2.3