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

[len0x]

It works like this:

- when you add the job settings are copied from defaults if you don't specify them explicitely
- if you specify them by launching codec settings from Encode window then
-- first time they are loaded from defaults
-- all consequent times they are loaded from the file in the output directory
-- even if you load them first time then they might be loaded from jobname_firstpass.settings in the output dir if it exists (so make sure to delete all *.settings from output folder).

[niamh]

I see, thanks for the clarification. I cleaned up my testing folder yesterday indeed, today is a mess of files again. I'm glad to learn about that little quirk.

(That was it indeed, now it all makes sense and works as well)

[niamh]

I'm not able to open a dev-api-3 xvid avi through the open d2v button... It makes GK simply vanish into thin air. (All builds of Xvid 1.x seem to open fine, as well as the x264 ones, may I say)

[len0x]

Well, I did that for 0.33.2 - previously you could open pre 1.0 AVIs OK, but not dev-api4. Now it happens vice versa (they are mutually exclusive it seems) - I think it makes more sense to have as now as dev-api-3 is obsolete.

[niamh]

It sure does indeed. I wonder what's so special about xvid, since all the other codecs seem to play nice in this case..

[len0x]

Its coz M$ avifil32.dll library cannot properly work with XviD. If you right click on xvid file in windows you'll see very weird info about it being 12 bit, that screws things when you try to access video frames...

[Mtz]

I think the latest v 0.34.3 beta is not working with miniDV input transfered via firewire. :(

enjoy,
Mtz

[len0x]

Afaik it was never supposed to work (i.e. dv/huffyv/mjpeg)

[killingspree]

hi,

yesterday i did my first encodes with x264 and gknot and i have to say, i'm impressed at how fast this was implemented so well...

anyway, for some comparisons i encoded a couple of chapters of LOTR SEE at a high res with a rather low bitrate (645kbit, 704x288) - still an acceptable bitrate, but definitely not overkill ;) - and encoded it with xvid and x264 (no noise reduction, lanczos resize); as expected, overall xvid fared a little worse, although on easy two encode scenes, there was hardly any difference.

what i had noticed though, was the fact that in some areas, it seemed to me the xvid still preserved more details, whereas x264 presented a little smearing. on the other hand, xvid had scenes where it was blocks and nothing but, and x264 still had watchable results...

anyway, that probably belongs to the x264 dev thread. bottom line, encoding with x264 in gknot works fine so far, thx len0x, just now i'm doing a 700MB encode to see if there's any surprises...

oh and btw, the file sizes are still marginally off, no matter if i use calculate frame overhead or not

steVe
PS: if anybody wants some screenshots, just drop a message here, i've got quite a few...

[len0x]

Originally posted by killingspree
what i had noticed though, was the fact that in some areas, it seemed to me the xvid still preserved more details, whereas x264 presented a little smearing. on the other hand, xvid had scenes where it was blocks and nothing but, and x264 still had watchable results...


It is possible that XviD preserve more details sometime (especially if you use custom matrixes). Also x264 looks much better to me without usage of b-frames atm (plus reference frames has to be increased from default 1 to at least 5).

Originally posted by killingspree
oh and btw, the file sizes are still marginally off, no matter if i use calculate frame overhead or not


you're the only one having such problems it seems...

[len0x]

I consider first stage of x264 integration as completed. I did more tests and tuned comp test result according to that.

*Edit* also I was able to do two types of loading for AVI files that should be ok for both types of XviD.

P.S. plz have a go with ColorMatrix filter - should be interesting to see the results (those who complained about encodes being too dark might be happy with this filter).

[killingspree]

Originally posted by len0x

you're the only one having such problems it seems...

hmmm... well i'm going to run a couple more tests asap using the new beta and i'll see if they persist...

[len0x]

Make sure you have x264 properly installed (i.e. uninstall any old version you might have).

[Koti]

Small bug in color matrix .xml or my system
"Rec.601->Rec.709" and "Rec.709->Rec.601" are entered in quotes " in the string presets which results in the final entry being double quoted.
ColorMatrix(""Rec.709->Rec.601"",true) in the avs file.

All the rest is great , even a x264 logo :) .
Thanks

[Hesse]

