Is the legend of GordianKnot alive?

[har-vas]

Hi. I am using GordianKnot for almost 4 years now and I love very much this program, because I have spent countless hours with it and it has helped me a lot with my encodes. I was very happy when I saw (at the early of 2005) that it has added support for the new mkv container and the next-generation x264 codec. The last 1,5 year, since the latest (real) version of GK, v0.35, I am using MKV container to have all my chapters and subtitles inside a file and I am also using x264 codec, which is awesome. I am very satisfied with the results and with all these capabilities, that's why I don't use AutoGK or any other simple tool. Well I believe that GordianKnot is a legend for all the faithful rippers out there and I don't want to see this program dying, at least when this is not really inevitable (technically). I see that many tools and codecs which GK uses for the encode process, do continue their improvement, so why not GK? But enough sentiments, here my real questons:
1) Should we wait for a new version of GordianKnot with (except from any bug fixes) support for DivX 6, new audio codecs or even new containers? Or should we accept that game is over?
2) I am using now the x264 revision 556 and I cannot find the latest versions (>580) in the well-known x264-xxx-install.exe form with the installer and configuration panel (I used to download from free-codecs). I have not really understand which is the difference between this version and the cli-only version of x264.nl (x264.exe). Both free-codecs.com and x264.nl say: "Vfw and installer removed from auto update, vfw is outdated". Does this mean that I can't use the newest versions of x264 with my favorite GK?
3) Can someone explain me please (or supply a relative URL) what exactly is this vfw mode and (mainly) why is so bad? What I gain if I use the so called "native mode" of x264? Speed or quality?
4) When a new build of x264 is out, I am just unistalling the old one and then I am installing the new version, keeping the default_x264_firstpass.settings (and secondpass) files intact. I see from the codec's panel that the settings are kept as before. Is that correct, or I have to delete the files, re-enter and re-save the default x264 settings from GK's "Options" tab for the new version to work correctly?
5) Lastly, I read about MeGUI ("the combined successor of Gordian Knot and Auto Gordian Knot") and its capabilities and I have also installed it in my system. It looks really powerful but to be honest, I want to know FIRST if GK is really dead, before I decide to read a comprehensive guide, to combat with its numerous settings, to experiment with my first encodes, to troubleshoot with it etc. You know what I mean... Anyway, I believe that it is in an early development stage from every point of view ("MeGUI is still undergoing heavy development, and we plan to simplify the interface a lot"). So please, don't point me in this program, skipping my GK-related questions (this happened to many other "GK-asking" posts). I would like from you to try answering to my x264 and GK related questions first and I promise to read more about MeGUI, before I post anything here.
Thank you all.

[Blue_MiSfit]

IIRC Gordian Knot development is dead.

The reason you can't find any newer x264 VFW builds is because they aren't making VFW builds anymore. Look into the AVC forums to read up about it, though it's a touchy subject.

~MiSfit

[agressiv]

Definitely check out MeGUI, which is more aligned with what you are trying to do than AutoGK.

http://mewiki.project357.com

I use it with DVD inputs for x264/MKV as well. While its not as brainless as AutoGK, its definitely simpler than old GK IMO :)

You'll need the .NET Framework 2.0 if you don't already have it.

