Opened 8 years ago

Closed 8 years ago

#1178 closed defect (fixed)

Use of cu_transquant_bypass_flag in controlling intra prediction

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 8.4.4.2.6 Specification of intra prediction mode in the range of INTRA_ANGULAR2.. INTRA_ANGULAR34, equation 8-54 is only triggered if cu_transquant_bypass_flag is equal to 0. In previous versions of the specification, there was no mention of cu_transquant_bypass_flag in this part.

This seems an odd change because:

  1. It appears to break backwards compatability for Main and Main10 profile
  2. The corresponding code at line 263 of TCompPrediction.cpp makes no mention of this extra condition:

const Bool edgeFilter = isLuma(channelType) && (width <= MAXIMUM_INTRA_FILTERED_WIDTH) && (height <= MAXIMUM_INTRA_FILTERED_HEIGHT);

Can someone clear up my confusion on this point?

Change History (2)

comment:1 Changed 8 years ago by DefaultCC Plugin

  • Cc davidf joel teruhiko jct-vc@… added

comment:2 Changed 8 years ago by davidf

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

Fixed in O1005v1 based on adoption of JCTVC-O0147

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)