Can anyone explain to me the function of

idct=5
and
cpu=4

in the line MPEG2Source?

If I want to do Kdvd from Dvd is right to use:

Mpeg2Source ("dvd.d2v",cpu=4,idct=5)
thanks

They are internal functions of the meg2dec3.dll.

Explanation/readme is delivered with the dll file or here:
http://mf.creations.nl/avs/filters/MPEG2Dec3.html

CPU:

cpu : 0 to 6.

DivX decoder like cpu level setting. - 0 : No PP
- 1 : DEBLOCK_Y_H
- 2 : DEBLOCK_Y_H, DEBLOCK_Y_V
- 3 : DEBLOCK_Y_H, DEBLOCK_Y_V, DEBLOCK_C_H
- 4 : DEBLOCK_Y_H, DEBLOCK_Y_V, DEBLOCK_C_H, DEBLOCK_C_V
- 5 : DEBLOCK_Y_H, DEBLOCK_Y_V, DEBLOCK_C_H, DEBLOCK_C_V, DERING_Y
- 6 : DEBLOCK_Y_H, DEBLOCK_Y_V, DEBLOCK_C_H, DEBLOCK_C_V, DERING_Y, DERING_C
(Y=luma C=chroma, H=horizontal V=vertical)
default : 0


IDCT:

idct : 1 to 5.

iDCT : iDCT algo used.
-0 : Default value (in .d2v file)
-1 : 32 bit MMX
-2 : 32 bit SSEMMX
-3 : 64 bit FPU
-4 : 64 bit IEEE-1180 Reference
-5 : 32 bit SSE2 (for P4)
default : 0

what is this?

Please, give me a answer more "simpler".

I am not graduated in avisynth.

byby

Dialhot, where are you?

CPU is for deblocking for example high compressed sources as divx, choose CPU=4 generally they will be spatial well treated.

IDCT is acording to your CPU type (as listed)

thanks, now is better.
by

Here is an even better explanation: using

Mpeg2Source("C:\Documents and Settings\user\Desktop\test.d2v",cpu=6,idct=5)

produces 6.3% lower data rate (6.3% more video per CD) than

Mpeg2Source("C:\Documents and Settings\user\Desktop\test.d2v")

at least on the test I did.
I did not see a difference in quality.

you should look better

cpu = 6 (deblocking + deringing) blurs/smoothes more

I would have say like FuPP

Deblocking has very low visual effect, but deringing blurs a lot.
That's why all my script use cpu=4.

I do not have the experience that you two have and apparently not as sharp of eyes either. Thanks for pointing that out. I will take a closer look.

Since zagor seemed to want a simple answer, I was just trying to point out why cpu is used in simple terms. Which for me has been to get more video per CD at low data rates. Sorry if I led astray.

Dialhot wrote:
Also those for Dvd ---> Kdvd?.

or only Avi ----> Kdvd, kvcd.

by

Also for DVD->KDVD.

I gave my script there :
http://www.kvcd.net/forum/viewtopic.php?t=8675&start=16

Read what inc said:
For DVD to KDVD, Kwag's Optimal Script don't use CPU command.
Dialhot's scripts are designed for DivX/Xvid to KVCD/KDVD.
(I think that Dialhot's thread "Latest optimal script for AVI to KVCD" it is for KDVD too)

You think wrong ! I do not do ANY Xvid->KDVD and I will NEVER recommand anyone to do that. But that's the subject of a (closed) discussion I had with Vmesquita about Diko.

So my scripts aren't for avi -> KDVD ans when I said I use cpu=4 even for DVD is only in the kind of script that I referenced in my previous post.

I know that Phil. I think in same way too, AVI to KDVD have not sense.
But my question is, if somebody want to make KDVD from AVI's, it will be usefull your V4 script?

Let say that is better than doing this with no script at all or even with another script (because this script quope with a lot of problems presents in avi sources). But I'm sure that something can be found that would be better to this particular purpose. I'm mainly worried by the resolution increase. And there is also the bitrate allowed on a DVD that permit to be less "heavy" on the filtering than when you target to do a 800 MB video.