23.08.2021, 22:48
(23.08.2021, 21:49)Selur Wrote: @antoniu200: will send you a link to a dev version to test in a few minutes.
If add 'none' and 'CUVID (FFMPEG)' as deinterlacers.
Note that to useĀ 'CUVID (FFMPEG)' Filtering->Support need to be set to 'no XSynth'.
I tested it with a few clips and it seem to work, but I'm pretty sure there are some bugs created by these two changes.
Take as much time as you need. No rush, by me.
I will also test it and try and break it. I'm no genius at that, but sometimes I do manage to trigger quite obscure bugs.
As an opinion from a less experienced programmer: honestly, I don't think anybody will ever find every bug in their program before they release it. But a good, working release can be done quite simply by not rushing and thinking thoroughly what it is that you're adding or changing.
(23.08.2021, 21:54)shijan Wrote: After some struggle i am ok with current logic. No need deinterlacer - set input to progressive. So if this makes things more stable and easier to code and if it produce less less bugs - i can live with it.
But from user side it is slightly confused and non intuitive to understand it first time. So removed "Use deinterlacer" option needs some decent explanation in release notes and tooltip manual. Otherwise it will be endless amount of same question from forum users.
That was what I thought as well.