Opened 12 years ago

Closed 12 years ago

#848 closed defect (wontfix)

Inter prediction semantic bugs

Reported by: laurent.birtz@… Owned by: bbross
Priority: minor Milestone:
Component: Text Version: D9 (K1003) v9
Keywords: Cc: bbross, wjhan, jct-vc@…

Description Derivation process for motion vector components and
reference indices

The process does not assign a value for mvL0 and mvL1 when their list is
unused. To my knowledge and unlike H.264, the HEVC specification does
not assume anywhere that the MV is null in that case but to be formal a
value should be assigned regardless. Prediction unit semantics

The value of "merge_idx" is unrestricted (not bounded by MaxNumMergeCand
anywhere as far as I can tell).

Change History (2)

comment:1 Changed 12 years ago by DefaultCC Plugin

  • Cc bbross wjhan jct-vc@… added

comment:2 Changed 12 years ago by bbross

  • Milestone HM-9.1 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Re: Derivation process for motion vector components and
reference indices
When the list is not used, the corresponding MV is not used too so there is not need to explicitly set the MV in that case, e.g. to zero.

Re: Prediction unit semantics
Reply from Minhua:
"In Table 9-32, it has
merge_idx TU, cMax = MaxNumMergeCand − 1
It somehow implies that merge_idx is restricted to [0: MaxNumMergeCand – 1]."

Thus, I consider this ticket as closed.

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

  • Benjamin Bross(Owner, Subscriber, Participant)
  • jct-vc@…(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Always)
  • laurent.birtz@…(Reporter)
  • Woo-Jin Han(Subscriber)