You can put the filter right after "STMedianFilter(8, 32, 0, 0 )" line of the current script.
I used: MipSmooth(preset="MovieHQ")

-kwag

Hey, hey Don't think that I'm bad at Mathematics :lol:

It's just such a big time Time difference, that I required some confirmation.

Well, I think 5 Times slower is just too much. The current optimal Script is very developed, already. So for me It's not worth it to wait 25 Hour's for a result which would only slightly be better. And also the Tok Prediction for PAL is a reason. I don't want to wait 25 Hours for a result that is probably too big.

And there's really no visual quality difference after adding MipSmooth :wink:

-kwag

:!:
after a test with MipSmooth after STMedianFilter
was needed 5 times more to encode and
15 seconds to encode each 27 frames,
more or less 56 seconds to encode 90 frames...

:!:

I think it looks great being used alone. So I do not even use anything else like STmedianfilter. I just change the resizers in the filter to bicubic or lanczos depending on the source. I find Kwags Optimal Script is extremely slow on 720x480 DVDs.(I only put two movies on a DVD, so I never resize my video, trying to keep them at the highest res for my future HDTV.)Adding mipsmooth to the Optimal Script will just kill it. Besides a couple of months ago you guys were all diehard 2.08 "we will never leave it" , "space dust rules!!!"fans. :) Now you guys are into stmedian filter and 2.52, so this could just be another addition\change to KVCD filter group. :)

digitalize,
:)
in my third post in the first page i did tests with MipSmooth
and the results was great (like you posted) using:
MipSmooth(preset = "movieHQ") and
MipSmooth()

but using in the Kwag script after STMedianFilter
was too slow and the result was good too.

resuming, the final quality is cool but take long time.

do you have some idea to use MipSmooth
in the script and turning it faster?
...will be welcome!
:wink:

You can take all the filters out (current script) and use MipSmooth alone. Now time your encode.
Now remove MipSmooth and add the current script again. Time your encode again.

Result:
With MipSmooth, it's still 4X the time to encode :wink:
The filter chain that is in the current script is a better choice (for the time being), because we are able to "plug" filters for different conditions. Not to mention the "Adaptive" nature of the script, which takes advantage of the motion difference between frames.

-kwag