Tomsmocomp

[cool9]

Can someone explain the Searcheffort a little better for me? (Varies from 0-30 with 30 being the most CPU intensive but he (TBarry) says #'s above 15 haven't been tested much.) It's the CPU time used to find motion? So what would be the difference if I used a "5" then tried a "10"? What exactly is the deinterlacer doing?

[cool9]

What kind of motion settings (ie VHQ, Motion Precision) should I use in XviD if I use Tomsmocomp since it uses motion compensation to deinterlace?

[Fizick]

It is avisynth filter, try find right old thread about it.

[communist]

What kind of motion settings (ie VHQ, Motion Precision) should I use in XviD if I use Tomsmocomp since it uses motion compensation to deinterlace?
You just use what you use always, there isnt a relation between the search effort in TMC and MSP/VHQ in XviD.

[LoRd_MuldeR]

Can someone explain the Searcheffort a little better for me? (Varies from 0-30 with 30 being the most CPU intensive but he (TBarry) says #'s above 15 haven't been tested much.) It's the CPU time used to find motion? So what would be the difference if I used a "5" then tried a "10"? What exactly is the deinterlacer doing?

Well, afaik Motion Compensation trys to rebuild moving objects from various frames. The more effort it makes to find moving objects, the better results you'll get. That's because less areas need to be interpolated. However too high values for Searcheffort need too much CPU power and they produce artifacts, like funny dots jumping arround in your video. Don't think there is any need to go above 10.

Too sad, Tom did not release any updates since 2003 ...