id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
1098	wrong POC referencing while building combined bi-predictive merging candidates	tee.jung		"I found some weird condition from '8.5.3.2.3 Derivation process for combined bi-predictive merging candidates'.

A merging candidate list mergeCandList includes temporal merge candidate, but POC comparison between L0combCandk and L1combCandk does not consider the case that L0combCandk or L1combCandk comes from temporal merge candidate, as in below:

* ( DiffPicOrderCnt( RefPicList0[ refIdxL0l0Cand ], RefPicList1[ refIdxL1l1Cand ] ) != 0 ) | | ( mvL0l0Cand != mvL1l1Cand )

RefPicList0/1 are defined as L0/L1 list of a slice, so if l0Cand or l1Cand is temporal merging candidate then refPicListL0/1 of co-locate picture should be referred instead of RefPicList0/1. 

And in case that, num_ref_idx_l0_active_minus1 of current slice is lesser than num_ref_idx_l0_active_minus1 of co-located picture, RefPicList0[ refIdxL0l0Cand ] can cause referencing on undefined value. 

Is this intended behavior?
"	defect	closed	critical	HM-10.1	Text	D10 (L1003) v33	invalid		bbross wjhan jct-vc@…