Otherwise, there is a program being developed called AutoMKV (http://forum.doom9.org/showthread.php?t=113811) (which is somewhat similar to AutoGK, yet uses x264 and MKV) and is much simpler than MeGUI. It just lacks batching.

MeGUI is much more developed than AutoMKV, and is stable. I think one of the developers is porting it to linux, so its been fairly stable lately, other than occasional updates to x264.exe. Its auto-updating (but alas the auto-update server is currently down, so hang tight) which is a nice feature.

agressiv

[Henrikx]

While its not as brainless as AutoGK

Your Words are angry and stupid at the same time

[BigDid]

... While its not as brainless as AutoGK, its definitely simpler than old GK IMO...
Sir,

Two points if you please:

1/The author of AutoGK may or may not appreciate your formulation; at least it may infringe Rule 4:"Be nice to each other and respect the moderator. Profanity and insults will not be tolerated... "

2/ I strongly disagree with your -AGK is brainless- formulation
- Agk uses and chooses between
* 2 regular and 2 (even3) custom matrixes
* 2 different SAP (players) profiles
- It has a powerful comptest
- It can accepts video input like MPEG1/2, VOB, AVI's, some TS streams ...
- It can process DTS/AC3/MP2/LPCM, keep original(s) or encode to MP3 VBR or CBR
and many more features see FAQ: http://forum.doom9.org/showthread.php?t=72679

From your other posts it seems you can be constructive, please continue to do so and do us, AGK users, a favor if you please, forget this section.

You have my regards for the first and last time because, from now on, your posts will be ignored.

Did

Edited to rectify a mis-comprehension

[CWR03]

The above is not a statement it is your opinion. If you keep this sentence, I strongly wish you edit your post and make clear that it IS your opinion.
I believe that he meant that it's relatively brainless to use since it was designed for functional simplicity. Besides, he did say "IMO" (which stands for "in my opinion").

[check]

sounds like a case of the insult that wasn't actually there!

to the OP, I'd also recommend you play with MeGUI - just be aware that the update server is down, so you will have to wait til it revives :)

[BigDid]

I believe that he meant that it's relatively brainless to use since it was designed for functional simplicity. Besides, he did say "IMO" (which stands for "in my opinion").
Hi CWR03,

You are right for IMO, I will edit my post but brainless is brainless, aka a strong pejorative word :(
Thanks anyway.

@Check, I did not mention insult, I quoted rule 4 which begins with "Be nice to each other... "

Did

[har-vas]

Hi again. I saw that many of the above answers were out of the thread's subject because of a careless expression. This is a known problem in the forums, so we should all try to respect the rules and be very scrupulous with our posts. For example, it's a matter of principle for me to give feedback when I receive help or instructions from someone. I believe that this increases the productivity of a forum as a source of information.
Anyway back to the subject, If I understood correctly, the development of GK is dead. Is this an author's decision or just a conjecture? I hope that lenox will see this thread and answer all my questions. I definitely believe that GK can be refreshed and useful again. I think that one or two releases per year will be adequate for that, but I think that now all the efforts go to AutoGK due to the larger range of users.
As for the x264 VFW, I read a lot in the AVC forum and I understood that is really hard to see a newer version (the latest available in VFW is 573). I hope to be found at least one developer to work on that, even for 3-4 releases per year. I will gradually turn in native mode of course (starting with AutoMKV), but I would like to have more options available in the meantime. As for my third question, I tried to find information in wikipedia, but a compendious reply from an expert would be welcome (especially in the speed or quality issue). My fourth question was not answered and I think that only few people can do that. Thanks.

[kikounet]

Hi har-vas,
I agree with your original Post. I much prefer the "good old" GK, although i understand "Auto" can be nice for people not willing to deep into tons of details.
What I like in original GK, amongst others, is its precise ability to let me decide exactly what line i want to crop, what ratio i want to deform my video, etc.

Please Mister Tony Lenox, don't let die your pure jewel !

Note: VFW stands for Video For Windows, the previous way of accessing avi files, now replaced by Direct Show(DS)...

[Brother John]

2) & 3) GK depends on VirtualDubMod which depends on VfW which is a video framework originating from Win 3.1. It's outdated and has a bunch of problems with modern codecs. Not only H.264/AVC but also XviD/DivX. Speed or quality is not the main issue, rather video streams that have to break MPEG-4 specs to be compatible with AVI. Simply put AVI is a part of VfW. VfW support was removed from x264 with revision 581.
If you understand German you might want to try agkp (http://forum.gleitz.info/showthread.php?t=22860), which is an addon for GK adding x264 cli, MKVMerge and extended AviSynth filter management. Unfortunately afaik no English documentation exists.

1) & 5) Since there is a new version of AutoGK len0x seems to be active again. However Gordian Knot’s source code hasn't changed, so I wouldn't count on any further development from his side. Because GK is open source someone else could take over easily, though I doubt anyone will find the will. The effort to cut GK’s ties to VfW would be huge. I’m a little sad myself that GK seems to have reached the end of its lifetime. After all I did my first clueless DVD backup with that program. But the fact remains: GK depends entirely on an old encoding framework which is not (or only with hacks) compatible to modern codecs and containers – especially H.264 and MP4. So in the end you have two choices: Stay with good old GK and AVI or move on to the recent technology and change your frontend. Well, theoretically there’s a third one: Download the GK sources, fire up Delphi and get to work.
When looking for alternative frontends don't limit your options to MeGUI. There's also StaxRip, AutoMKV, RealAnime... Browse the "Encoder GUIs" forum to find your favourite.

4) Keeping the .settings files is probably ok. But if you want to be 100% sure delete them and reconfigure.

[kikounet]

GK depends on VirtualDubMod which depends on VfW which is a video framework originating from Win 3.1. It's outdated and has a bunch of problems with modern codecs. Not only H.264/AVC but also XviD/DivX...
I loved that explanation!
Question: What replaced VirtualDubMod for AutoGK to depend on?

Could we expect AutoGK to get a "more advanced/secret" settings tab to allow us the very flexible and precise cropping tab of "good-old-GK"?
Pleeeeeeease Tony! :)
Thanks to all for helping.

[CWR03]

Could we expect AutoGK to get a "more advanced/secret" settings tab to allow us the very flexible and precise cropping tab of "good-old-GK"?
You can already crop in even numbered increments, you just don't get a realtime display of what's been cropped. You can always use GordianKnot to determine the crop needed and transfer the numbers to AutoGK.

[numaios]

I agree with you, CWR03. I think "brainless" just means "with lack of control from the user", a little bit like DivX Converter (please forgive me if this comparison is offensive, but I can't know if AutoGK is better/smarter because its modus operandi is kind of a secret).

You can always use GordianKnot to determine the crop needed and transfer the numbers to AutoGK.
You are right, and we can always use GordianKnot to decide how much bits/(pixel*frame) we have with certain resolution, and then transfer that resolution to AutoGK.

But in both cases we are using more than one all-in-one tool. Maybe that's what kikounet meant.

What replaced VirtualDubMod for AutoGK to depend on?But AutoGK uses VirtualDubMod, doesn't it?

[har-vas]

Brother John, thank you very much for your detailed answers. I am posting just for that. Unfortunately, I can't read German, so I can't understand the (28-page pdf) documentation, which seems excellent, and also the posts for the very interesting AGKP! I am very sad about that, because AGKP sounds like the solution to my problem (substantial upgrade of GK). I hope that a German citizen will be found to translate the documentation for me and others like me! Anyway, in the meanwhile, I will try some of the new front-ends.

PS: Brother John, if you have worked with AGKP, I would like to hear your comments and opinion for this program. Is it handy, reliable and effective? Do you have personal experience? Thanks.

[Brother John]

Agkp indeed is a nice piece of software. Because of the weird scripting language the avs filter feature needs some getting used to. But x264 cli and MKVMerge is straight forward and works flawlessly. I'm trying to get some English documentation done for x264 and MKV. But don't take this as a 100% promise.

[Brother John]

Keeping that promise:
http://forum.doom9.org/showthread.php?t=117883