Doom9's Forum - View Single Post - Chroma Problem with Inverse Telecine filter (IVTC)

poisondeathray · 19th October 2020, 02:34

This occurs because vdub/vdub2's IVTC filter works in 422 . The 420 => 422 chroma upsampling is performed in a progressive fashion, not interlaced aware. That produces those chroma artifacts

I don' t know of any internal vdub2 workaround. The alias format, convert, and decode options don't have interlace aware options. You need something equivalent to avisynth's ConvertToYUY2(interlaced=true) , or ConvertToYV16(interlaced=true). Or vdub2's IVTC filter needs to be reworked to support 4:2:0, or some proper intermediate conversion routine needs to be added

If you feed an avs script to vdub2 (with ConvertToYUY2(interlaced=true) ) it will work . (But if you were using avisynth, you might as well IVTC in the original YV12 in avisynth and skip vdub2 altogether in the first place)

19th October 2020, 02:34	#2 \| Link
poisondeathray Registered User Join Date: Sep 2007 Posts: 5,374	This occurs because vdub/vdub2's IVTC filter works in 422 . The 420 => 422 chroma upsampling is performed in a progressive fashion, not interlaced aware. That produces those chroma artifacts I don' t know of any internal vdub2 workaround. The alias format, convert, and decode options don't have interlace aware options. You need something equivalent to avisynth's ConvertToYUY2(interlaced=true) , or ConvertToYV16(interlaced=true). Or vdub2's IVTC filter needs to be reworked to support 4:2:0, or some proper intermediate conversion routine needs to be added If you feed an avs script to vdub2 (with ConvertToYUY2(interlaced=true) ) it will work . (But if you were using avisynth, you might as well IVTC in the original YV12 in avisynth and skip vdub2 altogether in the first place)