id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
412	Deblocking processing order in Draft Text does not match HM	pieterkapsenberg	bbross	The draft text specifies that for each CU in coding order (I assume this means the leaf CU, not the largest CU), first all vertical edges are filtered, then all horizontal edges are filtered. HM6.0 does all vertical edges for the whole picture first, then all horizontal edges for the whole picture. This is a different data dependency. For HM, all vertical edges use pre-deblocked pixels as input, whereas the draft spec suggests that the vertical filters may sometime use horizontally deblocked pixels as inputs. Which one is correct/intended? A picture-based ordering has buffer implications for hardware implementations. 	defect	closed	minor	D7	Text	D6 (H1003) dI/dJ/dK	fixed	deblock deblocker order ordering	bbross wjhan jct-vc@…