Auto Gordian Knot: current version 2.55

[len0x]

Originally posted by hujer
maybe you try to access variable that you have just destroyed, but no clue how that can happen in fast ht cpus only with only one thread :)

there is no variables to destroy - I only have boolean and short string vars there.

P.S. PM me for contact details - I'm on all messenger networks

[len0x]

Thanks to hujer we nailed down the problem: it was CPU info function from one of 3rd party libraries (JCL). Problem was fixed easly afterwards.

[len0x]

hopefully its 1.20 RC :)

[jeremymacmull]

Congrats!!

JEREMY

[nightrhyme]

Originally posted by len0x
Thanks to hujer we nailed down the problem: it was CPU info function from one of 3rd party libraries (JCL). Problem was fixed easly afterwards.

Sounds good :)
Will be testing it out ;)

[rmagere]

I will be testing if that also solves the affinity problem with dual cpu.

[Taurus]

Great work on a great project!
What will we do, when AutoGk is stable and there is nothing left to be implanted?
Retire and settle down?
I dont hope so.

Cheers

Taurus

[jeremymacmull]

There is always more stuff to do,

new codecs and other containers ie ogg etc

ofcourse there is always GKNOT regular which could have a lot more things

so i doubt lenox will be retiring anytime soon

from me i think its swell all the effort he has put in and he must be proud of his baby (AUTOGK) to have come so far

JEREMY

[CvH]

