14.10.2026, 04:30
(side note: haven't used vivtc for ages)
regarding 1.:
No, that’s not intended. When the source isn’t YUV420P8, Hybrid builds the 8-bit match clip and VFM’s clip2 from the same variable that also holds the deinterlaced clip. So VFM matches and outputs QTGMC frames, which explains your 300/300 ‘c’. With 8-bit 4:2:0 sources, VFM already works on the original fields.
regarding 2.: Yes, that’s should fix it: match clip = 8-bit conversion of the source, clip2 = source, and the selected deinterlacer only in the FrameEval post-processing for frames flagged _Combed. I’ll add it to the next dev build.
regarding 3.: Also a bug. Hybrid only writes options that differ from Hybrid’s defaults, and for Block X/Y those differ from vivtc’s own defaults (VFM: Hybrid 32 vs. vivtc 16; VDecimate: Hybrid 64 vs. vivtc 32). So your 32/32 got dropped and VFM ran with 16/16. Your other values match vivtc’s defaults, so leaving them out doesn’t change anything. Checked it, in vivtc’s source: VFM’s block default is 16/16 and VDecimate’s is 32/32, and clip2 does not affect chroma. I’ll fix that too.
About as seqfault: will look into adding a workaround (padding, deinterlacing, removing the padding)
=> don't have enough time to fix these before work, but will look at it once I'm back home after work (~13hrs), also found another small bug which could potentially cause issues with the used scan order in vfm. I'll also adress that and then release new dev versions. (which will then be inside the R81 folder in the experimental folder)
Cu Selur
regarding 1.:
No, that’s not intended. When the source isn’t YUV420P8, Hybrid builds the 8-bit match clip and VFM’s clip2 from the same variable that also holds the deinterlaced clip. So VFM matches and outputs QTGMC frames, which explains your 300/300 ‘c’. With 8-bit 4:2:0 sources, VFM already works on the original fields.
regarding 2.: Yes, that’s should fix it: match clip = 8-bit conversion of the source, clip2 = source, and the selected deinterlacer only in the FrameEval post-processing for frames flagged _Combed. I’ll add it to the next dev build.
regarding 3.: Also a bug. Hybrid only writes options that differ from Hybrid’s defaults, and for Block X/Y those differ from vivtc’s own defaults (VFM: Hybrid 32 vs. vivtc 16; VDecimate: Hybrid 64 vs. vivtc 32). So your 32/32 got dropped and VFM ran with 16/16. Your other values match vivtc’s defaults, so leaving them out doesn’t change anything. Checked it, in vivtc’s source: VFM’s block default is 16/16 and VDecimate’s is 32/32, and clip2 does not affect chroma. I’ll fix that too.
About as seqfault: will look into adding a workaround (padding, deinterlacing, removing the padding)
=> don't have enough time to fix these before work, but will look at it once I'm back home after work (~13hrs), also found another small bug which could potentially cause issues with the used scan order in vfm. I'll also adress that and then release new dev versions. (which will then be inside the R81 folder in the experimental folder)
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.