I am having some problems with updates after GK 0.33.1. I am trying to reencode some AVI files of very large size, ~16GB. GK 0.33.1 can open the file and process it like a charm. However, any version after just quits when I select the file to open. I also tested a 2GB file and it does the same thing, simply just quits, no errors or anything.

Any chance this could be looked at?

Thanks,

Jesse

[jsprogg]

i am testing the GK 0.34.4 beta and all is well except for the file load option for avi, it loads divx5 and div3 fine but trying to load xvid avi's the app just shuts down.
i have tried several xvid files and get the same problem with all of them.

[thewonderer]

It seems as though there are problems with the download links for the 1.89 beta of autogk. i've noticed this before with previous versions.

Access denied/no permission...

Please fix

Thanks

[len0x]

Please don't ask questions about AutoGK in this thread! (and read FAQ Q 0)

[len0x]

Originally posted by jsprogg
i am testing the GK 0.34.4 beta and all is well except for the file load option for avi, it loads divx5 and div3 fine but trying to load xvid avi's the app just shuts down.


Did you have the same problem with 0.33.1 and 0.33.2 ?

[len0x]

Originally posted by Hesse
I am having some problems with updates after GK 0.33.1.


Version 0.33.1 had original old code. Then I modified it to be able to open new XviDs in 0.33.2. Now in 0.34.4 I've put old code back but in case it fails I'm trying new code second time. So 0.34.4 should not behave any worse than 0.33.1.

[len0x]

Originally posted by Koti
Small bug in color matrix .xml or my system
"Rec.601->Rec.709" and "Rec.709->Rec.601" are entered in quotes " in the string presets which results in the final entry being double quoted.
ColorMatrix(""Rec.709->Rec.601"",true) in the avs file.


Indeed on line 17 you should remove "quot;" twice (along with ampersand) from the string if you want to fix it yourself.

[niamh]

So 0.34.4 should not behave any worse than 0.33.1.
As a matter of fact, it behaves the exact same :D
Fat chance of M$ fixing their dll, so we'll have to live with it :)

[len0x]

Originally posted by niamh
As a matter of fact, it behaves the exact same :D


Not really - 0.33.1 couldn't open dev-api4 XviDs while 0.34.4 can...

[niamh]

Woops, I was thinking 0.34.3 ;)

[jsprogg]

Did you have the same problem with 0.33.1 and 0.33.2 ?

To be honest Lennox , I don't recall trying it with xvid in 0.33.1 or 0.33.2 , reading back on this thread I guess that it is intentional and that my test files are simply older xvid versions.

[len0x]

I have no problems opening any kind of XviD files with 0.34.4.
Can you make available a small sample of what you can't open with current version?

[jsprogg]

ok I re-installed GK 0.34.4 and can now open xvids fine, i still have one problem file although i can't seem to detect just why it's a problem,i checked it in v-dub and it doesn't seem to have any errors or be corrupt.I did split a little off the file but the sample opens fine in GK ..lol
so I am hoping that this file has a unique problem.

[niamh]

@len0x:Well I've just reformatted, and I still can't open dev api 3 xvid. You can get a little sample of one of my reluctant files here (http://c.1asphost.com/niaomalley/dev-api-3.sample.7z). Not that it matters greatly really, but you asked :)

[len0x]

Well I never said that if you were not able to open some XviDs of dev-api3 with 0.33.1 that you will now. All I said that all XviDs that you were able to open with 0.33.1 you should still be able to open with 0.34.4 plus dev-api4 files can be opened as well.

P.S. I wonder if that's QPEL that makes it impossible to open, btw.
(All samples that I have of dev-api3 are without QPEL and work just fine, but yours is with QPEL and gives us the troubles).

[niamh]

I'm not sure I tried that file in 0.33.1, but I can't recall one that didn't open( I kinda test the same ones, and this one I know has Qpel, so usually it goes first).I've binned it, so I can't try to reinstall it. Thing is, none of my dev-api-3 open, that's what I was trying to say. It seems to be me only though, so no bother ;)

(edit:I'm on 56k, and it'd take an hour to get the whole pack back, I might try another day when I have time online)

[len0x]

I tried your sample in 0.33.1 - didn't work...

[niamh]

Thanks for trying :)
Can we revert situations and somebody send me a little sample of a dev-api-3 that opens for them? because I can't get a single one to open, I'm being curious.

[sillKotscha]