could it happend , since AGK Update from 1.18 to 1.19 AGK donst work anymore ? :(

I can start it and choose the source and so on ..
then i klick on start but nothings happens ... -> after 1 minute agk crashs

I have updatet it like every version before ... i cant explanin me the error :P

tryed to reinstall it (at first uninstall , then reinstall)

v1 works , v1.10 works , v1.19 dosent work ... :(

[rmagere]

The dual cpu affinity problem is still there, i.e. virtualdubmod launched by AutoGK sets its affinity to 1 cpu only, virtualdubmod launched by GK sets its affinity to both cpus.

[btothec2]

Vdubmod starts with affinity set to both processors on my machine. This is a real dual cpu machine not a HT machine, which is I believe your setup correct?

B

[nightrhyme]

AutoGK 1.19 seems to work ok on my HT Cpu now. All though it does not seem to utilize both cpu's. Still it does not crash anymore. Thanx so much :)

BTW. Where do you guys see the affinity setting in VdubMod ?

http://hjem.tele2adsl.dk/nightrhyme/AutoGK_2.jpg

[Stebs]

Originally posted by CvH
could it happend , since AGK Update from 1.18 to 1.19 AGK donst work anymore ? :(


From the AutoGK Website:

*EDIT* silent update was done to 1.19 since queue wasn't working at all in the first 1.19 I put online. sorry about that

So try downloading 1.19 again and see if it works now...

[therealjoeblow]

I've used every version of AutoGK over the past many months, with nary a problem. On Saturday and Sunday I encoded this same movie 4 different times in v-1.18 with various settings (credits, no credits, forced ivtc, auto-everything), and *no problem at all*, every one of them ran smoothly. Yesterday I had to reapply Win2kSP4 and reinstall DirectX9. Today I decided to try encoding the same movie again, and now, no matter what settings I use, I get a Range Check Error and crash *everytime* after the analysis, and immediately as the comptest starts. Every Time! I tried uninstalling AutoGK, reinstalling the v-1.0 stable, (and NOT the aplha xvid), and then the v-1.18 update (of course ensuring that the entire AutoGK directory got deleted after the uninstall). That didn't make any difference, I still get the crash every time. Anyone have any insight? Log file follows...

[4/27/2004 10:32:21 PM] Input dir: L:\GORMENGHAST\Episode1\VIDEO_TS
[4/27/2004 10:32:21 PM] Output file: C:\__\gg1.avi
[4/27/2004 10:32:21 PM] Audio: English
[4/27/2004 10:32:21 PM] Subtitles: none
[4/27/2004 10:32:21 PM] Codec: XviD
[4/27/2004 10:32:21 PM] Target size: 700Mb
[4/27/2004 10:32:21 PM] Custom audio settings: AC3
[4/27/2004 10:32:21 PM] Started encoding.
[4/27/2004 10:32:21 PM] Demuxing and indexing.
[4/27/2004 10:35:26 PM] Analyzing source.
[4/27/2004 10:35:26 PM] Writing the following script to C:\__\gk_tmp\lastjob.vcf
===========================================================
VirtualDub.Open("C:\\__\\gk_tmp\\_.avs",0,0);
VirtualDub.RemoveInputStreams();
VirtualDub.video.SetDepth(24,24);
VirtualDub.video.SetMode(0);
VirtualDub.video.SetFrameRate(0,1);
VirtualDub.video.SetIVTC(0,0,-1,0);
VirtualDub.video.SetCompression();
VirtualDub.video.filters.Clear();
VirtualDub.subset.Delete();
VirtualDub.SaveAVI("C:\\__\\gk_tmp\\_.avi");
===========================================================
[4/27/2004 10:39:00 PM] Source has percentage of interlacing in motion areas: 57.32
[4/27/2004 10:39:00 PM] Source has percentage of telecined patterns: 25.84
[4/27/2004 10:39:00 PM] Source has percentage of progressive patterns: 6.90
[4/27/2004 10:39:00 PM] Source has percentage of interlaced patterns: 67.26
[4/27/2004 10:39:00 PM] Source is considered to be hybrid (mostly NTSC).
[4/27/2004 10:39:00 PM] Writing the following script to C:\__\gk_tmp\lastjob.vcf
===========================================================
VirtualDub.Open("C:\\__\\gk_tmp\\_test.avs",0,0);
VirtualDub.RemoveInputStreams();
VirtualDub.video.SetDepth(24,24);
VirtualDub.video.SetMode(0);
VirtualDub.video.SetFrameRate(0,1);
VirtualDub.video.SetIVTC(0,0,-1,0);
VirtualDub.video.SetCompression();
VirtualDub.video.filters.Clear();
VirtualDub.subset.Delete();
VirtualDub.SaveAVI("C:\\__\\gk_tmp\\_test.avi");
===========================================================
[4/27/2004 10:39:00 PM] Looking for optimal hybrid thresholds.
[4/27/2004 10:39:34 PM] Found threshold of: 1.43
[4/27/2004 10:39:34 PM] Found 108388 frames
[4/27/2004 10:39:34 PM] Credits start frame: 106414
[4/27/2004 10:39:34 PM] Credits quality percentage: 25
[4/27/2004 10:39:34 PM] Credits greyscale option activated.
[4/27/2004 10:39:34 PM] Audio size: 86,797,824 bytes (82.78 Mb)
[4/27/2004 10:39:34 PM] Overhead: 602,752 bytes (0.57 Mb)
[4/27/2004 10:39:34 PM] Video size: 646,602,624 bytes (616.65 Mb)
[4/27/2004 10:39:34 PM] Running compressibility test.
[4/27/2004 10:39:34 PM] Writing the following script to C:\__\gk_tmp\gg1_comptest.avs
===========================================================
LoadPlugin("D:\PROGRA~1\AutoGK\filters\mpeg2dec3dg.dll")
LoadPlugin("D:\PROGRA~1\AutoGK\filters\autocrop.dll")
LoadPlugin("D:\PROGRA~1\AutoGK\filters\decomb.dll")
LoadPlugin("D:\PROGRA~1\AutoGK\filters\undot.dll")

function getOrder(clip c) {
order = GetParity(c) ? 1 : 0
return order }

movie = mpeg2source("C:\__\gk_tmp\gg1.d2v")
cropclip = autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=10,aspect=0,threshold=35)
c_width = width(cropclip)
c_height = round(height(cropclip) / 0.911392405063291)
input_par = float(c_width)/float(c_height)
fixed_aspect = input_par > 1.4 ? 0.911392405063291 : 0.888888888888889
c_height = round(height(cropclip) / fixed_aspect)
input_par = float(c_width)/float(c_height)
out_width = 640
out_height = round(float(out_width) / input_par)
hmod = out_height - (floor(out_height / 16 ) * 16)
out_height = (hmod > 4) ? (out_height + (16 - hmod)) : (out_height - hmod)
new_aspect = (float(out_width) / float(out_height)) / fixed_aspect
Telecide(movie,order=getOrder(movie),guide=1,post=2).Decimate(mode=1,threshold=1.43)
autocrop(mode=0,wmultof=4,hmultof=4,samples=10,aspect=new_aspect,threshold=35)
Undot()
LanczosResize(out_width,out_height)
SelectRangeEvery(300,15)
===========================================================
*************************************
EXCEPTION: Range check error
*************************************
[4/27/2004 10:39:35 PM] Job finished.

[therealjoeblow]

I tried a completely different movie, to completely different drives (same machine), and had the same crash. So in a fit of rage, I did the following, in this order:

1) uninstalled divx 5.1.1 (from add/remove programs)
2) uninstalled xvid 1.0rc4 (from add/remove programs)
3) uninstalled avisynth 2.5.4 (from add/remove programs)
4) uninstalled autogk 1.18 from it's shortcut

