Log in

View Full Version : MeGUI vs Gordian Knot


Bh4i
30th September 2006, 00:03
I want to know something i couldnt find here. I want to encode a DVD to Xvid. Like most ppl, i always used Gordion Knot.
But i noticed MeGUI can also handle xvid encoding.

So i wondered: what is the difference in quality between encoding with MeGUI & Gordion Knot. I as a newbie thinks there isnt any difference in quality, because quality depends on:
- AVS script (filters used)
- Xvid settings used
- Matrices

Plz correct me if im wrong :o

kurt
30th September 2006, 00:51
XviD in MeGUI is native (uses xvid_encraw), has direct mkv ouptut and it is also possible to mux in different containers automatically

XviD in gk is vfw

btw: if using forumsearch with encraw native, multiple threads will show up :)

check
30th September 2006, 05:00
apart from what kurz listed, there will be no quality differences. As you correctly assumed, quality is dependant on two factors: input and encoder settings.

Blue_MiSfit
30th September 2006, 05:08
Very true, but MeGUI has several distinct advantages

1) Native support for AAC Audio
2) Native support for x264
3) Automatic Deinterlacing
4) Auto Update

These 4 for me make it a no-brainer to use it exclusively.

Still, Gordian Knot is very much capable of creating fantastic looking AVIs, so if it works and you don't need anything more, why switch?

~MiSfit

Bh4i
30th September 2006, 05:13
Well, i like that detecting deinterlaing in MeGUI and u have to set soooo many options in Gordion Knot :o

But i do know that Gordion Knot has something like a "compresssibility test". Never seen this option in MeGUI.... isnt this function needed for Xvid encoding?

CWR03
30th September 2006, 10:46
It's not needed, it mainly helps in deciding the resolution and file size based on how it will compress.

xyloy
30th September 2006, 12:40
Well, i like that detecting deinterlaing
But when I used "TDeint + EDI (slow)" I had _a lot_ of deinterlace artifacts... I should have tested the others solutions MeGUI gives, I guess.. :P

MeGUI's interlacing detection is ok, but choosing the first deinterlace methode available in MeGUI's AVS Script Creator after the detection process is not a very good idea.

So "no-brainer deinterlacing" is, once again, a dream.

BTW, I prefer to use TDeint for 25 FPS PAL movies, and TIVTC(tfm with tdecimate) for 29.97 NSTC movies(TIVTC converts it to 23.976), this way deinterlace artifacts are nowhere(*). No need for MeGUI, only DGIndex and Windows' notepad..

(*) Thx again, Teegedeck :)