Auto Gordian Knot: current version 2.55

[len0x]

Originally posted by ((( atom )))

all in all your suggestion is good, for my special case though it brings up a rather serious problem:


Let me be clear here: I don't try to solve you special problem, but to see if there is a generic slution which can benefit many other users.

If i'm gonna be putting auto-size feature - I'm planning to do it as follows now - put an option to specify the increment in MB if quality is not reached with no maximum size limit. Auto split will no longer work on > 3CDs, but you still have a good quality.

Originally posted by ((( atom )))

and regarding the 704/720 issue: if the movie is made in 704 then 704 is the correct width to choose and if it is 720 then 720 is it. if one could simply choose "use full resolution" we would have achieved a non-resized picture anyway.

I don't know where you got 704 width from as DVDs only have 720. In case there are some pixels to crop left and right thne maximum mod 16 width is 704 indeed, but its not real movie width. As of current version of AutoGK width always scales up to 720 and not 704 as it was before.

[((( atom )))]

Originally posted by len0x
Let me be clear here: I don't try to solve you special problem, but to see if there is a generic slution which can benefit many other users. sure. i didn't want my extra-special feature just for myself. i just wrote down my specific problem, wich might affect others who are writing their movies to dvd as well.

Originally posted by len0x
... Auto split will no longer work on > 3CDs, but you still have a good quality. i am not exactly understanding. what happens >3cds? the file stays one big file?

Originally posted by len0x
I don't know where you got 704 width from as DVDs only have 720. ... i use an optibase moviemaker 200 at work a lot, wich is a professional encoder-board. the software that comes with it lets you choose between 720 width or 704, so i assume that is is a standard. also i see a lot of movies wich come in 704 width, meaning that the rest of the pixels up to is left black.
if i recall correctly also tmpegenc has an option for 704 pixels width.

[Zhnujm]

704 and 720 are both in the dvd specs.
Usually 720 is 704 pixel image + 16 pixel border and 704 only contains the image with no black borders.

[len0x]

Originally posted by Zhnujm
704 and 720 are both in the dvd specs.
Usually 720 is 704 pixel image + 16 pixel border and 704 only contains the image with no black borders.

Have you actually seen 704 DVDs?

Anyway if DVD is 704 then AutoGK will no go up to 720 by default.

[manono]

Hi-

704 and 720 are both in the dvd specs.

And so is 352. But my understanding is that official studio released retail DVDs are always 720x480/576.

[((( atom )))]

hmm, but when going up to 720 resizing would be involved again. what i actually meant, wehn i wrote about a 704 dvd, ist the usable picture, wich mostly ends up being 704 in width after cropping.

[len0x]

Originally posted by ((( atom )))
hmm, but when going up to 720 resizing would be involved again. what i actually meant, wehn i wrote about a 704 dvd, ist the usable picture, wich mostly ends up being 704 in width after cropping.

I have no intentions to cover this case atm, since AutoGK has no idea what the source is - only autocrop inside avs does...

[len0x]

Originally posted by manono
And so is 352.

I actually have a sample of this one. In AutoGK I just multiply the width by two in this case to get maximum allowed width for the clip.

[len0x]

Originally posted by ((( atom )))
i am not exactly understanding. what happens >3cds? the file stays one big file?


If I don't touch anything now, then yes. I have to see how much splitting code is affected as values 1400 and 2100 are hardcoded now.

[((( atom )))]

Originally posted by len0x
I have no intentions to cover this case atm, since AutoGK has no idea what the source is - only autocrop inside avs does... i am beginning to understand.. too bad, though, because that actually kills the nice idea of no resizing. is there a chance that you might have a look at it sometimes?

[len0x]

Originally posted by ((( atom )))
is there a chance that you might have a look at it sometimes?


I doubt, coz the whole idea was to do everything inside avs script. On the other hand it might be possible to check that inside the script, but then then we don't know if user really wants given width or need maximum cropped width. It needs investigating...

*Edit* if width gets adjusted inside of avs script then comp test result gets invalid, so its bad idea anyhow. I don't really see a problem upscaling a bit - you're doing that anyway when watching...

[len0x]

You can override autocrop parameters now.

[Sharkbyte]

Wicked, I will test it out and see how the stand-up comedian show encoding will go ! Will report back.

