XviD speed issues (is this normal?)

[Wintershade]

When I encode to XviD via MeGUI, the encoding speed of each pass is around 3-4 FPS.
This is the AVISynth script I'm using at the moment:

# Set DAR in encoder to 179 : 98. The following line is for automatic signalling
global MeGUI_darx = 179
global MeGUI_dary = 98
DGDecode_mpeg2source("D:\Temp\DP\Pod's Travels.d2v",cpu=4)
edeintted = last.AssumeTFF().SeparateFields().SelectEven().EEDI2(field=-1)
TDeint(order=1,full=false,edeint=edeintted)
crop( 6, 76, -6, -76)

Lanczos4Resize(640,384) # Lanczos4 (Sharp)
#denoise

I'm running this on my laptop, which is a Pentium-M @ 1,6 GHz and 2MB L2 cache. Alternatively, my desktop computer, AthlonXP 2800+ runs the encoding at about the same rate.

Is there a way to speed this up? What am I doing wrong?
I remember encoding via GordianKnot some time ago, with the same two computers, and achieving much higher FPS rates, and I believe the AVISynth scripts were similar (they had deinterlacing, resizing and cropping).
Many thanks.

[henryho_hk]

1) try a faster deinterlacer, e.g. yadif() (http://forum.doom9.org/showthread.php?t=124284)
2) Compression parameters greatly affects the speed. Are you using high quality presets in megui?

[Wintershade]

OK, is there a quality difference between the various deinterlacers and, if so, how does this one stand?
Can I use it for any kind of interlaced video? I mean, MeGUI offers me different deinterlacers for different types of interlaced video.
Thanks.

edit: As for the compression parameters, I'm using Turbo, Motion Search Precision 4 and VHQ mode 1, as well as VHQ for Bframes (as far as I managed to understand, these have most speed issues). Should I change those settings to something else? And moreover, are there any other settings I should watch for?

Forgot to mention... Quality is most important to me. Although I would like to have greater speed, if there would be significant quality loss I'll survive.

[henryho_hk]

only you can tell whether this deinterlacer is good enough. ppls said it's equal/better than tdeint(), while being faster too. not sure how it compares to tdeint+eedi2, though (don't you think it's a bit unfair?)

and MSP 6 is highly recommended.

---
edit ~ MSP = Motion Search Precision

[Wintershade]

What is MSP 6?
(forgive my ignorance...)

[imcold]

MSP = motion search precision.

[prOnorama]

Do you use Qpel and/or GMC? These operations can really slow things down

I get 6-7 FPS on an old Celeron 900 using Kernel De-Interlace, Medium Noise filter & Lanczos resize in Gordian Knot (Motion Search Precision = 6, VHQ for B-frames = ON, Chroma Motion = ON, Qpel/GMC = OFF, Trellis = ON, VHQ Mode = 1 (Mode Decision))

Your computers should be at least twice as fast as mine at similar settings I reckon

[Wintershade]

OK, thanks for the info.
One more question - I've been reading about yadif, it seems (based on what people say) it's among the best. Where can I find info on how to load it in AviSynth 2.57? I can't load it with the commands provided in it's readme file.

edit: okay found this, now can anyone explain to me a bit how the syntax works?
Thank you.

[kurt]

:search:
http://forum.doom9.org/showthread.php?t=124284&highlight=yadif
http://avisynth.org.ru/yadif/yadif.html

[Wintershade]

OK, I've read those. Does this mean that I should just put something like this in my scripts:

load_stdcall_plugin("C:\Program Files\AviSynth 2.5\plugins\yadif.dll")
Yadif (mode=0, order=-1)

or is there something more to add in here?
Sorry for my ignorance, but I'm quite new to writing AVISynth scripts and all that.

[henryho_hk]

loadcplugin("C:\Program Files\AviSynth 2.5\plugins\yadif.dll")
DGDecode_mpeg2source("D:\Temp\DP\Pod's Travels.d2v",cpu=4,ipp=true)
yadif(order=1)
Lanczos4Resize(640,384,6,76,708,424) # Assuming PAL, 424=576-76-76

# P.S. The resolution seems rather low.