13.10.2023, 14:49
No, that is still needed.
When filtering interlaced content with filters that only support progressive content you got 2 choices:
1. split the content into fields and treat them as source with half the height ('separate fields'). (since each field has only half the height)
Downside is this that temporal dependencies and thus temporal filtering will work on different content. Which can negatively impact temporal filtering. (The next 'frame' isn't a frame but a shifted 'field')
2. bob deinterlace the source and reinterlace it later. This is what "QTGMC via Misc -> Script -> Filter Interlace Handling ->QTGMC(preset="Fast")" does. It tells Hybrid to use bob deinterlacing and reinterlace later.
Cu Selur
When filtering interlaced content with filters that only support progressive content you got 2 choices:
1. split the content into fields and treat them as source with half the height ('separate fields'). (since each field has only half the height)
Downside is this that temporal dependencies and thus temporal filtering will work on different content. Which can negatively impact temporal filtering. (The next 'frame' isn't a frame but a shifted 'field')
2. bob deinterlace the source and reinterlace it later. This is what "QTGMC via Misc -> Script -> Filter Interlace Handling ->QTGMC(preset="Fast")" does. It tells Hybrid to use bob deinterlacing and reinterlace later.
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.