[pindawg]

I'm getting "error parsing input directory" with the new ver. (1.40b). I had encoded fine from this same directory with the previous version, but now get the error. Any suggestions?

[Sharkbyte]

Hmm, I thought it was something I did, I also get that problem. Went fine with 1.35b :confused:

[len0x]

That's what happening when I try to debug some stuff right before releasing new version :) Back space is a tricky button...

[pindawg]

Yeah I guess I should clarify, "previous version" was 1.35b.

[((( atom )))]

Originally posted by len0x
... but then then we don't know if user really wants given width or need maximum cropped width. It needs investigating... couldn't you just make it an option: "full movie width" or "720"?

Originally posted by len0x
... if width gets adjusted inside of avs script then comp test result gets invalid, so its bad idea anyhow. I don't really see a problem upscaling a bit - you're doing that anyway when watching... hmm, the comp-test thingie sucks, although i don't fully understand it. isn't the comp-test made _after_ cropping? ..but at this point i might not be deep enough into your routines.

what i think is bad about scaling is, that when upscaling to 720 whilst encoding and maybe even downscaling again whilst watching you certainly loose a bit or get nasty little stairs(i had quite a hard time with these before..). it all depends on your watching equipment, of course, but if one can choose the best for his equipment, a standalone user would choose his/her native tv-resolution, eg. 720 for pal and i would choose 704, wich is the absolut maximum my vga-tv can cope with. both we would have very straight viewing-chains without any scaling. :) :) :)

[mob]

Originally posted by len0x
You can override autocrop parameters now.

Thanks len0x! This feature will help me out tremendously!

Can you please elaborate on how I would go about doing this?

I can't seem to find any option for it.

[mob]

Nevermind len0x, I've figured it out on my own.

It wasn't too hard and it actually worked!

Very Nice! THANKS!

Just one question about the threshold:

Is the threshold the starting frame# for which to begin when examining the number of frames that are set?

If not, what is it for?

Thanks again len0x!

[len0x]

Originally posted by mob
Is the threshold the starting frame# for which to begin when examining the number of frames that are set?


Sorry, I wasn't clear about frame number - it is a number of frames examined by autocrop to find crop values. It is not recommened to to change default 10 unless you have substitled movie (as mpeg2/ts file) and 10 frames may be not enough (subtitle may not appear in those 10 frames and they will be cut off). Threshold itself is just level of sensitivity to the black-ish areas...

[len0x]

Originally posted by therealjoeblow
@len0x - been away for a while (changed carreers in the last month, very busy times)

standing by for updates to hidden options tool :D

[Taurus]

@therealjoeblow

standing by for updates to hidden options tool
That's what I'm counting on.
Hate to edit scripts manually :D ;)

Cheers

Taurus

[mob]

Originally posted by len0x
Sorry, I wasn't clear about frame number - it is a number of frames examined by autocrop to find crop values. It is not recommened to to change default 10 unless you have substitled movie (as mpeg2/ts file) and 10 frames may be not enough (subtitle may not appear in those 10 frames and they will be cut off). Threshold itself is just level of sensitivity to the black-ish areas...


So in order to fix my problem with the top portion of the video being cut off, you say it is not recommended to change the default 10 for the number of frames?

The only thing is that by changing the frame number to 12 and keeping a threshold of 34 I was able to encode the video perfectly fine. While changing the threshold didn't seem to do anything.

[len0x]

Originally posted by mob
The only thing is that by changing the frame number to 12 and keeping a threshold of 34 I was able to encode the video perfectly fine. While changing the threshold didn't seem to do anything.

I'd recommend starting off by changing threshold and if that doesn't help, then change number of frames. It might be that there is one very confusing frame for autocrop and by changing number of frames, selection of frames is different - therefore elminating the problem.

[Sharkbyte]

Yes, the movie encoded perfectly ! Although I'd rather had it not resize (640x464 or something, and I did set width to maximum), it did encode flawlessly without cropping ! Thank you for the great support and wonderful program !!

[Zhnujm]

Originally posted by len0x
Have you actually seen 704 DVDs?


No :) Only my own creations from DVB streams.

[jeeproject]

When using AutoGK with Xvid, default settings, and a output file size of 2GB all the movies have a low volume. This happens with other versions of AutoGK as well and with different file sizes to. Any way to fix this?

