id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
109	One potential bug may lead to mismatch	libin		"At encoder, both skip mode and direct mode are checked in xCheckRDCostSkip(). When the encoder selects the bi-predicted direct mode and this CU has no residue (it will only happen with CABAC, when the encoder thinks this direct mode will cost less bits than skip mode), the variables should be reset as the skip mode.
Actually, when this happens, xEncodeCU() will take it as skip mode, and the decoder will receive skip mode too. But at the encoder TransformIdx may not always be 0 (because in RD process, the encoder takes it as direct mode, not skip mode), at the decoder TransformIdx will always be 0(because the decoder takes it as skip mode). This will lead to mismatch after deblocking filter.
So, in my opinion, after the RD process, when pcCU->isSkipped( uiAbsPartIdx ) is true, the variables should be reset as the skip mode, to avoid the mismatch between the encoder and the decoder."	defect	closed	minor	HM-3.1	HM		fixed		fbossen ksuehring davidf jct-vc@…