24.09.2020, 15:04
I'm using AviSynth 32 bit.
You can actually feed QTGMC whatever content you want... you can feed progressive content and set input type to 0, which in some cases can actually work better than using input types 2 or 3, which is what you're "supposed" to use to correct interlacing artifacts on progressive video. You could also feed interlaced content with input types 1 - 3, for creative or experimental reasons.
But as a standard, if QTGMC is used with input types 1 - 3 on progressive video, Hybrid should not be "thinking" that it is interlaced content.
One idea:
- If input type is interlaced (top/bottom field first, either directly from input video, or via "overwrite" option), if QTGMC is selected, set input type to 0 and grey the input type control...
- If input type is progressive, if QTGMC is selected, set input type to 1, and only allow options 1-3 to be set for input type. Hybrid will then insert QTGMC into the AviSynth script and not set any deinterlacing options for filters before it.
If someone wants to run input type 0 on progressive content, they could use the "overwrite input type" control. They will not however be able to run filters that require deinterlacing before it without Hybrid inserting TDeint scripting. Which makes me think the old "Force" option may be the best choice, since it's more versatile.
You can actually feed QTGMC whatever content you want... you can feed progressive content and set input type to 0, which in some cases can actually work better than using input types 2 or 3, which is what you're "supposed" to use to correct interlacing artifacts on progressive video. You could also feed interlaced content with input types 1 - 3, for creative or experimental reasons.
But as a standard, if QTGMC is used with input types 1 - 3 on progressive video, Hybrid should not be "thinking" that it is interlaced content.
One idea:
- If input type is interlaced (top/bottom field first, either directly from input video, or via "overwrite" option), if QTGMC is selected, set input type to 0 and grey the input type control...
- If input type is progressive, if QTGMC is selected, set input type to 1, and only allow options 1-3 to be set for input type. Hybrid will then insert QTGMC into the AviSynth script and not set any deinterlacing options for filters before it.
If someone wants to run input type 0 on progressive content, they could use the "overwrite input type" control. They will not however be able to run filters that require deinterlacing before it without Hybrid inserting TDeint scripting. Which makes me think the old "Force" option may be the best choice, since it's more versatile.