then:

1) reinstalled divx 5.1.1
2) reinstalled xvid 1.0rc4
3) reinstalled AutoGK 1.0 full, everything minus xvid alpha
4) reinstalled AutoGK 1.12 update only
5) reinstalled AutoGK 1.16 update only
6) reinstalled AutoGK 1.18 update only

Now it all appears to work (at least it's running the comptest right now - I'll have to report back later if it finishes completely, but it was failing before the comptest everytime earlier).

If it did get fixed, I have no idea exactly which step above it was that was the cure, but if anyone runs into a simlar problem, give this a shot.

[hujer]

Originally posted by rmagere
The dual cpu affinity problem is still there, i.e. virtualdubmod launched by AutoGK sets its affinity to 1 cpu only, virtualdubmod launched by GK sets its affinity to both cpus.

did you remove win98 compatibility setting ?

i did test encode now and it uses both cpus

[pindawg]

Has anyone else had a problem with credit mode starting early in the latest release? I just encoded 3 movies, and in all 3 the credit mode started early. I verified the frame number with vdubmod, and the frmae number in the credit file to be correct. ie one movie credits start @ frame 156299, and it appears AGK started credit mode at ~ frame 125088.

Any Ideas??

[len0x]

Originally posted by pindawg
Has anyone else had a problem with credit mode starting early in the latest release? I just encoded 3 movies, and in all 3 the credit mode started early. I verified the frame number with vdubmod, and the frmae number in the credit file to be correct. ie one movie credits start @ frame 156299, and it appears AGK started credit mode at ~ frame 125088.
Any Ideas??

yes its IVTC applied, you should always supply non-FF (or IVTC-ed) frame number for credits start.

[pindawg]

Originally posted by len0x
yes its IVTC applied, you should always supply non-FF (or IVTC-ed) frame number for credits start.

Got it.. Thanks len0x!

[rmagere]

Originally posted by hujer
did you remove win98 compatibility setting ?

i did test encode now and it uses both cpus

Yeah I never used win98 compatibility as I have never bothered enabling HT, however it still see that problem. I'll try reinstalling everything and have a look.

[therealjoeblow]

Originally posted by len0x
yes its IVTC applied, you should always supply non-FF (or IVTC-ed) frame number for credits start.

...Or use the frame calculator feature in the 'Hidden Options' tool, just enter the credit start timestamp, and choose NTSC or PAL, and you're done :)

BTW, the uninstall/reinstall process noted earlier for the 'Range Check Error' worked. Don't know exactly what was pooched, but something sure was.

[RathO]

The hidden options are very hidden since i press ctrl-F9 and nothing appears... why?

Regards

[Stebs]

Originally posted by RathO
The hidden options are very hidden since i press ctrl-F9 and nothing appears... why?

Regards

:rolleyes: Because it's Ctrl-F10 ;)

Ctrl-F9 is for a plugin you have to download and place in the AutoGK-Folder.

[RathO]

Ah, the tool is downloadable... should be included in AutoGK by default. Thanks for the fast reply!

Regards

[QNX]

damn.. it works.. don't have troubs anymore with my HT cpu :)

10x! :D

[Toge]

will 1.20 be a stable?

[usrbinmadness]

Hello. I enjoy AutoGK for Windows and it works great.

