24.09.2020, 15:26
Hybrid, during in the scrip creation, doesn't distinguish whether the content was progressive or interlaced from the beginning or whether that was archived by 'overwrite scantype'.
When a filter supports no interlaced content then Hybrid either deinterlaces the content before applying the filter or it splits the content into fields to apply the filter.
Do I get you right, that you want to apply filters that only support progressive content on interlaced content (even if that wracks the frame content) ?
Because if you can change the filter order the scan type of the content can change before the filter (QTGMC) is applied.
From what I see Hybrid does work correctly and applies the filters with the settings and order it is given by the user.
Cu Selur
When a filter supports no interlaced content then Hybrid either deinterlaces the content before applying the filter or it splits the content into fields to apply the filter.
Do I get you right, that you want to apply filters that only support progressive content on interlaced content (even if that wracks the frame content) ?
Quote:- 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...That does only make sense if you can't change the order of filters.
- 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.
Because if you can change the filter order the scan type of the content can change before the filter (QTGMC) is applied.
From what I see Hybrid does work correctly and applies the filters with the settings and order it is given by the user.
Cu Selur