Opened 5 years ago

Last modified 5 years ago

#1077 new defect

Log2MinIpcmCbSizeY range issue when MinCbLog2SizeY = 6

Reported by: stefane Owned by:
Priority: minor Milestone: D10
Component: Text Version: D10 (L1003) v33
Keywords: Cc: bbross, wjhan, jct-vc@…

Description

In 7.4.3.2 Sequence parameter set RBSP semantics, for syntax element log2_min_pcm_luma_coding_block_size_minus3:

"The value of Log2MinIpcmCbSizeY shall be in the range of MinCbLog2SizeY to Min( CtbLog2SizeY, 5 ), inclusive."

Specifically for MinCbLog2SizeY = CtbLog2SizeY = 6 (discouraged but allowed when pcm_flag = 1):

"The value of Log2MinIpcmCbSizeY shall be in the range of 6 to 5, inclusive."

which is contradictory (assuming ranges are specified low to high).

A similar issue exists for syntax element log2_diff_max_min_pcm_luma_coding_block_size.

Change History (2)

comment:1 Changed 5 years ago by DefaultCC Plugin

  • Cc bbross wjhan jct-vc@… added

comment:2 Changed 5 years ago by kchono

The following should fix the issue (including the Log2MaxIpcmCbSizeY constraint).

"The value of Log2MinIpcmCbSizeY shall be in the range of MinCbLog2SizeY

to Min( CtbLog2SizeY, 5 ), inclusive."

is changed by
"The value of Log2MinIpcmCbSizeY shall be in the range of Min( MinCbLog2SizeY, 5 ) to Min( CtbLog2SizeY, 5 ), inclusive."

What do you think?

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(Subscriber)
  • David Flynn(Always)
  • jct-vc@…(Subscriber)
  • Karl Sharman(Always)
  • Karsten Suehring(Always)
  • Keiichi Chono(Participant)
  • Woo-Jin Han(Subscriber)