However, I would like to install AutoGK in Linux using WINE, but the installer doesn't appear properly on the screen so I cannot continue with the installation under WINE on Linux, I have to kill the process. I've tried it several times and it continues with this problem*. I have installed Gordian Knot codec pack fine because it uses a different installer. What I'm wondering is if it's possible to release AutoGK with the same installer as Gordian Knot uses? This way I (and many others) would be able to use AutoGK in Linux under WINE. Thanks for reading.

*=I hope this post isn't considered off-topic. I enjoy AutoGK very much but would like to use it in Linux making it available with a different installer (such as the one Winamp has used) would solve the problem I am having.

[cork]

Originally posted by usrbinmadness I enjoy AutoGK very much but would like to use it in Linux making it available with a different installer (such as the one Winamp has used) would solve the problem I am having. [/B]
Errr... AutoGK precisely uses NSIS 2.0 which is also used by winamp and GK's System Pack.
What version of winamp works ? Please try Winamp 5 to see if it is a specific 2.0 problem.

[Carraway]

len0x,

Is there any chance that the maximum fixed width could be increased to 800 as it is in GKnot? I have several 2.35:1 movies that would easily fit on 2 CD's at that resolution but 720 is the maximum autogk will go. This is a relatively minor issue but I figured I'd float the idea for peace of mind. Let me know what you think.

[buk]

Hi, today trying to connect to autogk web page I have following message: "Fatal error: Call to undefined function: message_die() in /home/len0x/public_html/web/db/db.php on line 88". I must point out, that a few weeks i have terrible problems with downloading files from this site. A few days after each new version (beta) is the server out of order for me. I must download autogk from some Polish site or other site. I´m using Win XP Pro, IE6, broadband connection with personal firewall (blocked refferers, ads.... and so on). What is the problem?



Thanx,

buk

[buk]

Hi, today trying to connect to autogk web page I have following message: "Fatal error: Call to undefined function: message_die() in /home/len0x/public_html/web/db/db.php on line 88". I must point out, that a few weeks i have terrible problems with downloading files from this site. A few days after each new version (beta) is the server out of order for me. I must download autogk from some Polish site or other site. I´m using Win XP Pro, IE6, broadband connection with personal firewall (blocked refferers, ads.... and so on). What is the problem?



Thanx,

buk

[len0x]

gr... just as I woke up I found out that my hosting server it totally down. when they get it up again my web site should be working as usual..

[Taurus]

Congratulation!

Anybody noticed it, that we arrived at page 100 (in standard page view)?
Never thought that we will go this far.
Thank you lenOx and all supporters for your incredible work.:) :) :) :D

Cheers

Taurus

[((( atom )))]

i have an issue wich i would say is caused by badly masterd dvds - incorrect aspects - and could be easily taken care of in autogk.

i have a 16:9 tv with vga in, so that means very very little overscanning since it actually functions like a pc monitor, and i have adjusted the image to slightly exceed the screen.

i just encoded the second movie wich is ot exactly 16:9 but a little less wide (672x416 in my recent encode). it looks plain stupid on my display, having little bars to the left and right side. on a 16:9 tv though, the rather large overscan would fix the issue, so it would fill the screen again.

using gknot i (and may others i assume) always make sure the output will be strict 4:3, 16:9 and so on. gknot pretty much helps enforcing this by using the multiple of 16/32 switches.

anyway, i think it might make sense to make autogk just crop a few pixels more in order to achieve correct results again.

i might as well oversee some point here, so please comment.


regards,

[len0x]

I've just received an email from my hosting service - they're moving servers around so website is still unaccessable (hopefully tomorrow it should be up and running again).

Here (http://64.246.25.140/~len0x/AutoGordianKnot.1.19.beta.Update.exe) is direct link for those still wishing to get 1.19 version.

[manono]

Hi atom-

I don't understand. I don't know what the original AR of the movie is, but it's easy to see how a 1.66:1 movie could become 1.62:1 (672x416) with cropping from the left and right sides to get low Aspect Error. Are you saying that you want it to fill your screen without black bars, even if that means giving it bad AR? And what do you do for 2.35:1 movies? Do you like to stretch them vertically just so they fill the screen (sorry-couldn't resist)?

