Gordian Knot with x264 support is here (v 0.34.8 beta)

[len0x]

Something for the public to play with. Head off to sourceforge to get latest beta that supports x264 codec (I used latest build from celtic_druid here: http://celticdruid.no-ip.com/xvid/ Note that x264 doesn't include decoder atm, so to be able to play its files you need to install latest ffdshow from the link above).

please note that x264 is still in alpha developemnt stage

Upgrade instructions:
always uninstall x264 before installing new revision, then always delete
- default_x264_firstpass.settings
- default_x264_secondpass.settings
in GK folder after upgrade of both GK and x264

0.34.8 beta

- fixed comp test for x264 on advanced SaveAVS window
- MPEG2 decoding library setting is removed (GK always uses DGDecode.dll from where DGIndex.exe resides)
- DGMPGDec updated to version 1.2.0 RC3

0.34.6

- fixed loading of "don't check" check boxes on the path tab
- fixed first comp test script upon startup of GK
- DGIndex is updated to version 1.2.0RC2

0.34.5

- fixed opening of AVI files (any kind that has proper VFW decoder installed can be opened now)
- DGIndex updated to version 1.2.0b6 (1.1.0 was not recommended for usage)
- filters xml definitions are updated

0.34.4

- Frame overhead is always checked for x264
- comp test startegy is changed for x264 (now its discarding first and last frames for non bframes encode and first two/last two frames with bframes encode)
- XviD AVI dev-api3 can be opened again
- deinterlacing section is moved before crop to avoid green line problem
- added logo for x264 (my lame variation on XviD theme )
- DGMPGDec is updated to version 1.1.0
- ColorMatrix filter is included with its xml description (read about its usage here: http://forum.doom9.org/showthread.php?s=&threadid=82217 )

0.34.3

- bitrate propagation for x264 fixed again

0.34.2

- now only support rev 107 and up of x264
- fixed bitrate propagation for x264

0.34.1

- comp test changed to use common strategy as was used for b-frames.
- min&max key frame distance is swapped in rev 103, so GK was changed to compensate for that

initial version 0.34 and comp test:

- quant 18 single pass encoding is used
- snip size of 20 frames is used (as well as min-key interval=20)
- without b-frames algorithm's using all frames for comp test (works within 5% in all my tests so far)
- with b-frames algorithm's discarding starting and ending 3 frames (doesn't really work in 100% of cases - much more work to be done here).
- you should still aim at about 70% quality

Enjoy.

[len0x]

Wrong time for the forum to be down

Anyway version 0.34.1 should work with rev 103 until x264 developers will fix keyframe settings, then I will need to update GK back...

[niamh]

Ha, I managed to get 0.34 yesterday morning, haven't tried 0.34.1 yet.

Thank you very much for the New Year surprise len0x, it's very much appreciated
I will try 0.34.1 asap

[len0x]

Note that rev 105 of x264 that is out may not work as they introduced stats file parameter. I'll wait until min/max keyframe issue is fixed and then release 0.34.2 with support of later revisions.

[The Edge]

Thanks alot for your continued work len0x

[Bluedan]

GordianKnot is still the one application in the centre of my video encoding activities.
I like it very much.

Thank you for this update!

[Koti]

A wonderfull unexpected addition to one of my favorite toys -

[b0b0b0b]

Hi len0x, thanks very much for your work on gk and autogk

[netchris]

Revision 106 is up
Fixes : registry values for min/max keyint were mixed up

[niamh]

Well I got a 129 mb file instead of 221 with rev 105 so it seems it does not work
Is it a case of the codec is developping faster than the app?

By the way the bitrate was slightly off when I tried an encode in 0.34(with whichever rev, an older one), and notwithstanding the big error in the filesize this time, the bitrate sent to vdub seems to be off again .I explain, in the GK window it gives me a bitrate of 1373 kbps(it's the correct one), and the rate sent to vdub was 1346 . (same deal first time, where I got a 218 mb file instead of 221)

[len0x]

Originally posted by netchris
Revision 106 is up
Fixes : registry values for min/max keyint were mixed up

I don't see binaries yet...

[len0x]

Originally posted by niamh
Is it a case of the codec is developping faster than the app?

So far its codec developing faster then QA can be done and therefore last two revisions do not work properly (at least with GK) at all...

Originally posted by niamh
I explain, in the GK window it gives me a bitrate of 1373 kbps(it's the correct one), and the rate sent to vdub was 1346.

This seems to be a 1024 vs 1000 bytes in 1Kb problem: DivX 3.11 is using 1000 bytes notion, while the others are using 1024. I will change that in GK.

[niamh]

I got twice a 129 mb file, that corresponds exactly to a 800kbps CBR, as discussed in the x264 thread. It's consistent

[len0x]

not sure what you meant...

[niamh]

but second time codec resets itself to CBR mode (although registry settings are correct!).

hhmm, that, unless I got confused

[len0x]

ah

We found the problem (well, virus found it) - we are chatting live on IRC...

[niamh]

any chance to get the addy so I can get in, sit and learn? (or get a headache)

[len0x]

#x264 on freenode network.

[niamh]

Thank you, I got pounced on and served with a bugfix release Going to test as soon as vdub is free.

[len0x]

So it should be ok to use for testing purposes now. Please leave feedback about problems with encoding itself in x264 development thread here: http://forum.doom9.org/showthread.php?s=&threadid=80910

P.S. Latest revisions of x264 can be found also here: http://www.iti.uni-stuttgart.de/~ber...or/videotools/