I don't know if my question is answered here somewhere - if so, link me ;)

... starting with version 0.34.4, for me it is not possible anymore to open an(y) *avs script.

going back to v0.33.2 everything works as expected :)

and somehow opening captured huffyuv files > 2GB let GK work and work and work and than crash...

huffyuv version used is: Huffyuv v2.1.1 CEESP-Patch v0.2.5

I didn't tried versions below. This does happen with both mentioned GK versions but as I said, with v0.33.2 I'm at least able to open huffyuv files > 2GB via avisynth

what else do you need to know?

cheers Sill

[len0x]

After reading specs for AVI files, WinAPI docs and analysing a bunch of files last night I sorted all the problems for opening AVI files (haven't tried AVS yet). Its not about the codec its about AVI structure that is very different for different files (and just happen to be different for different codecs). Now I'm able to open everything that has proper VFW decocer installed (i.e. can be opened in VDub). I tried xvid/divx/huffyuv/mjpeg - all went fine. I only had problem with DV source (dvsd) that I was decoding via ffdshow_vfw (I kept getting access violation in module ff_vfw.dll).

*Edit* AVS works as well

[len0x]

Should fix all you AVI problems :)

[The Edge]

Cheers for your continued efforts len0x ;)

[niamh]

Everything opens, I'm very impressed. Being in charge suits you Len0x :D
:thanks:

Hi Edge :) (OT: Did you manage to get tickets? ;) )

[sillKotscha]

hey len0x,

how nice :)

thank you... !!!!

that was really quick.

Sill

[The Edge]

Originally posted by niamh
Hi Edge :) (OT: Did you manage to get tickets? ;) )

Nope! :(

PM sent! :)

[digidragon]

I'm using the core 14 build of x264, and am getting an error in vdubmod: "Cannot start video compression - maybe corrupt data (error code -100)" when it tries to encode the avs generated by gk. However, if I just encode the mpg (the original source in the avs) then I don't get an error.

Any ideas please?

[niamh]

This is yet another x264 error, it doesn't like for example certain resolutions, you must take it to the x264 dev thread :)

[len0x]

Originally posted by digidragon
I'm using the core 14 build of x264

Is it rev 114? There were some errors fixed in rev 115 and you can try it. If doesn't help, then report it in the x264 development thread.

[digidragon]

It's rev 115.

After a bit of playing it's the crop and resize functions (either of them) that cause the error.

Using gk's auto crop, these are the two lines in the avs file:

crop(6,16,712,548)
LanczosResize(712,376)

[len0x]

Yeah, they might. What if you try to stick to mod16 resolutions?

[digidragon]

Thanks for the suggestion.

I posted in the X264 thread and they suggested that too. And it worked. I also mentioned that the codec properties don't mention any restrictions on resolution, as some others do.

Is it normally a good idea to stick to mod16 in xvid too?

[Dester]

I'm here to thank you for all the work, bu especially for this fix:

- deinterlacing section is moved before crop to avoid green line problem

I wrote on this forums many months ago for this problem and I thought my post was lost :))))

Many thanks again, wow !
Dester.

[killingspree]

Originally posted by digidragon

Is it normally a good idea to stick to mod16 in xvid too?

yes, definitely... some people even suggest mod 32 resolutions...

kr
steVe

[len0x]

Mod32 was needed for proper playback on old graphics cards. I don't think its a problem nowadays (for instance AutoGK uses mod16 for ages and nobody complained).

[hpn]

Well, any forced modXX is evil, unless you don't mind either cropping your valued video content or producing encodes with some aspect error. But since codecs, supporting mod16, are much easier to program (it plagues even new encoders like x264, which other than that is a very promising encoder), we have to comply with it in the next decade or so. Just like when ages ago some guys decided that interlaced footage was much easier to produce. Hopefully when HD resolutons such as 2,880x1,440 become omnipresent in about 10 years, any ModXX issues will be solved, cause simply no one will record anything less than 1,280x720. But it's definately not the case now when you try to recode some weird 200x300 clip.

p.s. Len0x, GK is great, keep up the good work.

[Esc]

Looks like I have found a bug.
I have path for vStrip intentionally left blank. Now I want to set it. I press Locate button right to it, select vStrip_gui.exe and nothing happens at all. Other buttons seem to work fine.