Opened 9 years ago Closed 7 years ago #1451 closed technical change (fixed)not clear spelling
Description
In the spec, there is:
pcm_enabled_flag equal to 0 specifies that PCM data are not present in the CVS.
It is not clear what PCM data are assumed not to be in the stream: only PCM samples, or related syntax like pcm_sample_bit_depth_luma_minus1 etc. Change History (4)comment:1 Changed 9 years ago by kolya
Version 0, edited 9 years ago
by kolya
(next)
comment:2 Changed 9 years ago by kolya
comment:3 Changed 9 years ago by kolya
comment:4 Changed 7 years ago by bbross
This issue is fixed in the 2016/12 release of the HEVC specification. 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
|
The spec seems to be ill-formed: when log2_min_luma_coding_block_size_minus3 is equal to 3; log2_min_pcm_luma_coding_block_size_minus3 + 3 is expected to vary in the range [6,5], i.e., from higher to lower value.
At the same time, according to NOTE 4, the spec allows pcm_enabled_flag to be equal to 1, and log2_min_pcm_luma_coding_block_size_minus3 equal to 2 is allowed to present in the stream.
It seems the spec could be fixed by forcing pcm_enabled_flag to be set to zero with log2_min_luma_coding_block_size_minus3 equal to 3; instead of current edition of the NOTE 4.