id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
1107	Possible contradiction with regard to picture latency	jackh		"This ticket relates to spec sections 7.4.3.2 and C.5.2.3.

Say I have a CVS with the following pictures (given in decoding order):

|| '''POC''' || 1 || 4 || 2 || 5 || 3 ||
|| '''Reorder''' || 0 || 0 || 1 || 0 || 2 ||
|| '''Latency''' || 0 || 2 || 0 || 1 || 0 ||

The reorder and latency values have been arrived at using the definitions in section 7.4.3.2:

   '''Reorder:''' the maximum allowed number of pictures that can precede any picture in the CVS in decoding order and follow that picture in output order

   '''Latency:''' the maximum number of pictures that can precede any picture in the CVS in output order and follow that picture in decoding order

So in the SPS for this CVS, I have sps_max_num_reorder_pics=2 and sps_max_latency_increase_plus1=1, giving 2 as the maximum value for reorder and latency.

Now I come to decode this CVS using the procedure in C.5.2.3. The process goes like this:

1.Decode POC 1. Store in DPB as 'needed for output'. No bumping on this step. DPB at end of this step:

|| POC || 1 ||
|| PicLatencyCount || 0 ||

2. Decode POC 4. No output. DPB at end of this step:

|| POC || 1 || 4 ||
|| PicLatencyCount || 1 || 0 ||

3. Decode POC 2. As NumDPB>2, invoke bumping and output POC 1. DPB at end of this step:

|| POC || 4 || 2 ||
|| PicLatencyCount || 1 || 0 ||

4. Decode POC 5. As NumDPB>2, invoke bumping and output POC 2. As PicLatencyCount for POC 4 is now 2, invoke bumping again and output POC 4. DPB at end of this step:

|| POC || 5 ||
|| PicLatencyCount || 0 ||

The order of output will now end up as 1,2,4,3,5 instead of the expected 1,2,3,4,5. It seems like the condition in C.5.2.3 should be that PicLatencyCount is greater than SpsMaxLatencyPictures, rather than greater than or equal to."	defect	closed	minor		Text	D10 (L1003) v33	fixed		bbross wjhan jct-vc@…