Opened 6 years ago

Closed 6 years ago

#1479 closed defect (fixed)

SCM/Spec mismatch in the processing order of merge candidate rounding and merge candidate bi-pred restriction

Reported by: rickxu Owned by:
Priority: major Milestone:
Component: HM SCC Version:
Keywords: Cc: jct-vc@…


In SCM8.5, after getInterMergeCandidates(), the merge candidate bi-pred restriction, i.e. xRestrictBipredMergeCand(), is done before the merge candidate rounding, i.e. roundMergeCandidates().
But in the Spec, the merge candidate list generation follows the below steps, where the bi-pred restriction should be done after the merge candidate rounding. This caused the inconsistence between SCM and Spec.

Step 1: Derive the merge candidates (step 1-8 in spec, and SCM function is getInterMergeCandidates())
Step 2: Round the merge candidates if needed (step 9 in spec, and SCM function is roundMergeCandidates())
Step 3: Disallow 8x4 and 4x8 bi-pred merge candidates(step 10 in spec, and the SCM function is xRestrictBipredMergeCand())
Step 4: Disallow bi-pred merge candidates for some 8x8 CUs (the below part in spec, and the SCM function is xRestrictBipredMergeCand())

When all of the following conditions are true, refIdxL1 is set equal to −1 and predFlagL1 is set equal to 0.
– predFlagL0 is equal to 1.
– predFlagL1 is equal to 1.
– nPbSw is equal to 8.
– nPbSh is equal to 8.
– TwoVersionsOfCurrDecPicFlag is equal to 1.
– noIntegerMvFlag is equal to 1.
– identicalMvs is equal to 0.

Change History (1)

comment:1 Changed 6 years ago by libin

  • Resolution set to fixed
  • Status changed from new to closed

fixed in r4925.

Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber, Participant

  • Bin Li(Participant)
  • jct-vc@…(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Always)
  • Lidong Xu(Reporter)