When I play 1.66:1 movies on my widescreen TV, I also see small black bars on the left and right sides. It doesn't bother me at all. When I watch 1.77:1 or 1.85:1 movies on the widescreen, the overscan hides the black bars (on the 1.85:1 movies), and the movie fills the screen. But those are the only ones where I get true full screen (and in my opinion, the only ones that should fill the screen). If your movie was originally 1.77:1 or 1.85:1, then I'd say you have a case. What's the movie, and what is the movie's AR? And you're not confusing DAR (4:3 or 16:9) with the movie AR (1.66:1, 1.77:1, 1.85:1, 2.35:1, etc.) are you?

[((( atom )))]

hi manono,

no, i don't want to stretct any movie to make it loose its ar, i'd rather cut a little from top and bottom to make it fill my screen and look nice. as written, on regular tv sets all four sides are "cut", due to overscanning and the picture fills the screen again, i just don't have that.

who is using 1.66:1? where would that format come from? is there any film format like that?
so far it looked like an error in the mastering process to me..

and, no... i don't want to stretch 2.35:1 movies to fill my screen ;)

[manono]

Hi atom-

on regular tv sets all four sides are "cut", due to overscanning and the picture fills the screen again, i just don't have that.

If it's a 1.66:1 movie, on a regular TV, even taking the overscan into account, there will be small black bars on top and bottom. A regular TV set is 1.33:1.

who is using 1.66:1? where would that format come from? is there any film format like that?

Sure, IMDB lists over 500 movies in 1.66:1 ratio:

http://www.imdb.com/Sections/DVDs/AspectRatios/1.66_:_1/

This page has some discussion of 1.66:1 movies:

http://www.hkfanatic.com/widescreen/widescreen/widescreen.php

And here's a nice thread about the issue, including some history of the development of the 1.66:1 ratio, with some real experts chiming in:

http://www.hometheaterforum.com/htforum/showthread.php?threadid=147312

I can almost understand you wanting to crop a little from the top and bottom so that the movie fills the screen of your TV set. But I also think it's too much to ask AutoGK to do for you. If your movie really is 1.66:1, then the autocrop isn't doing anything wrong. I think you either have to zoom the picture a little more to cut from the top and bottom (by using Zoom Player, for example, that's easy to do), or crop it the way you want by using GKnot.

[((( atom )))]

hi manono,

thx for the links, very interresting.
here a more visual impression of what i see: http://www.othyrworld.com/16x9/

so since it turned out to be a format of its own, it would be technically wrong to have any application automatically "correct" it, you are right.

still it looks rediculous on either screen, so i wonder why the studios not fit it before releasing..

[therealjoeblow]

Originally posted by ((( atom )))
hi manono,

no, i don't want to stretct any movie to make it loose its ar, i'd rather cut a little from top and bottom to make it fill my screen and look nice. as written, on regular tv sets all four sides are "cut", due to overscanning and the picture fills the screen again, i just don't have that.

who is using 1.66:1? where would that format come from? is there any film format like that?
so far it looked like an error in the mastering process to me..

and, no... i don't want to stretch 2.35:1 movies to fill my screen ;)

atom - you didn't mention the player you're using - have you tried zoomplayer? I use it with the default zoom set to about 105%, which effectively does the same as what you want in terms of additional crop, it clears up all of the remnant side edges. Actually with a remote (ATI Remote Wonder, and the Rylos plugin), the 1-10 keys on the remote are mapped to the 10 zoom presets, and I've got mine going up in about 5~10% increments, so I can zoom in and out at will, with virtually no effort.

I usually watch true 16:9's at the 100 or 105% setting (depending if any cropping is needed), and most 2.35:1's zoomed at somewhere around 150%, so they look similar to 16:9's - 2.35:1 is just too wide and short for a 32" TV. Note, there is no stretching going on, it just zooms in and fills the display, with whatever doesn't fit going off into digital oblivion somewhere.

[Black0ut]

I just encoded an Futurama Episode with AutoGK 1.19 and while Encoding VDubMod showed "Autoloaded 1 Filters". Which filter could it autoload?

PS: I also used XviD Cartoon Mode

edit: I found a problem, AutoGK thinks it is interlaced, but I looked it through it isn't!

[baeckerg]

Hi len0x,

When I read about the latest fixes in AutoGK I was wondering if you could shed some light on how the problem on hyperthreading was solved.

The reason for the question is that I am working with Delphi 7 and ran into a problem on Hyperthreading machines myself with a Runtime 216 and a stable application after turning off the hyperthreading or switching to Win98 compatibility mode.

Kind regards and thanks for a great program
Gernot

[GizmoDerMokwai]

Originally posted by Black0ut
I just encoded an Futurama Episode with AutoGK 1.19 and while Encoding VDubMod showed "Autoloaded 1 Filters". Which filter could it autoload?

PS: I also used XviD Cartoon Mode

edit: I found a problem, AutoGK thinks it is interlaced, but I looked it through it isn't!

"Autoloaded 1 Filters" <- it's mostly the VobSub Filter which gets outo loaded by default when using vdub...

And cause you're from germany i thing you'r encoding pal german rc2 version of futurama, as i did, which for sure is interlaced as nearly all tv series in pal!

[((( atom )))]

Originally posted by therealjoeblow
atom - you didn't mention the player you're using - have you tried zoomplayer? i watch my movies off a linux box running mplayer and lirc for remote controll. it holds all my movies on a laaaarge disk. it's great!

[homerjay]

just got hold of this ant tested for a friend to see if it really is idiot proof

hes got one of those divx dvd players so converting to avi is perfect for him

what a fantastically smooth program - thankyou very much for your work :D

now a question :sly: it may have been asked before but its such a big thread are there text versions of the scripts used anywhere and could they be converted for use with dvd2svcd as the 1cd xvid with 128mb mp3 audio was as good as i have ever managed doing 1cd svcd's

[len0x]

Originally posted by baeckerg
When I read about the latest fixes in AutoGK I was wondering if you could shed some light on how the problem on hyperthreading was solved.


JCL function getCPUInfo was at fault in my case (from JEDI library), although I didn't use it directly myself. (and its not 216 error, but division by zero)

[len0x]

Originally posted by Carraway
len0x,

Is there any chance that the maximum fixed width could be increased to 800 as it is in GKnot? I have several 2.35:1 movies that would easily fit on 2 CD's at that resolution but 720 is the maximum autogk will go. This is a relatively minor issue but I figured I'd float the idea for peace of mind. Let me know what you think.

why not, but only for fixed width mode :)

