![]() |
most NTSC files are incorrectly defined - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: most NTSC files are incorrectly defined (/thread-310.html) Pages:
1
2
|
RE: most NTSC files are incorrectly defined - kingcrimsonster - 22.02.2018 Quote:From what I see you are playing around with settings without knowing or understanding what they doBy default I set "Auto" in the "Auto deinterlacing" option in the "De-)Interlace" tab! In the "Config" - "Automation" I uncheck "interlaced check" When I load this file, Hybrid automatically puts "Decomb" mode. I do not change anything in this tab. What am I doing wrong? If "Decomb" mode wrong for this file, this problem a Hybrid? RE: most NTSC files are incorrectly defined - Selur - 22.02.2018 To me it looks like you changed something and you are not aware of it. -> reset your Hybrid defaults, restart Hybrid, disable the automatic interlaced check. I start Hybrid, do that and then load your source and QTGMC is used as deinterlacer,.. Cu Selur RE: most NTSC files are incorrectly defined - kingcrimsonster - 22.02.2018 Quote:reset your Hybrid defaults, restart Hybrid, disable the automatic interlaced checkThank you, now I see "ivtc-filmdint" Method "softpulldown + detc " stream frame rate 29,97 container frame rate 29,97 output frame rate 23,976 RE: most NTSC files are incorrectly defined - kingcrimsonster - 23.02.2018 There was a misunderstanding. After resetting, vapoursynth turned on Then I see "ivtc-filmdint" Method "softpulldown + detc " When I switch to "Avisynth support" again enabling "decomb" mode. Problem still exist. RE: most NTSC files are incorrectly defined - Selur - 23.02.2018 That happens if the sourc ist detected as mixed content. |