I was just wondering if there was a deinterlacing filter based on that method. By the way what is the method used by decomb ? Is it a motion-adaptative per-pixel deinterlacing filter ? :confused: Really weird questions isn't it ! :)
--------------------- Hej. Mam na imię Sebastian i studiuję w Gdańsku na Uniwersytecie. Moje zainteresowania to: motoryzacja oraz muzyka elektroniczna. Zajrzyj na mojego bloga motoryzacyjnego - abs-esp.pl.
TomsMoComp is a motion compensated deinterlacing filter (pure video source only, no IVTC). But it only searches a couple pixels left and right. Setting the SearchEffort parm greater than 5 can make it search more but seems to cause more artifacts. See: - Tom
--------------------- ludziska się śmiali, dziewczyna płakała.
trbarry, why didnt you choose a block based motion search BTW? That the present code would suffer from extreme aperture problems seems to be a given. It would be nice to have a good block based predictive ME in avisynth, seperate from the actual effect filters such as deinterlacing and denoising.
There are a load of televisions out there which use block based motion compensated deinterlacing, and what a load it is ... BTW I dont think it makes much sense to use variable block size motion compensation, just use 8x8 blocks for everything, even for motion estimation hierarchy can do more harm than good IMO.
@tom: greedyhma did some great job on ntsc and pal interlaced stuff, any plans to do some proper manual/guide so i will know what exactly is happening? And 2nd is there a plan to relese vdub version of greedyhma? tia.
smok3 - Well, for pure interlaced stuff (NTSC or PAL), my guide is to always use: TomsMoComp(1,5,1) or TomsMoComp(0,5,1) depending upon whether the clip is top first. For mixed or problem material these days I just use DeComb. Donald Graft has invested way more effort and patience into dealing with all the exceptions and requests than I am ever likely to be able to do. I may in the future come out with an optimized fast IVTC filter of some sort for the general cases. But I have no plans for handling all the special problems and pathological conditions that come up and I have no plans at all for writing Vdub filters of any sort. I do however have a partially completed version of TomsMoComp that should rate double to 50-60 fps. I'll try to finish and release that soon. - Tom
DDog - Sorry. The code got forked for the latest Avisynth 2.5 and I haven't gotten back to it yet. It's complicated somewhat by it being so long I forgot where I was in it and there have also been some new DScaler developements that I might like to incorporate. But I'll try to get back to it and finish up at least the 60 fps part. - Tom
And you thought we forgot :) I could use it as part of the "film look" I mentioned in the other post seems to involve going to 60 fps. Beggars can't be choosy. I just appreciate all the stuff you have done for the group (blatant suck up to twist your arm :) ).
If you search the various TomsMoComp threads I think someone (Hakko?) already published a TomsMoComp script function that will take it to 60 fps properly. The only difference would be a small amount of run time performance. - Tom
--------------------- Hej! Jestem Jacek. Jestem tu zupełnym początkującym, nie mniej mam w planach w wolnym czasie uczestniczyć, w życiu niniejszego portalu.