Opened 12 years ago Closed 12 years ago #1043 closed defect (fixed)Confusion about decoding engine initialization after pcm_flag
Description
9.3 "CABAC parsing process for slice segment data" says that the decoding engine is initialized after reading pcm_flag and decoding a 1.
This implies that a decoder should:
However, I suspect the intention is to have the decoding engine initialized only after reading the PCM samples:
Change History (5)comment:1 Changed 12 years ago by DefaultCC Plugin
comment:2 Changed 12 years ago by bbrosscomment:3 Changed 12 years ago by kchono
I think that the suggested HEVC text fix is correct. Thank you very much! comment:4 Changed 12 years ago by bbross
comment:5 Changed 12 years ago by bbross
Fixed in v32. 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
|
In AVC, the corresponding part is described as follows:
"In case the request for a value of a syntax element is processed for the syntax element mb_type and the decoded value of mb_type is equal to I_PCM, the decoding engine is initialised after the decoding of any pcm_alignment_zero_bit and all pcm_sample_luma and pcm_sample_chroma data as specified in clause 9.3.1.2."
Thus changing the aforementioned HEVC text to
"In case the request for a value of a syntax element is processed for the syntax element pcm_flag and the decoded value of pcm_flag is equal to 1, the decoding engine is initialized after the decoding of any pcm_alignment_zero_bit and all pcm_sample_luma and pcm_sample_chroma data as specified in subclause 9.3.2.5."
would fix that.