[Taurus]

Originally posted by jeeproject
When using AutoGK with Xvid, default settings, and a output file size of 2GB all the movies have a low volume. This happens with other versions of AutoGK as well and with different file sizes to. Any way to fix this?

ac3 or mp3?

For ac3 just open the ac3 decoder filter dialog and raise the settings to your desire.
And this question has been answered so many times at the doom forums.
So maybe look at the audio forum if you need further help.
Or search this thread, - has been answered many times.

[Nikse555]

The new hidden threshold parameter (at 16 for me) works great - Thx :)

[manono]

Welcome to the forum, jeepproject-

AC3, right? I think the easiest way to get more volume is to use the AC3 Filter (http://www.doom9.org/Soft21/Filters/ac3filter_0_70b.exe) to decode the Dolby Digital sound. Then go Start->Programs->AC3Filter->AC3Filter Config->Main Tab->Preset (in the lower left corner)->set to LOUD.

Taurus-

Or search this thread

Search over 2300 replies? :) But you're right, a search in any number of places would have turned up the answer. And so would a thorough reading of the AutoGK Tutorial (http://len0xmirror1.serveftp.net/~len0x/tutorial/AutoGK.html), where at the bottom it says, If the audio is too soft, go into Configuration and change the Preset to Loud (lower left)." But that damn thing is nearly as long as this thread. :)

[r6d2]

Originally posted by len0x
I actually have a sample of this one. In AutoGK I just multiply the width by two in this case to get maximum allowed width for the clip. @len0x, I was thinking if this really makes good sense... If source is 352 width (really rare anyway), and you double it, you'll probably be using much more bitrate, and without increasing quality. You may as well leave it at 352, use the available BR to increase the quality (lower quant) and let the player do the resize on playback. It should not do any more harm than resizing at encoding time and either saves space or increases quality.

[calinb]

VERSION HISTORY
1.41 beta

- added support for overriding autocrop parameters via ".autocrop" file:

len0x, Thank you, Thank you, Thank you! :D I've been waiting for this feature for a long time for my ReplayTV files. Now, with all the new support for various mpeg2 formats, it will be even more useful.:D :D :D

[Firewave]

I got problems with some movies, that are longer than 2 or 3 hours. They always run into the 30 minute demuxing/indexing timeout.
It would be nice to configure the timeouts.

[len0x]

Originally posted by Firewave
I got problems with some movies, that are longer than 2 or 3 hours. They always run into the 30 minute demuxing/indexing timeout.
It would be nice to configure the timeouts.

Demuxing step takes longer than 30 min ???
Can you measure manually with DGIndex how long it takes to do that manually? What kind of PC do you have ? Does defragmenting your hdd help ?

[len0x]

Originally posted by r6d2
@len0x, I was thinking if this really makes good sense... If source is 352 width (really rare anyway), and you double it, you'll probably be using much more bitrate, and without increasing quality. You may as well leave it at 352, use the available BR to increase the quality (lower quant) and let the player do the resize on playback. It should not do any more harm than resizing at encoding time and either saves space or increases quality.

Well, resizing on playback is definitely worse than within avisynth. Original 352 width is too small - you'll be loosing too much vertical pixels (which is normal 480/576). So width will be resized anyway, but height suffers in this case as well.

[((( atom )))]

..just got the latest autogk and actually saw the file input for the first time.

- nice -

one suggestion, though: just launching it, i sat there like a dummy in the first place and i would have to look up the readme or anything to actually know how to use the file mode, since i wouldn't know how to get my audio in there.

wouldn't it make sense to be able to actually "choose" the audiotrack(s) as a file just like the video for demuxed files?

another suggestion could be a little mouseover thingie that pops up a little ballon with a short explanation.

i didin't really follow the thread in terms of file-openeing because i would not need it yet, but that makes me a good newbie i guess ;)

[r6d2]

Originally posted by len0x
So width will be resized anyway, but height suffers in this case as well. You are absolutely right. Sorry, I forgot you are not a fan of "keep the height" encoding mode by using anamorphic aspects or original PARs.

[pindawg]

