Gordian Knot/XviD 1.1.3:
For our Gordian Knot testing we took a PAL episode of "Babylon 5" with a length of 41 minutes, 57 seconds and 8 frames.
We tried to "emulate" the most common usage of Gordian Knot:
1st: We have a perfect master, so we only de-interlace the content and resize it, without any other manipulations. We marked this as "fast."
2nd: You get bad mastering on many DVDs, especially "old" stuff or when the studios are in a hurry for the release. In this case you may want to improve the picture quality, which is done by filtering the content. You can choose from many filters for any purposes you can think of. We only used the most common "undot," "FluxSmooth" and "MSharpen." Of course, we also de-interlaced, filters were done before any resizing took place (which is slower). We marked this as "slow."
If you need more information about filters, we recommend reading the doom9.org forum
With this review we used x264 encode for an additional video encoding bench. x264 is a H.264/AVC codec which supports four threads and is available for free. We used the same "slow" settings like XviD. H.264 gives you a huge advantage in compressing size, and you need much less bitrate to achieve the same or better quality compared to XviD. While the H.264/AVC is much more advanced compared to MPEG2 encoders, now the CPU-power is available to do the encoding in an acceptable time.
You can clearly see that a quad-core brings an massive advantage in encoding speed; first passes seems to run on only two cores, but the second pass takes advantage of all four cores. With a quad-core you can nearly reach the speed of XivD, which can only use two cores for the time being.
The codec is open source, still in heavy development and you can grab it here.
Update: While testing a Q6600 we noticed discrepancies with the results of the QX6850. We rerun the tests and updated the chart. We apologize for the inconvenience.
We used the same episode for our MP3-testing. We don't recommend using MP3 for encoding, because AC3 can do the job better. The audio is almost 42 minutes long and it gives us approximately the length of most of album. A measurement in seconds, as many sites use, is useless, because the differences are too small.
We used the built-in play/CPU ratio, which means the CPU is encoding x-times faster then the track-length. Fast memory does not play an important role here. They will be produced with any other L.A.M.E. version, because only LameMT can do more than one thread and take advantage of a second dice. We used this setting: lamemt --vbr-new -q 2 -V 2 -m j --strictly-enforce-ISO --resample 48.
A quad-core does not improve the speed, because it can only utilize two cores.