Is GordianKnot dead?

[Elias]

It's been 0.35 for a very long time now. It used to get frequent updates in the past.

[E-Male]

any problems that would make an update neccesary?

[guada 2]

The men die, but the data rest.

In my opinion it is only there, no more. :D

[Doom9]

well.. being open source it's never really dead because anybody can pick up development at any time. And looking at dvd2svcd, there was a new build after 14 months of inactivity. I'm pretty sure that once DXN provides a means to configure their DivX6 series and future 6.x versions using the same mechanism for every build, we'll see an update there again. But if you're looking for stuff like MP4 output or more on the input side, turn to AutoGK or the tools you'll find in the MPEG-4 AVC forum (MeGUI et al).

[Elias]

well.. being open source it's never really dead because anybody can pick up development at any time. And looking at dvd2svcd, there was a new build after 14 months of inactivity. I'm pretty sure that once DXN provides a means to configure their DivX6 series and future 6.x versions using the same mechanism for every build, we'll see an update there again. But if you're looking for stuff like MP4 output or more on the input side, turn to AutoGK or the tools you'll find in the MPEG-4 AVC forum (MeGUI et al).Well, mp4 output would be neat, but that wasn't really what I wanted. I do mp4 pretty much my own way with MP4Box cmd, and that kicks major ass :D I just want to use the latest up to date software, and GordianKnot has gotten quite outdated today, and in need of an update... in my opinion at least. I can't do AVC, my computer is 950 mhz with 256 mb sdram. It's painfully slow.

As for DivX 6, I don't think it should be slowing down the progress of GordianKnot. DXN is going their own way; they were even supporting mp4 and open standards (they praised it for being an open standard file format that would make sure people didn't get locked in different fileformats from different companies, and now that's pretty much what they're doing with *.divx) in the beginning, but now they've concocted up their own DivX media fileformat with their own subs and all, and they have Dr. DivX, so I doubt that they really care about GordianKnot.any problems that would make an update neccesary?Yes, actually there has been some issues with DGIndex with some specific MPEG-2 streams (the first frame sometimes gets b0rked, for me at least). The codec pack needs an update too. Let's just put it like this: the software GordianKnot uses is getting rapid updates (especially x264), and GordianKnot is not keeping up with the software.

My 2 centsThe men die, but the data rest.

In my opinion it is only there, no more. :DHahah! Good one ;)

[guada 2]

Indeed, it would be interesting to know what can still give GK at its stage of development.
I am not developer. But I think that Gordianknot is very good software.
But the practice to accept comfort often takes different proportions.
AutoGK, is a pass key without constraint and very easy to use whereas GK to the advantage of proposing a double personality (manual and automatic) of quality.

The developer is often prone to the opinions increasing of young interested.
Thus, the consumer make his business.

[stax76]

I'm pretty sure that once DXN provides a means to configure their DivX6 series and future 6.x versions using the same mechanism for every build, we'll see an update there again.

They did something in 6.0.3, the problem with their cli approach is you have to hardcode the default command lines in order to provide reasonable defaults for first and second pass and comp. check. Only parameter that must be accessed is the bitrate if you don't count B-Frames for the overhead calculation. The problem now is if a new version comes out you are still working with the old command line so it has to be updated using the config dialog. So yes, a experienced user can continue to work with the application. With the old/XviD method you can set default values for certain values and you don't have to rely on regex to modify the bitrate though generally not a problem. I must admit it's a small limitation and I'm not sure anybody not working on a DivX application can understand what I'm writing. I hope at least somebody find the cli useful. I've never seen somebody using it though.

[Doom9]

well.. cli works if you're basically coding your own codec configuration dialog. MeGUI takes that approach. Of course, you can read the commandline from the registry, strip the bitrate from it and put the new bitrate in there, then start encoding.

I don't see what the problem is with x264 though, you can simply use the latest build.. I've never had an issue with GKnot and D2A /D2ADG or DGIndex so I don't get the problem there either. Just because a codec pack is outdated doesn't mean you can't switch out the apps it contains.

[Elias]

I don't see what the problem is with x264 though, you can simply use the latest build.. I've never had an issue with GKnot and D2A /D2ADG or DGIndex so I don't get the problem there either. Just because a codec pack is outdated doesn't mean you can't switch out the apps it contains.Well not everyone has the coding skills you have ;) n00bs like me need it all setup from the get-go to understand anything :)

[len0x]

n00bs are not supposed to be using GK...

[Elias]

n00bs are not supposed to be using GK...Well I understand GK relatively well, so I'm not that much of a n00b.

[iradic]

i was always wondering what happens if you copy only gordianknot.exe to a new comp where it was never installed , will that work?
of course then you manually set up program paths you want etc ...

[stax76]

i was always wondering what happens if you copy only gordianknot.exe to a new comp where it was never installed , will that work?
of course then you manually set up program paths you want etc ...


Why not try it? Personally I appreciate the simplicity of xcopy compatible applications very much and ask authors to support it though at least I copy the complete directory of the application.

[len0x]

Copy of a complete dir of the application would always work for GK - its totally standalone package(providing avisynth and vob sub installed separately) and registry keys are recreated on startup anyway.

[iradic]

Why not try it?

he he, i have only one comp ...
soon i will have the chance to try though ... (fresh OS install)

thanks, bye