[len0x]

Originally posted by Toge
will 1.20 be a stable?

looks like it won't. new DVD2AVI is on the way - I'll need some testing of that...

[baeckerg]

Originally posted by len0x
JCL function getCPUInfo was at fault in my case (from JEDI library), although I didn't use it directly myself. (and its not 216 error, but division by zero)

Thanks for the info. I got some problem with this part from JCL as well.

Gernot

[Carraway]

You may already be aware of this, but it seems that the new version may have a problem properly ivtc'ing FILM material. I've only tested a couple of sources but both have had the same problem, so I figured it was worth posting.

http://home.columbus.rr.com/carraway6/combing01.jpg

http://home.columbus.rr.com/carraway6/combing02.jpg

I encoded this clip with both 1.20 and 1.19. 1.19 encoded it correctly, obviously, so I compared the D2V files produced by both, and the only difference was the following:

DVD2AVIProjectFile02
1
49 D:\DVD\FIFTH_ELEMENT\CLIP01\VIDEO_TS\VTS_01_1.vob

Stream_Type=1,0,0
iDCT_Algorithm=2 (1:MMX 2:SSEMMX 3:FPU 4:REF 5:SSE2MMX)
YUVRGB_Scale=1 (0:TVScale 1:PCScale)
Luminance_Filter=0,0 (Gamma, Offset)
Picture_Size=0,0,0,0,0,0 (ClipLeft, ClipRight, ClipTop, ClipBottom)
Aspect_Ratio=4:3
Field_Operation=2 (0:None 1:ForcedFILM 2:SwapOrder 3:RawFrames)
Frame_Rate=23976
Location=0,0,0,61BE

In v 1.19, Field_Operation was set to 1. And when I change the v1.20 d2v file setting from 2 back to 1, it fixes the combing problems. I'm not terribly familiar with what SwapOrder does, so I have no idea if this setting is intentional in 1.20, but I thought I might as well post it anyway. Just in case.