Filters, Plugins, and the like

[checkers]

undot() also occasionally gives weird artifacts (there are a few threads on doom9 about it), so you should always use removegrain(1) these days.

[DarkT]

I prefer Undot ro RemoveGrain because I was too lazy to research the exactness of what I need to input to RemoveGrain - and while there was ONE time when I saw a messup left my undot, I never saw it since - so I was like "Mmhmhm, I'll just pretend I used removegrain" .

Meow... .

But now I'll drop undot... Mainly because some scripts are requiring more speed - and I use SSE2 of remove grain(ore was it remove dirt? Meow...) - anyway...

[Starks]

Is the syntax for the optimized versions also RemoveGrain()?

[martino]

Originally Posted by Starks

Is the syntax for the optimized versions also RemoveGrain()?

Yes, just make sure to load the correct DDL. They're all the same, just optimised for different instruction sets (AFAIK).

[DarkT]

Basically, here's how it is(from the html, reordered):

The binary package contains four versions of RemoveGrain, two small dynamically linked versions

RemoveGrain.dll = Athlon and Pentium 3 design
RemoveGrainSSE2.dll = Pentium 4 or Athlon 64
RemoveGrainSSE3.dll = Prescott P4s

*If none of these dlls work because of a missing dll, one has either to copy the missing dll to the window's system directory or one has to use RemoveGrainS.dll, which only requires SSE.

**Please put only one of the three plugins into the Avisynth plugin directory.

[Starks]

I have a Core Duo with SSE3, so I use the SSE3 one right?

[DarkT]

'suppose so, why not give it a try and see what happens? .