The following warnings occurred:

Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux) File Line Function /inc/class_error.php 153 errorHandler->error /inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback /inc/plugins/cookielaw.php 272 eval /inc/class_plugins.php 142 cookielaw_global_intermediate /global.php 100 pluginSystem->run_hooks /printthread.php 16 require_once Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux) File Line Function /inc/class_error.php 153 errorHandler->error /inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback /inc/plugins/cookielaw.php 272 eval /inc/class_plugins.php 142 cookielaw_global_intermediate /global.php 100 pluginSystem->run_hooks /printthread.php 16 require_once

[HELP] VIVTC (Fix Combed with deinterlacer) problem - 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: [HELP] VIVTC (Fix Combed with deinterlacer) problem (/thread-3640.html)

VIVTC (Fix Combed with deinterlacer) problem - dsiomnainc - 29.03.2024 Good afternoon. When I check the "Fix Combed with deinterlacer" checkbox inside VIVTC, the following error pops up.  Regardless of the selected deinterlacer.  Tell me what could be the problem. RE: VIVTC (Fix Combed with deinterlacer) promleb - Selur - 29.03.2024 Probably a typo, will look into it and report back. Cu Selur RE: VIVTC (Fix Combed with deinterlacer) problem - Selur - 29.03.2024 It was a bug introduced during some refactoring a while ago. Send you a link to a dev version via pm in which the problem should be fixed. -> test it and let me know whether that fixes the problem for you. Cu Selur RE: VIVTC (Fix Combed with deinterlacer) problem - dsiomnainc - 29.03.2024 Thank you, now the error does not appear.  But I ran into another problem. If you select QTGMC in this option, random frames from another part of the video begin to jump out in different parts of the video. Perhaps this is the case in my video, I am attaching a video sample. https://cloud.mail.ru/public/da5U/ePoP9NFZL RE: VIVTC (Fix Combed with deinterlacer) problem - Selur - 29.03.2024 Looking at the source, first thing I would recommend is: enable "Config->Internals->Handling->Ignore all input timecodes" (reload source) set "Crop/Resize->Base->Pixel Aspect Ratio (PAR)" to 3x2 Starting from there that source has no combing artifacts, just tons of blends. Using 'Fix combed with deinterlacer' does not make sense as there is no combing in the source. If you are planning on using VIVTC or TIVTC, you should enable "Filtering->(De-)Interlace/Telecine->Deinterlace/Telecine Settings->Overwrite input scan type to" and set it to 'telecine'. Personally I would set able "Filtering->(De-)Interlace/Telecine->Deinterlace/Telecine Settings->Overwrite input scan type to" and set it to 'progressive', try to figure out if there is a pattern to the blends and decimate them if possible. Problem is, that source is a mix of different progressive content and I doubt that there is a fixed pattern and I doubt sRestore can fix this. I doubt you can get rid of all the blends using Hybrid. Wobbly or Exblend might be the right approach. => I can reproduce the problem with 'Fix combed with deinterlacer' and will look into it, but like I mentioned, this should not be used on such input. Cu Selur RE: VIVTC (Fix Combed with deinterlacer) problem - Selur - 29.03.2024 It's not a bug, you need to increse the 'Threshold' value in 'Fix comed with deinterlacer' for the clip. (using i.e. 12 instead of the default 6 does seem to fix the problem here) Cu Selur RE: VIVTC (Fix Combed with deinterlacer) problem - dsiomnainc - 29.03.2024 Thanks! RE: VIVTC (Fix Combed with deinterlacer) problem - Selur - 29.03.2024 Correction, there are combing artifacs, so overwriting to 'telecine' instead of 'progressive' seem like a good start.