Opened 11 years ago

Closed 11 years ago

#1152 closed defect (invalid)

TZ algorithm tests MVs outside the search range

Reported by: mohamed.chibani Owned by:
Priority: major Milestone: HM-12.1
Component: HM Version: HM-12.0
Keywords: Motion estimation Cc: fbossen, ksuehring, davidf, jct-vc@…


The range search is set relative to MV predictor in xMotionEstimation function, but when performing the diamond search in xTZSearch, the start point could be the MV predictor or the zero MV. In the later case, the start point could be outside the search range and some of the diamond points may still be tested.
Is this behavior intended ?

Change History (2)

comment:1 Changed 11 years ago by DefaultCC Plugin

  • Cc fbossen ksuehring davidf jct-vc@… added

comment:2 Changed 11 years ago by fbossen

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

The current behavior is likely the intended one.

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

  • David Flynn(Subscriber)
  • Frank Bossen(Subscriber, Participant)
  • jct-vc@…(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Subscriber, Always)
  • mohamed chibani(Reporter)