New motion compensated deinterlace filter (TomsMoComp)

dividee - Thanks. I'll try that right away. Hopefully it will crash for me here also (what a thing to say ;) ) BTW, what release of Avisynth are you running? - Tom

I was using the CVS code from about 24h ago. Will try with older versions and report back. [EDIT:] Same behavior with 1.0b7, 1.0b6, 1.0b5 and latest CVS

Okay, I can crash it here too. It looks like I process too many lines and fall off the end of the buffer. Unless it's the -1 doubling option. Then I process too few. Fix soon. - Tom

There is a VirtualDub filter who does exactly this (I think):

Ah, too bad, that's a deinterlacer too. I thought you'd come up with a motion compensated temporal smoother ;) trbarry, can you adopt the code from avisynth's temp smoother (or was it dividee's code?) to work with the found motion? :) (well, and be scene-change adaptive as well is somewhat important i guess...) *hide* Regards, Koepi

Sorry guys, the bug is still not fixed. I mostly played hookey yesterday. And I don't think I can easily adapt this as a temporal smoother. - Tom

Just checking in here re: 60fps output (from the CPU Optimization thread.) Wanted to get on e-mail notify for this thread. trbarry: Occasionally when I use Force FILM on a DVD that shows 99% film in DVD2AVI, I still get choppy pans. What do you think about leaving such a thing at 29.97fps and using TomsMoComp on it? Stupid idea?