id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
1121	HighestTid should be used instead of t_id for bumping	rickard		"C.5.2.2 specifies among other things that bumping shall continue until the following condition becomes false:
""The number of pictures in the DPB that are marked as ""needed for output"" is greater than sps_max_num_reorder_pics[ HighestTid ]""

The HM code looks at sps_max_num_reorder_pics[temporal_id of the current NAL] instead of sps_max_num_reorder_pics[HighestTid]. This leads to pictures being output in incorrect order, for instance in this example with pictures listed in decoding order:

sps_max_num_reorder_pics[0]=0
sps_max_num_reorder_pics[1]=1
sps_max_num_reorder_pics[2]=2
sps_max_num_reorder_pics[2]=4 Note that 4 is needed here

IDR POC=0 t_id=0
TRAIL_R POC=8 t_id=0
TRAIL_R POC=4 t_id=1
TRAIL_R POC=2 t_id=2 HM bumps this picture too soon
TRAIL_R POC=6 t_id=2
TRAIL_N POC=1 t_id=3
TRAIL_N POC=3 t_id=3
TRAIL_N POC=5 t_id=3
TRAIL_N POC=7 t_id=3
"	defect	closed	major		HM	HM-11.0	duplicate		fbossen ksuehring davidf jct-vc@…