id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
1348	Inconsistency in HEVC spec and between the spec and HM	gaow02		"We found some inconsistency in HEVC spec and between the spec and HM software. We would appreciate if someone can help to clarify them.

1.Use of “concatenation_flag”: 
The meaning of this flag being either “0” or “1” as described in Annex C.2.3 Eq(C-11)(on “concatenationFlag”) is different from that described later in Annex D.3.2 (on “concatenation_flag”). Based on common sense and also as implemented in HM encoder, it seems that the description in Annex C.2.3 would be correct, i.e. concatenation_flag = 0, meaning no extra constraint related w/ prevNonDiscardablePic is needed, and the derivation of nominal removal time would be simpler and the same as in AVC. 

2.The setting of “nuh_temporal_id_plus1”: 
In HEVC spec 7.4.2.2, when explaining the setting of right values for “TemporalId for non-VCL NAL units”,the last statement is that “Otherwise, TemporalId shall be greater than or equal to the TemporalId of the access unit containing the NAL unit.” However, in the following “NOTE 9”, it says “When the NAL unit is a non-VCL NAL unit, the value of TemporalId is equal to the minimum value of the TemporalId values of all access units to which the non-VCL NAL unit applies.” The “greater than” in the 1st statement is contradictory w/ the “minimum” in the 2nd statement. From HM encoder, we see that it is implemented to be the “minimum” as stated in the 2nd statement. 

3. Inconsistency between HM encoder and HEVC spec: 
For HEVC VPS and SPS parameters “sps_max_dec_pic_buffering_minus1[i]”, and “sps_num_reorder_pics[i]” (same things for “vps_” as well), they are coded in HM encoder functions CodeSPS() and CodeVPS(). The related variables NumReorderPics and MaxDecPicBuffering of layer i are set the same value of the involved layer index, i.e. “i”, which can be seen by tracing all the code w/ key words “setNumReorderPics” and “setMaxDecPicBuffering”. This setting, however, violates w/ the value constraint of vps/sps_max_num_reorder_pics[i] as stated in HEVC spec 7.4.3.1 and 7.4.3.2, where it basically says max_num_reorder_pics[i] has to be in the range of 0 to max_dec_pic_buffering_minus1[i], inclusive. Now, the current HM setting value of NumReorderPics is equal to the value of MaxDecPicBuffering, which will violate the constraint as stated in the spec. 

==========
Note that: the version of the HEVC spec we are using is L1003_v34. However, I couldn't find that version in the list. So I choose the closest one, L1003_v33.
"	defect	closed	major		Text	D10 (L1003) v33	fixed		bbross wjhan jct-vc@…