Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#1203 closed defect (fixed)

Binarisation for log2_res_scale_abs_plus1 and cu_chroma_qp_adjustment_idc

Reported by: peterderivaz Owned by:
Priority: minor Milestone: RExt D5
Component: RExt text Version: RExt D5 (O1005) v1
Keywords: Cc: davidf, joel, teruhiko, jct-vc@…

Description

  1. In section 7.4.9.12 log2_res_scale_abs_plus1 is defined. Should these semantics also specify the legal range for the symbol?
  1. In Table 9-34 the encoding for log2_res_scale_abs_plus1 is set to TR with cMax=3, and cRiceParam=0. I believe this means that it will use at most 3 bins to decode the symbol, however table 9-39 defines values for 4 choices of binIdx. I suspect the last entry can be deleted.
  1. cu_chroma_qp_adjustment_idc is a multibit symbol, but Table 9-34 only defines a ctxInc for a binIdx of 0. It is not clear whether the remaining bins are in bypass mode or use context 0.

Change History (3)

comment:1 Changed 8 years ago by DefaultCC Plugin

  • Cc davidf joel teruhiko jct-vc@… added

comment:2 Changed 8 years ago by davidf

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

Regarding —

  1. the range of log2_res_scale_abs_plus1 can be derived from table 9–34 (cMax=34, cRiceParam=0).
  1. Checking the described encoding, cMax should be 4. Fixed in v2.
  1. Fixed in v2.

comment:3 Changed 8 years ago by davidf

  • Milestone changed from RExt D6 to RExt D5
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)