Originally posted by Firewave
I got problems with some movies, that are longer than 2 or 3 hours. They always run into the 30 minute demuxing/indexing timeout.
It would be nice to configure the timeouts.

Getting the same thing here. I've tried Mystic River twice, and it has timed out both times. Haven't tried it manually yet, but I can. Is there a way to get around this?

BTW: Running 1.7ghz P4 w WinXP Pro. All files are on a Linux server, not on local HD, so that may account for some slowdown.

[evil ryu]

When I try to set "Input directory" I get the following error: "Error parsing input directory. Make sure you used DVDDecrypter in IFO mode to rip a DVD".
I used DVDDecrypter in IFO mode as I have always done with every DVD.
What can I do to solve the problem?

[Sharkbyte]

Try the latest version (1.41b).

[MoonWalker]

Originally posted by evil ryu
When I try to set "Input directory" I get the following error: "Error parsing input directory. Make sure you used DVDDecrypter in IFO mode to rip a DVD".
I used DVDDecrypter in IFO mode as I have always done with every DVD.
What can I do to solve the problem?

I had the same problem with one movie I ripped using IFO-mode..The problem was at the VTS_01 - Stream Information.txt file that DVDDecrypter generates.

It has a line tha said :
0x80 - Audio - AC3 / 6ch / 48kHz / DRC / Unknown(' ') / LBA: 11 / PTS: 00:00:00.280 / Delay: -80ms

I changed it to this and worked :
0x80 - Audio - AC3 / 6ch / 48kHz / DRC / English / LBA: 11 / PTS: 00:00:00.280 / Delay: -80ms

Hope this helps,
MoonWalker

[Firewave]

Originally posted by len0x
Demuxing step takes longer than 30 min ???
Can you measure manually with DGIndex how long it takes to do that manually? What kind of PC do you have ? Does defragmenting your hdd help ?

The harddisk is almost empty and not that old yet, so it's quite defragmented.
How do I demux a file? "Save project"? That should take 10 minutes according to the estimated time.
My CPU is a P4 2,4Ghz with 512MB DDR333 RAM.
I did another movie, what didn't run into the timeout and recognised, that the writing during the demuing is quite slow compared to what I saw during "Save project". Maybe some optimizations not set properly when it is being used by AutoGK?

[len0x]

Some HTPC ppl would like to see main screen of the AutoGK not more than 640x480. I wonder if I can solve the problem by providing shortcuts for all button operations? (I tried resizing main window and can't fit in all the buttons...)

[evil ryu]

Originally posted by MoonWalker
I had the same problem with one movie I ripped using IFO-mode..The problem was at the VTS_01 - Stream Information.txt file that DVDDecrypter generates.

It has a line tha said :
0x80 - Audio - AC3 / 6ch / 48kHz / DRC / Unknown(' ') / LBA: 11 / PTS: 00:00:00.280 / Delay: -80ms

I changed it to this and worked :
0x80 - Audio - AC3 / 6ch / 48kHz / DRC / English / LBA: 11 / PTS: 00:00:00.280 / Delay: -80ms

Hope this helps,
MoonWalker

Thank you very much.

[((( atom )))]

Originally posted by len0x
Some HTPC ppl would like to see main screen of the AutoGK not more than 640x480. I wonder if I can solve the problem by providing shortcuts for all button operations? (I tried resizing main window and can't fit in all the buttons...) do you mean shortcuts _instead_ of buttons? i think that would make it rather confusing, because one couldn't use the application anymore without reading its manual. kinda newbie factor decreasing. also see my other post wich is related in a way.

also i myself tend to forget about options of software when using comandline tools a lot. having buttons this can't happen.

or did i get your posting wrong maybe? & what are htpc people?

[btothec2]

Home Theatre PC. Yea, I never really thought about it, but I use AutoGK on my HTPC all the time, and it would really suck if it didn't fit on screen.

[len0x]

@atom

lol :) How can you even imagine this: application without buttons??? :)
C'mon - I'm not that insane :D I meant just the same actions as on buttons for shortcuts.

@btothec2

Are you saying that now AutoGK fits nicely on the screen I was told that button for opening Save To dialog was inaccessible (width of AutoGK now is 700 pixels).

[btothec2]

len0x,

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.

[pindawg]

Any word on the timeout problem. I would like to finish a couple that timeout.

Thanks