'no deinterlacing' was removed a while ago.
Hybrid will only deinterlace when it's required.
Meaning, only if:
a. source is detected as interlaced ('overwrite input scan type')
b. output is not interlaced
will Hybrid deinterlace. This is also in the tool-tip.
Cu Selur
Hybrid will only deinterlace when it's required.
Meaning, only if:
a. source is detected as interlaced ('overwrite input scan type')
b. output is not interlaced
will Hybrid deinterlace. This is also in the tool-tip.
Quote:Deinterlace handling:
Sets what method will be used to deal with non-progressive content, assuming the output isn't marked as interlaced in the encoder.
Hybrid does only deinterlace if:
a. the source is non-progressive
b. the output is not interlaced
So:
- If your source is flagged as interlaced, but in reality is progressive: overwrite the scan type.
- If your source is flagged progressive, but in reality interlaced: overwrite the scan type.
- If your source is progressive and properly flagged, do not worry Hybrid will not try to deinterlace the source.
Quote:Overwrite input scan type to:Setting deinterlace handling to 'no deinterlacing' always was a bad idea, since it took away information from Hybrid.
If the normal headers indicate a wrong input scan type and the interlace detection of Hybrid also fails you, you can use this option to overwrite the current input scan type.
If the scan type is progressive, no deinterlace handling will be available unless the scan type is overwritten.
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.