Adjust bounds checking for hex search in real-time mode
authorYunqing Wang <yunqingwang@google.com>
Thu, 2 Jun 2011 21:33:17 +0000 (17:33 -0400)
committerYunqing Wang <yunqingwang@google.com>
Fri, 3 Jun 2011 12:53:42 +0000 (08:53 -0400)
commite5c236c21011c668c6b521dc4e554dbf91a161fe
tree1d3a47290354da8a4c29869775175f28bd0f7baa
parent4ce6928d5b048ce5f82a97cd3d56267432fdc634
Adjust bounds checking for hex search in real-time mode

Currently, hex search couldn't guarantee the motion vector(MV)
found is within the limit of maximum MV. Therefore, very large
motion vectors resulted from big motion in the video could cause
encoding artifacts. This change adjusted hex search bounds
checking to make sure the resulted motion vector won't go out
of the range. James Berry, thank you for finding the bug.

Change-Id: If2c55edd9019e72444ad9b4b8688969eef610c55
vp8/encoder/pickinter.c