Opened 9 years ago

Last modified 5 years ago

#1427 reopened enhancement

(8-155) and (8-157) do not seem to be used

Reported by: jk73.kim Owned by:
Priority: minor Milestone:
Component: RExt text Version: v4 (12/2016)
Keywords: Cc: davidf, joel, teruhiko, jct-vc@…

Description

In "8.5.3.2.7 Derivation process for motion vector predictor candidates" (pp.144 in H.265-201504),

...
refIdxB = RefIdxLX[ xNbBk ][ yNbBk ] (8-155)
...
refIdxB = RefIdxLY[ xNbBk ][ yNbBk ] (8-157)

Becasue the corresponding candidate has no chance of MV-scaling,
refIdxB does not seem to be used in the following.

So, (8-155) and (8-157) can be removed.

Thanks.

Change History (2)

comment:1 Changed 7 years ago by bbross

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

The equations are in fact used, e.g. point 5. is still executed after 4. even when availableFlagLXB is equal to 1

comment:2 Changed 7 years ago by bbross

  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Type changed from defect to enhancement
  • Version changed from RExt D7 (Q1005) v8 to v4 (12/2016)

In fact, (8-155) and (8-157) could be removed as refIdxB set in 3. used in 5. is set again in 5. because availableFlagLXB is re-initialized to 0 in 5.

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(Participant)
  • David Flynn(Subscriber)
  • jct-vc@…(Subscriber)
  • JK Kim(Reporter)
  • Joel(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Always)
  • Teruhiko Suzuki(Subscriber)