Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#571 closed defect (fixed)

wrong ME algorithm name given in configuration files

Reported by: chanduinece Owned by:
Priority: minor Milestone: HM-9.1
Component: HM Version: HM-7.0
Keywords: Cc: nalluri@…, fbossen, ksuehring, davidf, jct-vc@…

Description

In the configuration files (in folder /hevc/cfg/), under heading #====Motion Search=====, in the parameter "FastSearch", it is given as 0 for Full search and 1 for EPZS, in the comments. But technically this comment is wrong, as the Fast search algorithm used in HM is TZSearch algorithm that is implemented in MVC.
Basically these are the brief list of fast search algorithms in H.26x codecs.
H.264/AVC JM - EPZS,UMHexS,SUMHexS
H.264 MVC JMVM - TZSearch (or TZS algorithm)
Now in HM, the same algorithm that is implemented in JMVM is implemented, which is TZS. But from most of the JCTVC meeting files (example JCTVC D600, JCTVC B300), this is understood as EPZS algorithm and which is not (from file /source/Lib/TLibEncoder/TEncSearch.cpp).

Change History (4)

comment:1 Changed 9 years ago by DefaultCC Plugin

  • Cc fbossen ksuehring davidf jct-vc@… added

comment:2 Changed 9 years ago by ksuehring

  • Type changed from technical change to defect

This seems to be false categorized. Looks like a minor issue in a comment, not a required technical change that needs to be addressed at a meeting.

comment:3 Changed 9 years ago by ksuehring

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

fixed in r3112

comment:4 Changed 9 years ago by ksuehring

  • Milestone set to HM-9.1
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)
  • jct-vc@…(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Subscriber, Participant, Always)
  • nalluri@…(Subscriber)