Wrong HMVP table size

[lizhang]

The HMVP table size is fixed to be 5 as in the software and JVET-M0436, but the specification uses (maximum merge number - 1) which will cause mismatch between SW and specification when maximum merge number is less than 6.

Suggested fixes are as follows:

In sub-clauses 8.6.2.6 and 8.5.2.16 for the Updating process for the history-based motion vector predictor candidate list, replace the "MaxNumMergeCand − 1" by 5.

[ccc2384823]

I agree that it's reasonable to do VTM / WD alignment as your discussion

But, I think maybe a new proposal to fix it may be better.
It's suggested that maybe a new proposal will be needed ( instead of using ticket to do normative change) for this issue in next JVET meeting.

Thanks!

ChunChia from MediaTek

[LiZhang]

Please note that using fixed table size is what has been adopted. You may refer to the following meeting notes:

Reduce HMVP number from 6 to 5

In addition, the specification is not aligned with the software. I don't think it is necessary to make a proposal to fix typos.

[bbross]

Fixed in D5 v8