Hybrid used to have a "Force" option that dealt with this. That's been removed.
QTGMC has input types of 0, 1, 2, and 3. ONLY 0 is intended for actual interlaced content (although it can be used on content flagged as progressive using the "overwrite input" option).
So for example, if I have a regular progressive Blu-Ray rip of a movie that is extremely grainy or noisy, I can use QTGMC's temporal smoothing by setting the input flag to 1. It's intended by QTGMC that input type 1 means progressive input.
HOWEVER, in order to get Hybrid to generate a script that includes QTGMC, I have to now use the "overwrite input" option to "top field first". Now, Hybrid considers the video to be interlaced, not progressive. This really isn't a problem if the deinterlace function is moved to the top in custom filter order so that it runs first, OR if it runs with other filters that can work with both progressive and interlaced content.
HOWEVER, IF a filter can't work with interlaced content, AND the user wants that filter to run BEFORE QTGMC denoising for progressive videos, Hybrid now assumes the input video is interlaced, and inserts deinterlacing scripting using TDeint *before* the filter. That's not good.
ALSO, IF a filter has settings that are particular to interlaced content, those settings will be enabled by Hybrid, because it is erroneously assuming that the input is interlaced.
Bottom line, QTGMC with an input type other than 0 means progressive input, not interlaced, and Hybrid should not be setting deinterlacing scripting functions if QTGMC does not have input type set to 0.
I'm not sure of the best way to make it do that. Re-implement Force? Or something else? You could for example make it so deinterlacing functions don't get inserted if QTGMC is being used with an input type other than 0, but it doesn't seem right to set an option to overwrite the video input type to interlaced for a progressive video that you only want to denoise using QTGMC.
QTGMC has input types of 0, 1, 2, and 3. ONLY 0 is intended for actual interlaced content (although it can be used on content flagged as progressive using the "overwrite input" option).
So for example, if I have a regular progressive Blu-Ray rip of a movie that is extremely grainy or noisy, I can use QTGMC's temporal smoothing by setting the input flag to 1. It's intended by QTGMC that input type 1 means progressive input.
HOWEVER, in order to get Hybrid to generate a script that includes QTGMC, I have to now use the "overwrite input" option to "top field first". Now, Hybrid considers the video to be interlaced, not progressive. This really isn't a problem if the deinterlace function is moved to the top in custom filter order so that it runs first, OR if it runs with other filters that can work with both progressive and interlaced content.
HOWEVER, IF a filter can't work with interlaced content, AND the user wants that filter to run BEFORE QTGMC denoising for progressive videos, Hybrid now assumes the input video is interlaced, and inserts deinterlacing scripting using TDeint *before* the filter. That's not good.
ALSO, IF a filter has settings that are particular to interlaced content, those settings will be enabled by Hybrid, because it is erroneously assuming that the input is interlaced.
Bottom line, QTGMC with an input type other than 0 means progressive input, not interlaced, and Hybrid should not be setting deinterlacing scripting functions if QTGMC does not have input type set to 0.
I'm not sure of the best way to make it do that. Re-implement Force? Or something else? You could for example make it so deinterlacing functions don't get inserted if QTGMC is being used with an input type other than 0, but it doesn't seem right to set an option to overwrite the video input type to interlaced for a progressive video that you only want to denoise using QTGMC.