View Full Version : Auto Gordian Knot: current version 2.55
len0x
19th June 2004, 10:44
Originally posted by pindawg
Any word on the timeout problem.
I can ask you the same question. I asked ppl for exact timing for manual indexing and demuxing (audio demuxing is important in this case) and noone seemed to care...
len0x
19th June 2004, 10:48
Originally posted by btothec2
I actually have an old version on my htpc. I have not tried the newest version on there. I will install the latest and see how it goes.
How old ?
Every version from 0.8-1.25 had almost the same GUI in that respect. So you didn't have any problems? (if you have 640 width of screen then you should since AutoGK's width is 700)
Firewave
19th June 2004, 15:16
Originally posted by len0x
I can ask you the same question. I asked ppl for exact timing for manual indexing and demuxing (audio demuxing is important in this case) and noone seemed to care...
I replied to that on the 18th June. Read it above and answer, please.
len0x
19th June 2004, 16:01
Originally posted by Firewave
I replied to that on the 18th June. Read it above and answer, please.
How hard is to tell me just how much _exactly_ took demuxing of the source which timed out in AutoGK ? If you stop paying attention to what I'm asking I'll stop fixing the issue.
p.s. at least you attempted to answer, ppl like pindawg still whining...
Firewave
19th June 2004, 17:46
Originally posted by len0x
How hard is to tell me just how much _exactly_ took demuxing of the source which timed out in AutoGK ? If you stop paying attention to what I'm asking I'll stop fixing the issue.
p.s. at least you attempted to answer, ppl like pindawg still whining...
First you have to answer my question, what I have to do, because I see no option "demuxing audio" anywhere in that tool.
Do I have to choose "Save project"? And what settings do I need, that the behavior is the same as AutoGK?
And I couldn't tell you the exact time it took, because I never got around to run it in the past few days. Being a bit busy with real life and work.
If I get around to it I will look more deeply into it tomorrow, because right now I just got home and I am already on the run again.
Update: Well...I saw the "Demux" option now. Last time I looked into it I was too focused on "Demux All". I set it to demux and the estimated time was around 5 minutes. I will take another look at it in an hour, if it get to it.
Update 2: Starting it manually it took a few seconds more than 5 minutes. And running AutoGK again with a movie I had aproblem with...no timeout anymore.
Do you distribute DGIndex.exe with an default DGIndex.ini? I read the commandline documentation and it says, that non-supplied parameters are read from the ini file. Maybe starting it manually creates a default ini file and it takes some settings like floating point type from there. I can't check it right now. I am on the run. Sorry
len0x
19th June 2004, 18:53
The whole reason for putting 30 min timeout for DGIndex operation was to avoid problem with the queue when DGIndex in fact doesn't do anything (for unknown reason). So whatever you guys experiencing is exactly what it was intended for (as you see now yourself demuxing step doesn't take more than 15-20 min). Case closed.
P.S. DGIndex is suppied with all parameetrs dynamically and ini file is not used. and FYI floating point type is for _decoding_ via dgdecode.dll not demuxing with DGIndex...
calinb
20th June 2004, 05:05
Originally posted by len0x
Some HTPC ppl would like to see main screen of the AutoGK not more than 640x480. Fits just fine in the 720p output to my Sammy from my HTPC:D I like it the way it is now.
MRisos
20th June 2004, 07:05
I seem to be having a filesize problem this is the log.
I done MPEG2 2 XVID 350mb
Heres the log.
removed
The final completed 2pass xvid came out 172MB:rolleyes:
manono
20th June 2004, 09:16
Welcome to the forum, MRisos-
Could this be your problem? It's Q 6.3 from the AutoGK FAQ (http://forum.doom9.org/showthread.php?s=&threadid=72679):
6.3 I used to use old XviD and now I switched to XviD 1.0. Since then I _always_ have _very_ undersized/oversized files. What's the problem?
- old XviD has to be uninstalled properly, i.e. just installing new 1.0 over it is not a proper way. Try uninstalling old one, then reinstalling new one.
MRisos
20th June 2004, 10:38
Originally posted by manono
Welcome to the forum, MRisos-
Could this be your problem? It's Q 6.3 from the AutoGK FAQ (http://forum.doom9.org/showthread.php?s=&threadid=72679):
Hi, thank you :) It fixed my problem. Sorry i hadnt read the faq before posting.:(
((( atom )))
21st June 2004, 16:14
ok, now it is time for me to check out file input mode. i came across a film wich is split onto two dvds and i'd like to convert it in one session as one file.
so what would be the smartest way to do that?
i am worried about the audio-part mostly, i see synch issues troubling me already..
could someone pls give me a short explanation of how the audio is detected, as an external file? from within the vob? ...?
len0x
21st June 2004, 18:24
Originally posted by calinb
Fits just fine in the 720p output to my Sammy from my HTPC:D I like it the way it is now.
Tell me something. If you were to have a low resolution HTPC then (when you can't see the whole window) - would having shorcuts help or not?
len0x
21st June 2004, 18:25
Originally posted by ((( atom )))
could someone pls give me a short explanation of how the audio is detected, as an external file? from within the vob? ...?
Audio is always demuxed by DGIndex. If you want to queue up several files for one job - just name them with _1, _2 in the end and they will be picked up (in file mode only first audio will be demuxed). Audio synch may be an issue, but may be its gonna be ok. That depends on the source...
btothec2
21st June 2004, 19:55
Originally posted by len0x
Tell me something. If you were to have a low resolution HTPC then (when you can't see the whole window) - would having shorcuts help or not?
len0x
As a matter of fact, now that I think of it, it was very hard to use it, as parts were off screen. What I ended up doing, is logging in through remote admin.
B
ydobon
21st June 2004, 20:37
Hello there.
Originally posted by len0x
Tell me something. If you were to have a low resolution HTPC then (when you can't see the whole window) - would having shorcuts help or not?
Actually I was thinking in asking something similar, but not for the same reason.
I seem to remember you've said you don't plan to add command-line switches to AutoGK. In an effort to batch encode I've used macro tools (such as Macro Scheduler) to emulate keyboard and mouse events. It's usually easier to use just keys, so keyboard shortcuts would be most welcomed.
Also if the input field was editable, that would be great.
Even if all the buttons were into the tab/shift+tab cycle it would be good enough.
Regards,
calinb
21st June 2004, 21:16
Originally posted by len0x
Tell me something. If you were to have a low resolution HTPC then (when you can't see the whole window) - would having shorcuts help or not? IMHO, I think shortcuts are fine as an alternative for low res screens. The remote desktop features of Windows (either remote desktop connection on XP or through Netmeeting, which is available all the way back to ME, at the least) is also worth a look for users trying to control low-res HTPCs remotely.
Outerspacelord
22nd June 2004, 15:58
From AutoGK v1.30 beta I suppose I should read "- resizing algorithm changed heavily to accomodate upcoming support for different input sources (ITU standard is no longer applied)" as it goes for all sources (input directory too)? ITU standard is no longer applied at all?
And am I reading it right if I translate the info in Gordian Knot: "But actually this will result in an aspect ratio that is ~2.5% off!", that ticking the 'ITU standard' makes an aspect ratio that is ~2.5% off?
And to <manono> I have to say sorry for my english and my use of , and . and ... :cool:
thx
Edit: had to edit cause of some strange ,,,... and difficult english hehe
len0x
22nd June 2004, 16:08
Originally posted by Outerspacelord
ITU standard is no longer applied at all?
yes
Originally posted by Outerspacelord
And am I reading it right if I translate the info in Gordian Knot: "But actually this will result in an aspect ratio that is ~2.5% off!", that ticking the 'ITU standard' makes an aspect ratio that is ~2.5% off?
Yes, but all recent test by many ppl showed that they would be happier with no ITU resizing.
P.S. No-ITU resizing method for 4:3 sources was used in AutoGK almost from the beginning.
Outerspacelord
22nd June 2004, 18:14
Originally posted by len0x
Yes, but all recent test by many ppl showed that they would be happier with no ITU resizing.
Me too, I'm happy ... and thx for quick answere as usual.
I don't know if it's because english is not my native language, but could I propose that the info in GK change a bit since my eyes crossed reading that sentence over and over again. It first states that "It's recommended to leave this checked." and then reads "But actually this will result in an aspect ratio that is ~2.5% off! ...". Oh, those hard decisions hehe. I read the sticky "Resolutions, Aspect Ratios And The ITU-R BT.601 Standard" by <manono>, and in a way the info in GK is just the short version of how my confusion was...until now. So for new users it may be good to tell plainly what really is recommend? Tell them that if they tick the "ITU Standard" peoples faces will get flat wide ~2.5% off, which is a nice effect for a plugin :)
jebus
22nd June 2004, 20:14
@ len0x,
nice job, but just 1 Q:
Have had trouble with audio-synching, is there a way to synch it using only autoGK?
It works really great, done 'bout 5 movies the last 20 hours without any prob.
len0x
24th June 2004, 16:31
Originally posted by jebus
Have had trouble with audio-synching, is there a way to synch it using only autoGK?
Not really. What kind of issues do you have ?
len0x
24th June 2004, 16:32
Nothing major. Mostly GUI/shortcuts stuff.
len0x
nice strike 10x
now i can't run autogk
1.42b giving me an error
runtime error 216 at 0040357E
like it was with HT earlier as i remember :D
compatibility mode giving the same result
:sly:
len0x
24th June 2004, 19:41
Originally posted by QNX
like it was with HT earlier as i remember :D
hm... may be directx library screwed something up (I started building support for DV sources). I'll remove them in the next version. So stick to 1.41 in the meantime...
((( atom )))
25th June 2004, 00:50
wow - i figured the most amazing hidden option: autogk can even translate languages! ;)
i decided to try subtitels for the first time with the movie "in the mood for love (wong kar wai)".
i chose german subtitles and got the netherland ones.
very nice feature, indeed, but serios again: what went wrong?
i opened the ifo in vobsub and found 3 instances of german subtitles. the first appereance was "11 german". i checked it shortly and they were german alright, so i didn't care about the other two instances yet.
stream inforation.txt says:
0x21 - Subtitle - Franįais / LBA: 156 / PTS: 00:00:00.288 / Delay: 200ms
0x22 - Subtitle - Nederlands / LBA: 154 / PTS: 00:00:00.288 / Delay: 200ms
0x23 - Subtitle - English / LBA: 6 / PTS: 00:00:00.288 / Delay: 200ms
0x24 - Subtitle - Italiano / LBA: 4 / PTS: 00:00:00.288 / Delay: 200ms
0x25 - Subtitle - Deutsch / LBA: 14 / PTS: 00:00:00.448 / Delay: 360ms
0x26 - Subtitle - Greek / LBA: 12 / PTS: 00:00:00.448 / Delay: 360ms
0x27 - Subtitle - Deutsch / LBA: 10 / PTS: 00:00:00.368 / Delay: 280ms
0x28 - Subtitle - Espaņol / LBA: 8 / PTS: 00:00:00.368 / Delay: 280ms
0x29 - Subtitle - Espaņol / LBA: 144 / PTS: 00:00:00.288 / Delay: 200ms
0x2A - Subtitle - Espaņol / LBA: 142 / PTS: 00:00:00.288 / Delay: 200ms
0x2B - Subtitle - Espaņol / LBA: 4943 / PTS: 00:00:09.448 / Delay: 9360ms
0x2C - Subtitle - Espaņol / LBA: 4941 / PTS: 00:00:09.448 / Delay: 9360ms
0x2D - Subtitle - Espaņol / LBA: 4900 / PTS: 00:00:09.488 / Delay: 9400ms
0x2E - Subtitle - Espaņol / LBA: 4898 / PTS: 00:00:09.488 / Delay: 9400ms
0x2F - Subtitle - Espaņol / LBA: 3 / PTS: 00:00:00.368 / Delay: 280ms
0x30 - Subtitle - Espaņol / LBA: 2 / PTS: 00:00:00.368 / Delay: 280ms
0x31 - Subtitle - Espaņol / LBA: 148 / PTS: 00:00:00.288 / Delay: 200ms
0x32 - Subtitle - Espaņol / LBA: 146 / PTS: 00:00:00.288 / Delay: 200ms
0x80 - Audio - AC3 / 6ch / 48kHz / DRC / Chinese / LBA: 53 / PTS: 00:00:00.088 / Delay: 0ms
0x81 - Audio - AC3 / 6ch / 48kHz / DRC / Deutsch / LBA: 52 / PTS: 00:00:00.088 / Delay: 0ms
0x82 - Audio - AC3 / 2ch / 48kHz / DRC / Espaņol / LBA: 54 / PTS: 00:00:00.088 / Delay: 0ms
0x83 - Audio - AC3 / 2ch / 48kHz / DRC / Chinese / LBA: 51 / PTS: 00:00:00.088 / Delay: 0ms
0xE0 - Video - MPEG-2 / 720x576 (PAL) / 16:9 / Pan-Scan & Letterboxed / LBA: 1 / PTS: 00:00:00.088 / Delay: 0ms
and "deutsch - german" is not at line #11 but i really don't know how to interprete the codes given in this file.
investigated a lill further and opened the .sub file autogk generated in vobsub and the subs found were 05 - nederlands.
..just thought i'd let you know. hope my posting makes sense, i am awfully tired.
/nite
len0x
25th June 2004, 14:48
Originally posted by ((( atom )))
and "deutsch - german" is not at line #11 but i really don't know how to interprete the codes given in this file.
DVDDecrypter screwed up (IFO parsing code). This happens, nothing we can do here...
len0x
25th June 2004, 16:44
does anyone else have problem starting 1.42b (runtime error)?
((( atom )))
25th June 2004, 17:57
Originally posted by len0x
DVDDecrypter screwed up (IFO parsing code). This happens, nothing we can do here... ok, thx for letting me know..
Hesse
25th June 2004, 19:37
I seem to be getting undersized files again for some reason (using Xvid 1.0.1). Not all of my encodes are undersized though. I'm currently using AutoGK 1.42b, but its happened in 1.41b also. Everything was working previously (1.35b).
I don't think its the FAQ 6.3 because everything has been working until recently. And not all movies are undersized, just certain ones. The same thing is happening in the latest GK alpha (0.31).
Anyone else having this problem or is it just a codec problem on my system. I tried uninstalling Xvid and reinstalling it, no luck. Would any logs help out?
Thanks,
Jesse
On an unrelated note, would changing the autocrop threshold help me with a cropping problem I have. I am trying to encode eps of Angel, and I am getting a green line on the left hand side of the picture. I notice this line also when using the regular GK's autocrop (2 pixels on left). If I go with 4 pixels, the line goes away.
Carraway
25th June 2004, 19:50
Originally posted by Hesse
I seem to be getting undersized files again for some reason (using Xvid 1.0.1).
Question: when you get undersized files, are you using File Input rather than DVD Input?
len0x
25th June 2004, 20:05
Originally posted by Hesse
I seem to be getting undersized files again for some reason (using Xvid 1.0.1).
I need to see the logs...
Originally posted by Hesse
On an unrelated note, would changing the autocrop threshold help me with a cropping problem I have. I am trying to encode eps of Angel, and I am getting a green line on the left hand side of the picture. I notice this line also when using the regular GK's autocrop (2 pixels on left). If I go with 4 pixels, the line goes away.
Yes, it would. Would mind telling me which eps of Angel have this issue?
len0x
25th June 2004, 20:18
If you have runtime error on 1.42 startup - you might try this version:
http://len0x.leffe.dnsalias.com/AutoGK.zip
I removed directx reference and recompiled it with new update for Delphi.
P.S. @QNX - is any of these dlls are missing on your system:
ole32.dll
quartz.dll
msdmo.dll
Ksuser.dll
Ksproxy.ax
DSound.dll
DDraw.dll
d3d9.dll
If yes, then we might have found the problem...
Hesse
25th June 2004, 20:27
Yes, it would. Would mind telling me which eps of Angel have this issue?
The only ones I've tried so far are eps 1x01 - 1x04 (Season 1, Disc 1). There's a green line on the left edge. Also, eps 2 and 3 seem to be very problematic (or at least the most noticable). There are parts that come out looking very bad with interlacing artifacts. If I encode with deinterlacing with TomsMoComp in GK it looks better on these ones.
I need to see the logs...
I used the "DVD input". Here is the AutoGK log. Need any others? I was encoding with no audio. I set the file to come out at 1717 MB and it came out as 1581 MB (1,657,817,088 bytes)
AutoGK Log
-----------------------------------------------------------
[6/25/2004 7:26:41 AM] AutoGK 1.42b
[6/25/2004 7:26:41 AM] OS: WinXP (5.1.2600).2
[6/25/2004 7:26:41 AM] Job started.
[6/25/2004 7:26:41 AM] Input dir: H:\DVD\FORYOUREYESONLY
[6/25/2004 7:26:41 AM] Output file: H:\DVD\FORYOUREYESONLY\FORYOUREYESONLY_1.avi
[6/25/2004 7:26:41 AM] Subtitles: none
[6/25/2004 7:26:41 AM] Codec: XviD
[6/25/2004 7:26:41 AM] Target size: 1717Mb
[6/25/2004 7:26:41 AM] Started encoding.
[6/25/2004 7:26:41 AM] Demuxing and indexing.
[6/25/2004 7:28:41 AM] Source aspect ratio: 16:9
[6/25/2004 7:28:41 AM] Source resolution: 720x480
[6/25/2004 7:28:41 AM] Found NTSC source.
[6/25/2004 7:28:41 AM] Source seems to be pure FILM.
[6/25/2004 7:28:42 AM] Found 183615 frames
[6/25/2004 7:28:42 AM] Credits start frame: 225405
[6/25/2004 7:28:42 AM] Credits quality percentage: 20
[6/25/2004 7:28:42 AM] Overhead: 0 bytes (0.00 Mb)
[6/25/2004 7:28:42 AM] Video size: 1,800,404,992 bytes (1717.00 Mb)
[6/25/2004 7:28:42 AM] Running compressibility test.
[6/25/2004 7:28:42 AM] Writing the following script to H:\DVD\FORYOUREYESONLY\gk_tmp\FORYOUREYESONLY_1_comptest.avs
===========================================================
LoadPlugin("C:\PROGRA~1\AutoGK\DGMPGDec\DGDecode.dll")
LoadPlugin("C:\PROGRA~1\AutoGK\filters\autocrop.dll")
LoadPlugin("C:\PROGRA~1\AutoGK\filters\undot.dll")
movie = mpeg2source("H:\DVD\FORYOUREYESONLY\gk_tmp\FORYOUREYESONLY_1.d2v")
cropclip = autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=10,aspect=0,threshold=34)
fixed_aspect = 1.18518518518519
c_width = width(cropclip)
c_height = round(height(cropclip) / fixed_aspect)
input_par = float(c_width)/float(c_height)
input_par = input_par > 1.4 ? input_par : (4.0/3.0)
out_width = 704
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
autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=10,aspect=new_aspect,threshold=34)
Undot()
LanczosResize(out_width,out_height)
SelectRangeEvery(300,15)
===========================================================
[6/25/2004 7:28:42 AM] Writing the following script to H:\DVD\FORYOUREYESONLY\gk_tmp\lastjob.vcf
===========================================================
VirtualDub.Open("H:\\DVD\\FORYOUREYESONLY\\gk_tmp\\FORYOUREYESONLY_1_comptest.avs",0,0);
VirtualDub.video.SetMode(1);
VirtualDub.video.SetFrameRate(0,1);
VirtualDub.video.SetIVTC(0,0,-1,0);
VirtualDub.video.SetRange(0,0);
VirtualDub.video.SetCompression(0x64697678,0,10000,0);
VirtualDub.video.filters.Clear();
VirtualDub.subset.Delete();
VirtualDub.SaveAVI("H:\\DVD\\FORYOUREYESONLY\\gk_tmp\\FORYOUREYESONLY_1_comptest.avi");
===========================================================
[6/25/2004 7:36:28 AM] Duration was: 7 minutes 46 seconds
[6/25/2004 7:36:28 AM] Speed was: 19.69 fps.
[6/25/2004 7:36:28 AM] Compressibility percentage is: 105.16
[6/25/2004 7:36:28 AM] Chosen resolution is: 720x320 ( AR: 2.25 )
[6/25/2004 7:36:28 AM] Predicted comptest value is: 97.68
[6/25/2004 7:36:28 AM] Running first pass.
[6/25/2004 7:36:28 AM] Writing the following script to H:\DVD\FORYOUREYESONLY\gk_tmp\FORYOUREYESONLY_1_movie.avs
===========================================================
LoadPlugin("C:\PROGRA~1\AutoGK\DGMPGDec\DGDecode.dll")
LoadPlugin("C:\PROGRA~1\AutoGK\filters\autocrop.dll")
LoadPlugin("C:\PROGRA~1\AutoGK\filters\undot.dll")
movie = mpeg2source("H:\DVD\FORYOUREYESONLY\gk_tmp\FORYOUREYESONLY_1.d2v")
cropclip = autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=10,aspect=0,threshold=34)
fixed_aspect = 1.18518518518519
c_width = width(cropclip)
c_height = round(height(cropclip) / fixed_aspect)
input_par = float(c_width)/float(c_height)
input_par = input_par > 1.4 ? input_par : (4.0/3.0)
out_width = 720
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
autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=10,aspect=new_aspect,threshold=34)
Undot()
LanczosResize(out_width,out_height)
===========================================================
[6/25/2004 7:36:28 AM] Writing the following script to H:\DVD\FORYOUREYESONLY\gk_tmp\lastjob.vcf
===========================================================
VirtualDub.Open("H:\\DVD\\FORYOUREYESONLY\\gk_tmp\\FORYOUREYESONLY_1_movie.avs",0,0);
VirtualDub.video.SetMode(1);
VirtualDub.video.SetFrameRate(0,1);
VirtualDub.video.SetIVTC(0,0,-1,0);
VirtualDub.video.SetRange(0,0);
VirtualDub.video.SetCompression(0x64697678,0,10000,0);
VirtualDub.video.filters.Clear();
VirtualDub.subset.Delete();
VirtualDub.SaveAVI("H:\\DVD\\FORYOUREYESONLY\\FORYOUREYESONLY_1.avi");
===========================================================
[6/25/2004 9:20:09 AM] Duration was: 1 hour, 43 minutes 40 seconds
[6/25/2004 9:20:09 AM] Speed was: 29.52 fps.
[6/25/2004 9:20:09 AM] Expected quality of first pass size: 102.14
[6/25/2004 9:20:09 AM] Running second pass.
[6/25/2004 9:20:09 AM] Writing the following script to H:\DVD\FORYOUREYESONLY\gk_tmp\lastjob.vcf
===========================================================
VirtualDub.Open("H:\\DVD\\FORYOUREYESONLY\\gk_tmp\\FORYOUREYESONLY_1_movie.avs",0,0);
VirtualDub.video.SetMode(1);
VirtualDub.video.SetFrameRate(0,1);
VirtualDub.video.SetIVTC(0,0,-1,0);
VirtualDub.video.SetRange(0,0);
VirtualDub.video.SetCompression(0x64697678,0,10000,0);
VirtualDub.video.filters.Clear();
VirtualDub.subset.Delete();
VirtualDub.RemoveInputStreams();
VirtualDub.SaveAVI("H:\\DVD\\FORYOUREYESONLY\\FORYOUREYESONLY_1.avi");
===========================================================
[6/25/2004 11:49:52 AM] Duration was: 2 hours 29 minutes 42 seconds
[6/25/2004 11:49:52 AM] Speed was: 20.44 fps.
[6/25/2004 11:49:52 AM] Job finished.
-----------------------------------------------------------------
len0x
25th June 2004, 21:46
@Hesse
Your movie is maxed out - comp test is larger than 100%. Of course you'll get undersized movie!
About Angel - is it PAL or NTSC version ?
*Edit* I've tried PAL version and inded its quite bad source, but kerneldeint works quite ok with threshold 4 or 5 (AutoGK uses default 10). Its impossible to deal with every single source with just one setting... And I didn't manage to reproduce green line thing...
Hesse
25th June 2004, 22:53
Originally posted by len0x
@Hesse
Your movie is maxed out - comp test is larger than 100%. Of course you'll get undersized movie!
About Angel - is it PAL or NTSC version ?
*Edit* I've tried PAL version and inded its quite bad source, but kerneldeint works quite ok with threshold 4 or 5 (AutoGK uses default 10). Its impossible to deal with every single source with just one setting... And I didn't manage to reproduce green line thing...
Oh, silly me. I didn't even think of that. I'll check some of the other undersized ones and see if that is the case for them as well. Thanks for pointing that out.
For Angel, it was the NTSC version. I can reproduce the green line in the regular GK with kerneldeint. If I choose autocrop, it determines 0 pixels for left, and 2 for right. If I preview, I see green line on left side. If I change left crop to 2 or 4, then green line is gone. I'm trying to encode it again in AutoGK with a different threshold for autocrop. Does a lower number mean it will crop more?
Is it possible to add option for changing the kerneldeint threshold? I have problems with Mystery Science Theater DVDs as well. I have to deinterlace in GK for those. I believe the source for those are quite bad as well.
Originally posted by len0x
If you have runtime error on 1.42 startup - you might try this version:
http://len0x.leffe.dnsalias.com/AutoGK.zip
I removed directx reference and recompiled it with new update for Delphi.
P.S. @QNX - is any of these dlls are missing on your system:
ole32.dll
quartz.dll
msdmo.dll
Ksuser.dll
Ksproxy.ax
DSound.dll
DDraw.dll
d3d9.dll
If yes, then we might have found the problem...
all these dll's are present in system32 folder :P
and this build working fine now
Carraway
26th June 2004, 09:15
len0x, I have no clue if you're aware of this, or if it's deliberate, or whatever, but in File Mode you can enter any filename regardless of whether it exists or not, and AutoGK will accept it -- i.e. you can choose an AVI to save it to, add the job, etc. Only when you run the job and DGIndex hangs will there be any indication the file doesn't exist. So basically I'm saying AutoGK provides no error message when you choose a file that isn't there in File Mode, and that's sorta weird, right?
Also, this may be a crazy suggestion and feel free to shoot it down, but it'd be cool if when you selected, say, "test.vob" that AutoGK would then select by default an output file of "test.avi" in the input directory. BesweetGUI can do this with audio conversions and I kinda like it. Saves a great deal of time when encoding like 25 VOB files at once. Just a thought.
TheChosn
26th June 2004, 09:27
Dear autogk author,
I would be very happy if your program would run under win xp 64 as well as under normal xp, as i have heard that 64bit might almost double the encoding speed (with a 64bit optimized version of virtualdub which I believe will soon be there).
That would be very nice for the growing number of AMD64 owners out there.
Here some logs (didn't work with xvid as well):
#1
[6/26/2004 9:47:09 AM] AutoGK 1.42b
[6/26/2004 9:47:09 AM] OS: WinUnknown (5.2.3790).2 \\this is 64bit enhanced version of winxp beta 1184 (latest)
[6/26/2004 9:47:09 AM] Job started.
[6/26/2004 9:47:09 AM] Input dir: D:\Other\x\VIDEO_TS
[6/26/2004 9:47:09 AM] Output file: D:\Other\x\VIDEO_TS\aaa.avi
[6/26/2004 9:47:09 AM] Audio: Deutsch
[6/26/2004 9:47:09 AM] Subtitles: none
[6/26/2004 9:47:09 AM] Codec: DivX
[6/26/2004 9:47:09 AM] Target size: 700Mb
[6/26/2004 9:47:09 AM] Custom audio settings: CBR MP3 with bitrate: 160Kbps
[6/26/2004 9:47:09 AM] Started encoding.
[6/26/2004 9:47:09 AM] Demuxing and indexing.
[6/26/2004 9:51:33 AM] Source aspect ratio: 4:3
[6/26/2004 9:51:33 AM] Source resolution: 720x576
[6/26/2004 9:51:33 AM] Found PAL source.
[6/26/2004 9:51:33 AM] Analyzing source.
[6/26/2004 9:57:50 AM] Source is considered to be progressive.
[6/26/2004 9:57:50 AM] Found 196721 frames
[6/26/2004 9:57:50 AM] Encoding audio.
[6/26/2004 10:07:03 AM] Audio size: 157,381,568 bytes (150.09 Mb)
[6/26/2004 10:07:03 AM] Overhead: 7,158,656 bytes (6.83 Mb)
[6/26/2004 10:07:03 AM] Video size: 569,462,976 bytes (543.08 Mb)
[6/26/2004 10:07:03 AM] Target bitrate is: 579kbps
[6/26/2004 10:07:03 AM] Running compressibility test.
*************************************
EXCEPTION: Range check error
*************************************
[6/26/2004 10:07:04 AM] Job finished.
#2
VirtualDub Error
Avisynth open failure:
Evaluate: Unrecognized exception!
in gk_tmp\x_comptest.avs, line 19
[6/26/2004 10:11:26 AM] AutoGK 1.42b
[6/26/2004 10:11:26 AM] OS: WinUnknown (5.2.3790).2
[6/26/2004 10:11:26 AM] Job started.
[6/26/2004 10:11:26 AM] Input dir: D:\Other\x2\VIDEO_TS
[6/26/2004 10:11:26 AM] Output file: D:\Other\x2\VIDEO_TS\x.avi
[6/26/2004 10:11:26 AM] Audio: English
[6/26/2004 10:11:26 AM] Subtitles: none
[6/26/2004 10:11:26 AM] Codec: XviD
[6/26/2004 10:11:26 AM] Target size: 700Mb
[6/26/2004 10:11:26 AM] Custom audio settings: AC3
[6/26/2004 10:11:26 AM] Started encoding.
[6/26/2004 10:11:26 AM] Demuxing and indexing.
[6/26/2004 10:14:04 AM] Source aspect ratio: 16:9
[6/26/2004 10:14:04 AM] Source resolution: 720x576
[6/26/2004 10:14:04 AM] Found PAL source.
[6/26/2004 10:14:04 AM] Analyzing source.
[6/26/2004 10:21:10 AM] Source is considered to be progressive.
[6/26/2004 10:21:10 AM] Found 214140 frames
[6/26/2004 10:21:10 AM] Audio size: 411,147,264 bytes (392.10 Mb)
[6/26/2004 10:21:10 AM] Overhead: 1,427,584 bytes (1.36 Mb)
[6/26/2004 10:21:10 AM] Video size: 321,428,352 bytes (306.54 Mb)
[6/26/2004 10:21:10 AM] Running compressibility test.
[6/26/2004 10:24:24 AM] Duration was: 3 minutes 12 seconds
[6/26/2004 10:24:24 AM] Speed was: 55.54 fps.
*************************************
EXCEPTION: Cannot open file "D:\Other\x2\VIDEO_TS\gk_tmp\frames.log". The system cannot find the file specified
*************************************
[6/26/2004 10:24:24 AM] Job finished.
Greetz TheChosn
len0x
26th June 2004, 11:32
Originally posted by TheChosn
I would be very happy if your program would run under win xp 64 as well as under normal xp, as i have heard that 64bit might almost double the encoding speed (with a 64bit optimized version of virtualdub which I believe will soon be there).
That would be very nice for the growing number of AMD64 owners out there.
As AutoGK relies on many other programs for encoding - its impossible to make it work on XP64 if they don't support it. It lloks to me like its avisynth/filters problems. As soon as XP64 is released I'm sure tool will support it much faster than now...
P.S. for range check error you might wanna have a look ta FAQ 6.8
len0x
26th June 2004, 11:35
Originally posted by Carraway
So basically I'm saying AutoGK provides no error message when you choose a file that isn't there in File Mode, and that's sorta weird, right?
will fix that
Originally posted by Carraway
Also, this may be a crazy suggestion and feel free to shoot it down, but it'd be cool if when you selected, say, "test.vob" that AutoGK would then select by default an output file of "test.avi" in the input directory.
I can do that for file mode as well
therealjoeblow
26th June 2004, 19:42
Originally posted by len0x
standing by for updates to hidden options tool :D
I e-mailed v-0.7 to you today, Sorry it took so long, new job has been a major disruption to normal life...
--------
History:
--------
v-0.7 (June 26, 2004)
----------------------
-Added .autocrop support:
-first line is a threshold 0-255 (AutoGk uses 34 by deafault)
-second line is number of frames to examine (AutoGK uses 10 by default)
calinb
26th June 2004, 22:13
Originally posted by len0x
Some HTPC ppl would like to see main screen of the AutoGK not more than 640x480.
<snip>I tried a couple of versions of remote desktop with AutoGK. If there's a lot of interest in this subject, we should start a new thread rather than drift off-topic. However, I'd like to report that remote desktop is a workaround for networked lo-res HTPCs and AutoGK, if you don't like using the key mappings.
There are three different ways to do Remote Desktop with Windows:
1. Remote Desktop connection
2. Netmeeting
3. Remote Desktop Web Connection
They are all different ways to control your PC remotely from another Windows machine. I tried #1 and #2 above with AutoGK.
For #1, the HTPC host should be running XP-Pro because the host software is a built-in feature and relies on Terminal Services. Remote Desktop host can also run on Win2k or NT and the necessary Terminal Services are included in the "Terminal Server Edition" distri's.
The client software can be downloaded from MS and run on all Windows versions back to Win95.
The advantage of #1 is the session inherits the resolution of your client PC. Even if you host HTPC is running 640x460 mode, you can have a higher res desktop, if the client is running higher res.
For #2, you don't need Terminal Services. Just download Netmeeting from Microsoft and install it on both the host and client machines. You must enable "remote desktop sharing" capability in the setup options. AFAIK, the downside of Netmeeting, compared to option #1, is you are stuck with the res of the host PC. However, you could set your HTPC to a higher res, that may be too high to be useful on your HTPC televsion, and run AutoGK remotely. Just set it back when you're finished. Also deactivate "Remote Desktop Sharing" on the host PC when you're not using it because it uses the video hardware overlay and much of your video DSFs and other program (like WinDVD) won't run properly when it's enabled. Non-overlay video rendering works well enough to run DVD2AVI, DGIndex, Vdub, etc. and maybe some players, if you have a machine that's fast enough w/o the overlay.
There's much info on the MS site. Here's another link for FAQ and HOWTO:
http://labmice.techtarget.com/windowsxp/NetworkingXP/remote_desktop.htm
Hope this helps!
rotvel
26th June 2004, 23:34
Hi, thanks for a great tool.
I was wondering, is there a hidden option or some other workaround that makes it possible to adjust the placement of burnt-in subtitles. I have run into a few dvd's where they are placed almost in the middle of the screen, and it looks rather bad :-)
If not consider this a feature request.
Regards /max
manono
27th June 2004, 01:10
Hi-
It's easy to adjust the height of the subs. After running the Preview to have a look at the subs, and if you decide they're too high, then open the .idx file in Notepad. Where you see this line:
# Origin, relative to the upper-left corner, can be overloaded by aligment
org: 0, 0
Raise the bold-faced number to 40 or 50 to bring the subs down a lot, or a lower number to bring them down less. Then save the .idx, and open the .avs in VDubMod again to make sure they're OK. Then Save the Job and start the encoding process.
But, AutoGK is going to make the subs all over again, so while it's encoding the audio, or running the compress test, do it again for the final .idx file. I think that'll work for you.
rotvel
27th June 2004, 21:33
It worked quite nicely, thanks a lot.
Perhaps you should start a "How-To" supplement to the FAQ, a collection of more advanced AutoGK procedures. This explanation is certainly worth including.
Regards /max
((( atom )))
28th June 2004, 01:18
@len0x
i ran into several black and white encodes recently wich have colour-artifacts on patterns, e.g. in clothing or window-blinds. how about a switch or the possibility to enforce xvid's (dunno about divx) option for b/w encoding. that would surely match up with the .mono option, wich i found usefull already sometimes.
another thought:
what do you think about an option for the quality-threshhold? i recently compared a movie (brazil) wich i encoded a while ago with 608 width with a new autogk encode. autogk chose 640 res. and i amlost don't dare to say that the 608 encode was a bit more detailed due to less artifacts.
having a switch one could force a higher quality with reduced res. wich would be extremely usefull for encoding of old or generally difficult to compress movies.
old movies especially tend to have less sharpness and don't really make use of the 720 res. a dvd offers, so one wouldn't loose anything by lowering the res. but gain less artifacts. -> nice, or?
manono
28th June 2004, 02:35
Hi atom-
I think you can do what you want already. Are you using therealjoeblow's nifty utility to get your Mono audio when needed? You can also use it to greyscale the whole movie. Just check the greyscale box, start credits compression at frame number zero (or later if there's a colored studio logo at the beginning of the film), and set credits quality for 100%. If the movie is old, then there aren't much for end credits that you'll want to compress further anyway. It'll only work for XviD, but that's fine with you, isn't it?
I don't think I can help with your second question. And I don't know if you have the logs for both encodes to help me or len0x to figure out why the 2 movies turned out so differently. One thing you could do is to run both of them through DRF Analyzer to see what you can learn about the differences. The average quants and whether B-Frames were used for both are a couple of things to look for.
AlmanNewfred
28th June 2004, 03:58
Originally posted by ((( atom )))
[B]@len0x
another thought:
what do you think about an option for the quality-threshhold? i recently compared a movie (brazil) wich i encoded a while ago with 608 width with a new autogk encode. autogk chose 640 res. and i amlost don't dare to say that the 608 encode was a bit more detailed due to less artifacts.
You know, I've been thinking that the overall quality of my encodes has been lower despite the higher resolutions after the quality threshold was lowered, but I was hesitant to say anything since I haven't really given it a good test yet...
len0x
28th June 2004, 10:36
Originally posted by AlmanNewfred
You know, I've been thinking that the overall quality of my encodes has been lower despite the higher resolutions after the quality threshold was lowered
True if you compare directly two movies with diff resolutions. Of course smaller will look better. But for full screen stretch I don't think it would be that obvious. When I lowered quality - it was because I think with XviD 1.0 rips are getting too good, if you may :) I mean 80% quality is always better than 70% for instance, but it would be a waste of bitrate. In my subjective opinion 65% is enough quality (actually I can make it 66% to make sure average quant is always less then three).
Special option for minimum quality indeed would help in case you really wanna have a high-quality encode with a given target size. I'll think about it, but no promices.
((( atom )))
28th June 2004, 12:09
@manono
maybe my post wasn't that clear: i compared an old handmade rip of mine with a recently made autogk rip, so there could be plenty of reasons for the different quality. nevermind actually, since autogk does a very good job in choosing the settings and i think it was really just a matter of resolution.
about the greyscale option: thx a lot for the hint, i didin't use the tool. i used the .mono file, wich is quite handy: once you have one, you just copy it to the accoring folders and thats it. i'll check out the tool for the b/w option. can i achieve it manually, somehow?
[/edit]
just checked the tool and i can use credits compression in b/w, but i'd have to choose a fixed quality for the encode of the credits, so if i applied it to the entire movie, i would get a fixed quant encode as i understand..
[/edit]
@len0x
i always go for higher quality since sometimes i happen to visit friends with projectors and those really boost artifacts due to projection size and the way they work compared to a vga-monitor. also my tv takes vga in and is very picky on artifacs and details as well.
what i could watch by comparing the two rips is interesting anyway, though: the smaller movie just had more details, so when streched to full screen the smaller movie should still be the winner, or? i see no gain in higher resolution, if details are covered by artifacts.
any kind of switch for setting the threshhold would be sweeet. :)
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.