Featured Articles

IHS teardown reveals Galaxy S5 BOM

IHS teardown reveals Galaxy S5 BOM

Research firm IHS got hold of Samsung’s new flagship smartphone and took it apart to the last bolt to figure out…

More...
Galaxy S5, HTC One M8 available selling well

Galaxy S5, HTC One M8 available selling well

Samsung’s Galaxy S5 has finally gone on sale and it can be yours for €699, which is quite a lot of…

More...
Intel lists Haswell refresh parts

Intel lists Haswell refresh parts

Intel has added a load of Haswell refresh parts to its official price list and there really aren’t any surprises to…

More...
Respawn confirms Titanfall DLC for May

Respawn confirms Titanfall DLC for May

During his appearance at PAX East panel and confirmed on Twitter, Titanfall developer Respawn confirmed that the first DLC pack for…

More...
KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 gained a lot of overclocking experience with the GTX 780 Hall of Fame (HOF), which we had a chance to…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Tuesday, 08 May 2007 07:08

MSI P35 Neo Combo benchmarked - 8. Gordian Knot

Written by Eliot Kucharik
Image Image

Preview: MSI P35 Neo Combo, Part one


Benchmarks:
We didn't bother with synthetic benchmarks, because they won't tell you anything
interesting, we concentrate on real world applications, especially multimedia encoding.

Gordian Knot/XVID 1.1.2:
For our Gordian Knot testing we took an PAL epsiode from "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 manupulation, 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 like to improve the picture quality, which is done by filtering the content. You can choose from tons of filters for any purposes you can think of, but we only used the most common "undot", "FluxSmooth" and "MSharpen". Of course we also de-interlaced, filters were applied before any resizing took place (which is slower). We marked this as "slow".

If you need more info about filters, we recommend reading the doom9.org forum.

Due to the bug in the BIOS we needed to run our 3200MHz test with CL5-5-5-13-CR2T, which only overclocking friendy memory can provide, but shouldn't influence the results measurable.

Image

(Page 8 of 9)
Last modified on Tuesday, 08 May 2007 08:32
blog comments powered by Disqus

To be able to post comments please log-in with Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments