Opened 8 years ago

Closed 4 years ago

#1431 closed defect (fixed)

pred_weight_table incorrectly uses RefPicList0 to decode luma_weight_l1_flag

Reported by: peterderivaz Owned by:
Priority: minor Milestone:
Component: SCC text Version:
Keywords: Cc: rajan_joshi, jct-vc@…


In JCTVC-U1005-v2.doc the specification for pred_weight_table has a test for the presence of luma_weight_l1_flag based on the value of RefPicList0[i].

I believe (based on examination of TDecCavlc::xParsePredWeightTable) that this test (and the one for chroma_weight_l1_flag) should instead be based on RefPicList1[i].

By the way, it feels really weird that the syntax decode of pred_weight_table (which is inside slice_segment_header) now has dependencies on RefPicList0 and PicOrderCntVal - variables that (according to the first sentence of 8.3.2) are only computed "after decoding of a slice header".

Change History (2)

comment:1 Changed 8 years ago by rajan_joshi

The first part (incorrectly testing for the presence of luma_weight_l1_flag and chroma_weight_l1_flag based on the value of RefPicList0[i]) has been fixed in JCTVC-V1005. Please check.

The second part is still an open issue.

comment:2 Changed 4 years ago by karlsharman

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

The expressions were changed from

if ( PicOrderCnt(RefPicList0[ i ]) != PicOrderCnt( CurrPic ) )

luma_weight_l1_flag[ i ]


if( ( pic_layer_id( RefPicList0[ i ] ) != nuh_layer_id )

( PicOrderCnt(RefPicList1[ i ]) != PicOrderCnt( CurrPic ) ) )

luma_weight_l1_flag[ i ]

prior to publication (of v4).

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

  • jct-vc@…(Subscriber)
  • Karl Sharman(Participant)
  • karl.sharman@…(Always)
  • Karsten Suehring(Always)
  • Peter de Rivaz(Reporter)
  • Rajan Joshi(Subscriber, Participant)