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

[OMINUS]

yep it works thank you very much
one last question
because it seems that gk cant give correct compr test results with avi files should i use this part from the doom9 capture guide? -<http://www.doom9.org/capture/postprocessing_gknot.html-

its a little hard work to do it every time but if its the only way to get correct comp test from gk well no problemo ;)

[killingspree]

the proceture actually looks way more complicated than it really is. after doing it a couple of times you'll know it by heart and it will probably not take you more than a minute or two to do the extra steps... in addition you will notice that, after some time, you will actually get a feeling for how compressible a source is. i for example don't do a comp check in about 60% of the cases. ;)

kr
steVe

[len0x]

Originally posted by OMINUS
because it seems that gk cant give correct compr test results with avi files

why is that?

[OMINUS]

Originally posted by len0x
why is that?

well i used a 2hour captured avi file and the comp test showed me that with 70mb xvid output the quality i can get is at least maximum! ;)
i dont know what causes it - maybe its the xvid codec or the asv2 captured file - i will try and make some more tests with other avi although i am a little pessimistic with the final results :I

[Tima]

When saving script through 'advanced AVS Save window', loading of decomb.dll never gets commented.
I haven't tried to check this in simple save window..

[len0x]

I can't reproduce that - script tab always behaves properly for me...

[Tima]

The bug disappeared after I selected 'none' in 'field operations'. This was my first selection on a fresh install of GK, so the problem may lay there..

There is another strange thing: when I click EXACTLY on radiobuttons in 'field operations', everything os OK. But when I click on LABELS near them, the type of operation changes (and the script too), but buttons don't change their states..

Also a note about first bug: in that case loading of decomb.dll was not commented, but NO strings in the script actually used it.

P.s.: also there are always TWO strins: '# DENOISING: choose one combination (or none)' in the script.

[len0x]

Everything's fixed apart from denoising business that seems to be a feature (header is always printed out twice because there are two places where denoising can go).

[MetalMusicAddict]

Ive been gettin a weird bug in the past couple of betas of GK. Basically everything goes fine for a while into Vdub encoding. But I noticed somtimes the file its making, Whatever_Movie stays at 16 megs. Doesnt get bigger. Then, a little while later my PC will reset for no reason I can see. Cant figure it out. I like the new fearures ant dont wanna go back to the old "stable". Any ideas?

[len0x]

Originally posted by MetalMusicAddict
But I noticed sometimes the file its making, Whatever_Movie stays at 16 megs. Doesnt get bigger.

VDubMod writes output in 16Mb chunks. During first pass there is no output, so it will stay like this until second pass reaches the point when more than 16Mb is needed (ir will increase to 32Mb).

Originally posted by MetalMusicAddict
Then, a little while later my PC will reset for no reason I can see.

Nothing to do with GK (in the end it doesn't encode itself). Usual hardware reasons - overheating, overclocking, memory problems.

[MetalMusicAddict]

Originally posted by len0x
VDubMod writes output in 16Mb chunks. During first pass there is no output, so it will stay like this until second pass reaches the point when more than 16Mb is needed (ir will increase to 32Mb).

I was actually thinkin somthing like this.

Nothing to do with GK (in the end it doesn't encode itself). Usual hardware reasons - overheating, overclocking, memory problems.
As far as I can see with heat Im cool. :) Ill look further into this though. Thank you for the awesome app and support.

[OMINUS]

len0x i am sorry for your time but i would like your opinion about the process i use to encode avis with gknot

i create an avs (capture.avs) with the code:
SegmentedAviSource("capture.avi")
Trim(*.*)
ConverttoYV12()
KillAudio()

i open the avs with gk-i make the usual stuff,cropping,resizing etc etc,i set the bitrate,(always at 2000kbs-the comp test never work well with my avis dont know why yet)i set the xvid settings and i save the job

then i edit the saved avs from gknot and i change the line
avisource("capture.avs")
into the code:
SegmentedAviSource("capture.avi")
Trim(*.*)
ConverttoYV12()
KillAudio()

i save and then start the encoding from gknot
when the xvid is ready i rip the wav from the original captured avi
i encode it into mp3 and merge it with the xvid using for the whole process virtualdubmod

with this method i get excellent xvid from my captured avis
i just wanted to know if there is any other easier way than the one i use

anyway thats all thanx again

[len0x]

I'm not doing much capture encodings. Why don't you feed WAV file directly to GK as a part of a job?

[len0x]

Closed as GK 0.35 stable is released.