Opened 11 years ago

Closed 11 years ago

#1175 closed defect (fixed)

Valid range for BvIntra

Reported by: peterderivaz Owned by:
Priority: major Milestone: RExt D5
Component: RExt text Version: RExt D4 (N1005) v3
Keywords: Cc: davidf, joel, teruhiko, jct-vc@…

Description

In the semantics for mvd_sign_flag the range for BvIntra[x0][y0] is defined to be in the range of 0 to 128.

However, this would mean that the Intra block copying prediction would be copying from pixels that have not yet been decoded.

The encoder software produces both positive and negative values for BvIntra, but I believe that the block that is copied is always restricted to:

  1. contain already decoded pixels
  2. only contain pixels from the current CTU or the CTU to the left.

What is the correct valid range for BvIntra?

Change History (2)

comment:1 Changed 11 years ago by DefaultCC Plugin

  • Cc davidf joel teruhiko jct-vc@… added

comment:2 Changed 11 years ago by davidf

  • Milestone set to RExt D5
  • Resolution set to fixed
  • Status changed from new to closed

Resolved by adoptions (JCTVC-O0183) from Geneva that have codified the restriction:

  • Don't reference anything outside current CTU + Left CTU,
  • Don't reference anything outside current slice/tile,
  • Don't reference anything within the current CU being reconstructed.
  • Prohibit IntraBC from referencing samples outside the current picture

In addition to not referencing future samples.

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, Participant)
  • jct-vc@…(Subscriber)
  • Joel(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Always)
  • Peter de Rivaz(Reporter)
  • Teruhiko Suzuki(Subscriber)