Eocoder Test - here are the results

[ninja.rogue]

File size: PAL DV AVI 30" - children into swimming pool
System settings: Dual Xeon 2.4 with Supermicro P4DCE+, 1024 MB Rambus Samsung PC800
Standard Bios setting (no overclocking or performance enhancing optimization)
W2k pro SP2 and XP pro - no sp
DC precision 10
Standard matrix for Tmpgenc
vbr setting min 2000 avg 6000 max 9000
Program release: Tmpgenc 2.59 Plus and Procoder 1.035
Both encoders have been set to High priority into task manager
Source file is on separate disk than target file

Encoding Times:

Windows XP PRO - ht enabled
Tmpgeng hq 2pass vbr 3' 25"
Procoder hq 2pass vbr 2' 38"
Procoder mq 2pass vbr 13' 35"

Windows 2k PRO - no ht
Tmpgenc hq 2pass vbr 3' 00"
Procoder hq 2pass vbr 1' 54"
Procoder mq 2pass vbr 8' 20"


Windows XP PRO - ht disabled
Tmpgenc hq 2pass vbr 3' 23"
Procoder hq 2pass vbr 2' 12"
Procoder mq 2pass vbr 12' 55"

Average Q value:
Tmpgenc hq 7.7
Procoder hq 4.68
Procoder mq 4.63

I remain waiting for your comments
Cheers
Paolo

[cool]

Welche von den Zahlen sind die SECHS richtigen?
Habe ich gewonnen?

Wie gross ist der Durchschnitt aller Zahlen?
_________________
Wenn ich all mein Equipment aufzählen täte, ist die Seite vollgemüllt.

[DV User]

Hello Paolo,

unfortunately the only really usefull result I can get out of your test is that both programs are slower on XP than on w2k (just another reason not to change to XP). And that ProCoder with mq is painfully slow which isn't a new fact.

A 30 sec. clip is much too short for a 2pass vbr test. Especially if there are 30 seconds of full (water) movement in the clip. Also the Q values doesn't tell you all about the visual quality of the resulting clip. I can give you an impression especially when comparing the resulty of one encoder. E.g. if you compare a clip encoded with TMPGEnc and CCE which show nearly the same artefacts on the sceen the Q values are totally different.

BTW was TMPGEnc set to use multiple threads? Looks like it it's a bit slow for this machine.

DV User

[ninja.rogue]

Yes, Tmpgenc had hyperthreading enabled into cpu environmental settings.
What could it be the reason for the lack of speed?