fix sharpness bug and clean up
sharpness was not recalculated in vp8cx_pick_filter_level_fast remove last_filter_type. all values are calculated, don't need to update the lfi data when it changes. always use cm->sharpness_level. the extra indirection was annoying. don't track last frame_type or sharpness_level manually. frame type only matters for motion search and sharpness_level is taken care of in frame_init move function declarations to their proper header Change-Id: I7ef037bd4bf8cf5e37d2d36bd03b5e22a2ad91db
This commit is contained in:
@@ -1030,14 +1030,6 @@ int vp8_decode_frame(VP8D_COMP *pbi)
|
||||
if (pbi->b_multithreaded_rd && pc->multi_token_partition != ONE_PARTITION)
|
||||
{
|
||||
vp8mt_decode_mb_rows(pbi, xd);
|
||||
if(pbi->common.filter_level)
|
||||
{
|
||||
/*vp8_mt_loop_filter_frame(pbi);*/ /*cm, &pbi->mb, cm->filter_level);*/
|
||||
|
||||
pc->last_frame_type = pc->frame_type;
|
||||
pc->last_filter_type = pc->filter_type;
|
||||
pc->last_sharpness_level = pc->sharpness_level;
|
||||
}
|
||||
vp8_yv12_extend_frame_borders_ptr(&pc->yv12_fb[pc->new_fb_idx]); /*cm->frame_to_show);*/
|
||||
}
|
||||
else
|
||||
|
||||
Reference in New Issue
Block a user