Auto Gordian Knot: current version 2.55

[JeeWee]

Thank you Len0x for this wonderful tool.

Since the addition of the DivX support I am wondering what DivX features AutoGK uses: Does it only use the features of the free DivX codec or does it use Pro Codec features as B-Frames and GMC?

[len0x]

Originally posted by r6d2
OAT, I'm using Auto width so I always get 720. 720 source is supposed to match 654 AVI width in "resizerless geometry space" (as 704 matches 640). Dr.DivX and GK use cropping to achieve this. Source is cropped to 704 and then scaled to 640, keeping the original geometry and just correcting the PARs.
You use another approach, change the geometry a little and keep more film pixel (and keep DAR too).


I'm not sure I understand what you're trying to say here... If you're saying that 704*xxx resolution has less aspect ratio error that 720*xxx then it all depends on the source (i.e. cropping). But in any case if you prefer width 704 then just set it to fixed value. AutoGK only uses 720 when using maximum quality mode to reflect original resolution of the source. In all other modes maximum width is 704.
(I will change it to 704 for quality based encoding soon as well)

[len0x]

Originally posted by JeeWee
Since the addition of the DivX support I am wondering what DivX features AutoGK uses: Does it only use the features of the free DivX codec or does it use Pro Codec features as B-Frames and GMC?

It does use B-frames, but not GMC. In fact it uses Home Theatre profile for compatibility with standalones.

[jonny]

Meaning your player can't stretch the picture at all?
Too bad... Mine doesn't have any probs with any input AR.

It uses some kind of stretching, but it's quite hard to verify how it works exactly (and verify that the ar is correct). Using width<720 leads in different visual results (the not visible parts progressively became smaller). Reaching some width limit (iirc the first limit is w=608), the picture gets resized and some parts goes again out the tv due to overscan.
The same goes for the height.
Quite crazy to get the correct resolution! (at least seems to have no probs on playing 720x576+ac3, so i'm in some way satisfied ^^').
It have a PAL/NTSC switch (actually switching to NTSC helps to get a *decent* ar on my old encodes).

[QuietlyGoin]

reduce the bars in widescreen movies
I know the bars are abscence of video, I simply meant to crop the RL ends off the video
I know some of my players can resize full screen, but they don't want to keep AR for .avi files like they do for .Vob files.
I know how to use pan and scan for DVDs, however, my players disable this feature when playing files instead of discs. Even the ones that do still offer zooming with AR locked does nothing, with AR unlocked zooms full with distorted AR
They are freeware and you'll find them at the Download section of doom9.
The freeware players that do zoom or go AR 4:3, degrade the video pretty badly, I have tried most of them from the downloads section

I simply thought if I were able to crop the ends of a widescreen during encoding(change my widescreen version into a fullscreen version) I would be able to get a better quality video, even using my existing players rather than the above mentioned players, because they resize video after the fact and don't have as much to work with because of it.

Like I said, I have been out of the encoding game for a while and am just looking for my own best results.:confused:Guess I will just stick with my high quality widescreens. I will just sit closer to my computer.:D

Thanks for trying to give me an answer, just not quite the answer I was hoping for. Simpler answer would maybe have been "hey stupid, if you want fullscreen buy the fullscreen movie, when you encode, it will be fullscreen." :sly::p

Thanks all, I will just sit back and shut up now, so as not to embarass myself further. Hey did you know AutoGK is perfect for newbies:D

[basiech]

Hello QuietlyGoin,

hey, this was my first post and i didn't want to offend you, just offer a working solution to the problem of watching AVIs the way you asked for (btw. i can't see any degration of the video with the mentioned Players at all)
but if you were asking for making a fullscreen avi out of a widescreen source with AutoGK, sorry i misunderstand and hope the others can help... :)

Greetz
basiech

[len0x]

XviD quality based encoding now produces good-sized output.

Main feature of this release is external subs support (sorry no splitting yet - I have to think that through) with automatic rar-ing (if WinRAR's installed).

enjoy

[len0x]

I don't think there are tools for automatic making of 4:3 output from widescreen source. 1.8 AR movies could be dealt with manually, but for 2.35 AR sources even manual cropping would result in a very low resolution, so you'd have to zoom really a lot with any player.

So in fact I don't think you can do better than zooming with those software players around.

[r6d2]

Originally posted by len0x
I'm not sure I understand what you're trying to say here... [...]
(I will change it to 704 for quality based encoding soon as well)
After I read it again I convinced myself it was hard to grasp. ;) This is it:

If you have a source AVI with square pixels and 640x480 frame size, converting it to 720x480 NTSC (keeping the height, which is the best to avoid losing more information), you resize to 704x480 and pad to 720x480. This is outlined in detail here (http://www.uwasa.fi/~f76998/video/conversion/#conversion_table).

The inverse is also true. To convert a 720x480 NTSC source and keep the height, you crop to 704 and resize to 640x480. (Of course you can optimize this by cropping the black bars too.)

The good thing of this is that you keep the original height (that is what FACAR does).

An encode like this (704x480->640x480) is the least intrusive resizing, and keeps more detail producing the least artifacts. IMHO, it is the ideal for archiving.

I can indeed select 704 as width in AutoGK, but that would not keep the source height if not cropped.

The similar uncropped mapping is 720x480->655x480, but 655 is not a magic number. :)

Anamorphic sources can be dealt similarly. (Although contrary to polular belief, anamorphics are better corrected not stretching vertically, but widening horizontally.)

I'm pretty sure this cannot be understood by newbies, but a "keep the height" resizing mode would give you the best quality, even if it implies to crop those 8 pix by side (which you never get to see anyway because of overscan). :)

I hope I did it more clear this time. If still not readable, please let me know.

[QuietlyGoin]

apologies to you basiech, no actual offense taken. I just realized after I posted and got your response how unclear my question was and the fact that I didn't already tell you I had tried other players didn't help. I know I had asked about players that I didn't have, I should have listed all the ones I did have or had tried. That is why I posted as "poorly worded questions" if I could delete my post I would. And once again, len0x, sorry to bother you with a question that could have done without asking. I just thought that is what the cropping feature had done on GK, and thought it was in the software installed with autoGK, but wasn't sure. I misunderstood the posts about GK and since I haven't used it, didn't know.

[Mtz]

Originally posted by len0x
Main feature of this release is external subs support with automatic rar-ing (if WinRAR's installed).
enjoy

AutoGK, Version 0.74 beta

I have WinRar installed.
If I check "Use external subtitles", select the subtitle file in "Subtitle track:" and press "Preview", I have that:

[14.12.2003 11:34:17 PM] Writing the following script to O:\AutoGK\gk_tmp\vobsub.params
===========================================================
I:\VIDEO_TS\VTS_01_0.ifo
O:\AutoGK\gk_tmp\Movie
1
0
0 cc
CLOSE
===========================================================
[14.12.2003 11:34:25 PM] WinRAR is not found. Switching to internal subtitles.
[14.12.2003 11:34:25 PM] Job finished.

After pressing "Start" the rar-ing is executed:

[14.12.2003 11:51:40 PM] Compressing subtitles.

[darkonejr]

len0x:

How does the WinRar detection work? It doesn't detect winrar on my machine even though I have it installed.


Julian

[len0x]

I'm looking for this key in the registry:

SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\WinRAR.exe\Path

May be it's not the best way. I haven't look deeper yet...

[Mtz]

As I wrote, the problem is only in "Preview" mode.
After closing preview, and pressing "Start", no problem.

On my computer WinRar is at:
C:\Program Files\WinRAR

[len0x]

Originally posted by Mtz
As I wrote, the problem is only in "Preview" mode.
After closing preview, and pressing "Start", no problem.


ah, no worries then. I forgot to check preview - we don't need rar-ing there and some vars are not initialized by that point. So ignore that message for the time being and I'll remove it in the next version. Important thing is that encoding should work ok.

[darkonejr]

len0x:



Strange, I do have that key... maybe it's because I'm running in Win98 Compatibility mode on WIndows XP (because of the hyperthreading problem?)


EDIT: I tried it without, and that's not it... Here's the exact location and value of Path:

HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths\WinRAR.exe

Path=C:\Documents and Settings\Julian\Desktop

Julian

[pinnochio]

I'm having some problems with the burnt-in subtitles. When I choose Danish subs I get swedish subs. When I choose suomi(finnish) subs I get Danish subs. It looks like autoGK selects the subs prior to the one I select. In the log file it lists the right one.

I tried manually decoding subs with subrip and the Danish subs are in fact Danish so it's not because the DVD has mislabled subs.

Thanx for a great tool, Lenox!

What are the chances that you make an auto-remove end-credits? The quality of one cd rips would really benefit from this.

[jonny]

Originally posted by r6d2
I'm pretty sure this cannot be understood by newbies, but a "keep the height" resizing mode would give you the best quality, even if it implies to crop those 8 pix by side (which you never get to see anyway because of overscan). :)

I hope I did it more clear this time. If still not readable, please let me know.
I agree!
Plus, to make an example of overscanning: in my 720x576 encodes, the actual visible part is something like: 656x528... i'm loosing 32 pixel on left & 32 on right (while on 2.35AR movies, full height is visible)!

[len0x]

Originally posted by darkonejr
EDIT: I tried it without, and that's not it... Here's the exact location and value of Path:


Do you have this problem during encoding or just the preview ?
Coz yes, preview has issues, but this should not affect encoding...

[len0x]

Originally posted by pinnochio
I'm having some problems with the burnt-in subtitles. When I choose Danish subs I get swedish subs. When I choose suomi(finnish) subs I get Danish subs. It looks like autoGK selects the subs prior to the one I select. In the log file it lists the right one.

I tried manually decoding subs with subrip and the Danish subs are in fact Danish so it's not because the DVD has mislabled subs.


Please post the stream info file and beginning of log file.
I know that sub rippers are usually accurate, but DVDDecrypter may not be. So there is nothing I can do if stream info file doesn't match IFO. But before that I have to verify that stream info file is parsed properly, that is why I'm asking for logs.

Originally posted by pinnochio

What are the chances that you make an auto-remove end-credits?

None. Physically impossible atm. But there are way to do that manually, if you read several pages up in this thread - there will be a solution.

[satfabio]

Dear friends,

I think that the best settings for Audio AC3 and Interleaving in Virtualdubmod should be:

AC3: 192 Kbps - Interleaving: 320 ms
AC3: 224 Kbps - Interleaving: 256 ms
AC3: 256 Kbps - Interleaving: 192 ms
AC3: 384 Kbps - Interleaving: 160 ms
AC3: 448 Kbps - Interleaving: 128 ms

Now AGK put the same Interleaving for all Audio AC3.
Is this possible in the future version?

Paul

[len0x]

Originally posted by satfabio

I think that the best settings for Audio AC3 and Interleaving in Virtualdubmod should be:


just one word - why ?

[len0x]

Originally posted by r6d2
After I read it again I convinced myself it was hard to grasp. ;)


I almost missed this post. Only when Jonny replied I read a portion of your reply and thought "wait a minute, I haven't read that yet" :)

Originally posted by r6d2
I can indeed select 704 as width in AutoGK, but that would not keep the source height if not cropped.

Anamorphic sources can be dealt similarly. (Although contrary to polular belief, anamorphics are better corrected not stretching vertically, but widening horizontally.)


Heh, ok, for 4:3 sources keep height indeed makes lots of sense, but for anamorphic to keep height we have to go beyond 720 max width allowed...

[len0x]

Originally posted by jonny
Plus, to make an example of overscanning: in my 720x576 encodes, the actual visible part is something like: 656x528... i'm loosing 32 pixel on left & 32 on right (while on 2.35AR movies, full height is visible)!

This is really bizarre. What's overscanning? Do you mean that to fit 16:9 display in height which is 1.77 ratio you have to zoom a bit and crop left and right?

P.S. For DVD I don't see how this can be corrected, but divx players which cannot deal wityh this properly are rubbish imho... (and this should change soon, so that every player will be able to play any AR the way you like it)

[satfabio]

Originally posted by len0x
just one word - why ?

I don't know why, I find these settings online and I use these settings in virtualdubmod, but if is the same with the actual interleaving...no problem.

[r6d2]

Originally posted by len0x
I almost missed this post. Only when Jonny replied I read a portion of your reply and thought "wait a minute, I haven't read that yet" :)
Not difficult to happen on a hiperventilated thread like this one. (Resembles a chat) :)
Heh, ok, for 4:3 sources keep height indeed makes lots of sense, but for anamorphic to keep height we have to go beyond 720 max width allowed...
Why is there such a limit? (I have an answer, but really would like to see GK author's one, which he uses to signal red when going beyond that). ;)

In FACAR, I use gerti67's simplification: stretch the height by 3/4. However, I only do it only because:

a. It makes no sense to do otherwise when you have only 480x480 geometry space.

b. Anamorphic SVCDs are not recognized properly by most players.

But none of those restrictions exist in AVI world...

[len0x]

Originally posted by r6d2

Why is there such a limit? (I have an answer, but really would like to see GK author's one, which he uses to signal red when going beyond that). ;)


Simple hardware reason - mostly players don't support that atm. I haven't checked mine though yet. Will do soon...
Otherwise I'd be happy to deal with anamorphic source in the best way.

May be current hardware can handle anamorphic encodes even better then widecreen ones. I know that I would have no probs playing anamorphic encode on my standalone as I can stretch height on the fly to get proper AR.

Anyway, it's only an issue if you have spare space and do not bound by 1/2 CD restriction which is still more that 90% of cases (and when you resize down anyway to fit a given size).

[jonny]

I don't know too much about overscan, first time i've noticed this is after getting the mpeg4 standalone.
All i know is that the picture on tv goes slightly out of the viewable area (iirc this is done for vhs, where there are usually a lot of noise on borders).
So i have the *same missing parts* running mpeg2 on my PS2, on my mpeg4 standalone (and exactly the same happen with mpeg4 at w=720 on my standalone).
This does not happen with my PC (RADEON9500 tv-out), but there is an option to activate overscanning too iirc.

I bet someone will give you a more technical explanation.
Don't you notice overscanning in your TV?
To check this you can edit an avisynth script with different levels of colors, depending on how near you are to borders, in this way i've got the actual viewable area on my tv (i've done this encoding both in mpeg2 and mpeg4, the area is the same).

[len0x]

Originally posted by jonny
I bet someone will give you a more technical explanation.
Don't you notice overscanning in your TV?
To check this you can edit an avisynth script with different levels of colors, depending on how near you are to borders, in this way i've got the actual viewable area on my tv.

Well, by default edges are hidden indeed, but it's not a problem for me as it can be corrected by pressing just one button on the remote of my standalone...

[pinnochio]

Originally posted by len0x
Please post the stream info file and beginning of log file.
I know that sub rippers are usually accurate, but DVDDecrypter may not be. So there is nothing I can do if stream info file doesn't match IFO. But before that I have to verify that stream info file is parsed properly, that is why I'm asking for logs.

I don't have the log file anymore but the next time I get the problem I'll post the logs and stream info. But I did check that the stream info (from smartripper) was correct.

None. Physically impossible atm. But there are way to do that manually, if you read several pages up in this thread - there will be a solution.

When the end-credits are scrolling in the end of the movie it will generate a very high bitrate. AutoGK could try to detect this high bitrate at the end of the movie and cut this out. Maybe you can even detect if the picture is black and white. Most creditlist are white on black background.

[wertert]

Quality mode - nice.

I normally go for 2 CD rips. 1400Mb. If an average movie is 90mins what would the equivalent quality mode be ? I'm only after a rough idea - nothing clever. I like the idea of quality based as I'm storing my movies on a media center PC so space isn't really an issue.

I normally see a video bitrate of 1000->1300 and I go for AC3 sound. What quality is going to give me roughly the same picture as a 2 cd rip ?

And another thing ...... I'm just going some testing. I reckon about 65-70% gives the same sort of bitrate on a 90mins movie as a normal 2 cd encode. ROUGHLY !!!!

Quality based is 1 pass. Will I get a better picture using 2 pass ( ie 2 cd encode ) or 1 pass quality. I always thought you get a better result with more passes.

On last thing ........How about being able to call AutoGK from the command line ? This way some other clever code-monkey can write a batcher for it. This way we can queue jobs overnight/weekend - even if its a basic .BAT file !

ie autoGK_CLI.exe -I C:\temp\input -O C:\out.avi -sound auto -codec xvid etc etc etc. You get the idea. One thing about keeping this newbie friendly is that there will be fewer command line option to worry about.

Last thing ....... How long does a newbie remain a newbie ?

wertert

[azza_lizard]

G'day len0x,

thankyou for AGK, it's a wonderful piece of work; you have successfully taken the head-banging out of most transcodes (thanks also to everyone else for the tools behind the front-end, and hello to other AGK users).

Would it be worth your while to add a comparitive check of the Comp' Test return value? If the Comp' Test is below the users required minimum value AGK will halt or skip to the next job (when jobs are implimented).

I imagine that this would be relatively easy to impliment in code. And worth it if other users can see the value of such a setting, especially for one CD transcodes.

Kind regards,
AzzA

[r6d2]

Originally posted by wertert
I like the idea of quality based as I'm storing my movies on a media center PC so space isn't really an issue.
Then don't worry about space. Look at the quants with fddshow. Compare the ones from you satisfactory size-based encodes and choose the equivalent percentage from len0x formula: percentage=200/quant for your quality ones.

67% (2/3) is what gets you quant 3, almost perfect.
Quality based is 1 pass. Will I get a better picture using 2 pass ( ie 2 cd encode ) or 1 pass quality.
This is a religious topic and we better not get into it here ;) (It has several threads devoted to it, just :search:

[len0x]

Originally posted by pinnochio
I don't have the log file anymore but the next time I get the problem I'll post the logs and stream info. But I did check that the stream info (from smartripper) was correct.


Did you use DVDDecrypter to produce the rip?
If not, then it's kind hard to detect what's wrong...

Originally posted by pinnochio

When the end-credits are scrolling in the end of the movie it will generate a very high bitrate. AutoGK could try to detect this high bitrate at the end of the movie and cut this out. Maybe you can even detect if the picture is black and white. Most creditlist are white on black background.

AutoGK doesn't deal with source directly at all, it doesn't crop, resize etc. - everything done via avisynth, no interaction with that process is possible.

[r6d2]

Originally posted by len0x
Simple hardware reason - mostly players don't support that atm.
Interesting. I had no idea. My reason was much more conceptual and boring. :)
Otherwise I'd be happy to deal with anamorphic source in the best way.
IMHO, the best way by far is to encode anamorphically ;). Just crop the black bars and keep the PAR.

May be current hardware can handle anamorphic encodes even better then widecreen ones.
I read on someone's signature a quote that said something like: Widescreen on a bad movie just makes it twice as bad. :)

It could be extended to a bad encode. :D:D:D
Anyway, it's only an issue if you have spare space and do not bound by 1/2 CD restriction which is still more that 90% of cases (and when you resize down anyway to fit a given size).
Sorry, len0x, I don't follow this. Can you elaborate?

OAT, several pages back a newbie asked... How do I answer the "how many CDs" question? With AutoGK's current state, the answer is: just by experience, and you gain that by trial and error.

What about the following, for size-based encodes:
[list=1]
Let the user specify a minimum quality target (current percentage can be used, no need for a new parameter).
Do the comp test using quality based.
Determine the minimum number of media needed for that quality by the projected size of the encode.
Encode 2 pass size-based with that number of media.
[/list=1]
This is what D2Sroba does for SVCDs, and does it quite well. IMHO, newbies would be delighted to let the tool answer the most difficult question left by AutoGK. :)

[satfabio]

I find a little difference in this line on lastjob.vcf
I use AGK with target quality option on 100% for b-frame and codec divx and audio ac3.
This is the original line made by AGK, the character befor..... is A.
You can see below:

VirtualDub.video.SetCompData(406,"GAEAAAAAAADQBwAACgAAABQAAAD6AAAABgAAAAIAAAAFAAAAAQAAABQAAAAAAAAAAAAAAAAAAABkAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAyAAAAAAAAAAAAAAAAAACgmZnJPwAAAKCZmck/QAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAIACAADgAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOA/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA................

But if you open from virtualdub the same movies.avs, select the same settings in compression of divx with b-frame, the character befor....
is B.

VirtualDub.video.SetCompData(406,"GAEAAAAAAADQBwAACgAAABQAAAD6AAAABgAAAAIAAAAFAAAAAQAAABQAAAAAAAAAAAAAAAAAAABkAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAyAAAAAAAAAAAAAAAAAACgmZnJPwAAAKCZmck/QAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAIACAADgAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOA/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB..................

Why, this differnce?

Paul

[len0x]

Originally posted by wertert

And another thing ...... I'm just going some testing. I reckon about 65-70% gives the same sort of bitrate on a 90mins movie as a normal 2 cd encode. ROUGHLY !!!!


Comp test in AutoGK tuned to get ideally at least 70% quality. This should be your goal as well. But since resolution is always 704*xxx (unless you set it manually) then you'll get normally slightly larger size that 2CDs...

Originally posted by wertert

Quality based is 1 pass. Will I get a better picture using 2 pass ( ie 2 cd encode ) or 1 pass quality. I always thought you get a better result with more passes.


In theory quality-based mode and multi pass should give you the same quality if the same quality percentage was selected, but there are several practical factors which influence the result:

- comp test for two pass mode is not always accurate
- multipass mode may use different strategy for bit distribution (i.e. shifting bits to motion/static areas or based on PSY models, which might require first pass statistics)

But if pure model like this is for two pass encoding: just get the full maximum size and calculate quality for second pass, then there should be not much difference between modes.

Originally posted by wertert

On last thing ........How about being able to call AutoGK from the command line ? This way some other clever code-monkey can write a batcher for it. This way we can queue jobs overnight/weekend - even if its a basic .BAT file !


Batch mode will come anyway. And I won't do CLI version for public coz then ppl will make all other tools to wrap it. I'm trying to avoid hat at all costs. Just to remind you that this tool is freeware for personal use only and cannot be distributed with any other application without my authorization (if you read the license)...

[len0x]

Originally posted by r6d2

Sorry, len0x, I don't follow this. Can you elaborate?


I mean very few ppl do quality based encodings without much care of target size (this will change next year probably). So if you have 2CDs as a target, then in my experience there are not many movies which can go for higher then 720 in width with acceptable quality.
So you have to resize down anyway and option for keeping the height is pretty much useless...

Originally posted by r6d2

What about the following, for size-based encodes:
[list=1]
Let the user specify a minimum quality target (current percentage can be used, no need for a new parameter).
Do the comp test using quality based.
Determine the minimum number of media needed for that quality by the projected size of the encode.
Encode 2 pass size-based with that number of media.
[/list=1]
This is what D2Sroba does for SVCDs, and does it quite well. IMHO, newbies would be delighted to let the tool answer the most difficult question left by AutoGK. :)

That's a nice idea and pretty much doable. I might return to that after I do batch encoding feature.

[len0x]

Originally posted by satfabio
I find a little difference in this line on lastjob.vcf
I use AGK with target quality option on 100% for b-frame and codec divx and audio ac3.
This is the original line made by AGK, the character befor..... is A.


I have no idea to be honest. This string is a base64 representation of codec settings, so to find out how different it is - it has to be decoded first and only then compared. May be there are some parameters of the codec which are not exposed to the GUI (actually there are some), but being reset from GUI itself, and coded defferently in AutoGK (I used almost all params I could find in registry).

[satfabio]

Originally posted by len0x
I have no idea to be honest. This string is a base64 representation of codec settings, so to find out how different it is - it has to be decoded first and only then compared. May be there are some parameters of the codec which are not exposed to the GUI (actually there are some), but being reset from GUI itself, and coded defferently in AutoGK (I used almost all params I could find in registry).

Ok Lenx...no problem, please tell me the key of the registry where are the settings, and if its possible explane to me what is the string that is decrypt in base64.
I have the project on vb that crypt and decrypt in base64.

Thanks a lot.....Paul

[len0x]

Originally posted by satfabio
Ok Lenx...no problem, please tell me the key of the registry where are the settings, and if its possible explane to me what is the string that is decrypt in base64.


registry key is: HKCU\Software\DivXNetworks\DivX4Windows
The base64 string is that sting in between double quotes in SetCompData function of the script. I can't tell you more unfortunately.

*Edit* you can just compare that key while running AutoGK and when settings it manually - should see the diff if there is one.

[r6d2]

Originally posted by len0x
I mean very few ppl do quality based encodings without much care of target size (this will change next year probably). [...] So you have to resize down anyway and option for keeping the height is pretty much useless...
I get it now. You're right. The height thing is much more interesting for quality based encodes, not size based, since one of its purposes it to minimize the quality impact of resizing by doing it in only one dimension.
And I won't do CLI version for public coz then ppl will make all other tools to wrap it. I'm trying to avoid hat at all costs.
Just wondering... Would it be OK with you to let others do plugins for AutoGK?

I can think of some advanced features you don't want to get into because they would not be newbie oriented... For instance:
[list=1]
The keep-anamorphic thing
Credits cut/higher quant (doable in AVI2DVD or in AviSynth)
Smart left/right cropping
Auto language selection based on personal regional settings.
[/list=1]
I fully understand your concerns about people ripping people, so I prefer to ask since a plugin is not a wrapup but may be considered as such.

Also, AFAIK leaving out a CLI will not prevent others from wraping up your tool. It may make it more cumbersome, but not avoidable. (For instance, RB did a terrific job wraping up FitCD within DVD2SVCD, delivering AutoFitCD. CLIlessness to the limit).

[madprofessor]

hi i just wanted to repost my experience with autogk:
It worked fine for me with the divx5.1.1 option selected and the mp3 vbr for soound encoding but the 700mb movie has some glitches and shows more then 20 2-second scenes parts in a loop.
My congrats to the author and his attempt to sovle the gordian knot :)

[len0x]

Originally posted by r6d2

I can think of some advanced features you don't want to get into because they would not be newbie oriented... For instance:
[list=1]
The keep-anamorphic thing
Credits cut/higher quant (doable in AVI2DVD or in AviSynth)
Smart left/right cropping
Auto language selection based on personal regional settings.
[/list=1]


I don't see anything here which cannot be done within main AutoGK
(well, credits part has to be supplied somehow) especially if I have a config file for customization. I don't really see a room for plugins as such here...

Originally posted by r6d2

Also, AFAIK leaving out a CLI will not prevent others from wraping up your tool. It may make it more cumbersome, but not avoidable. (For instance, RB did a terrific job wraping up FitCD within DVD2SVCD, delivering AutoFitCD. CLIlessness to the limit).

True (I wonder how it works, btw), but I don't want to make the job easier for industry guys. Don't be mistaken - if they have oportinity then will take it. Providing intergration opportinities for other freeware projects is very dangerous (why do you think I keep it closed-source project) due to the fact that it also opened to ppl making money out of it.

[r6d2]

Originally posted by len0x
I don't see anything here which cannot be done within main AutoGK
Of course. I was just thinking about your priorities.
I don't really see a room for plugins as such here...
I'm glad I asked :)
True (I wonder how it works, btw)
It's open source. :) You can look at it. It is very, very clever. It makes FitCD think it is running on its own and masks only the interesting fields. If RB did not tell you, you cannot know it is FitCD. ;)
it also opened to ppl making money out of it.
IMHO, you should make money out of it. I doubt donateware has given you any money so far.

Rest assured that I'd buy the first release. It is so good to be a newbie with AutoGK. ;)

[r6d2]

@len0x, I forgot to turn off fuzzy thinking mode and came up with some more. :)
Originally posted by r6d2
I can think of some advanced features...:
[list=1]
The keep-anamorphic thing
Credits cut/higher quant (doable in AVI2DVD or in AviSynth)
Smart left/right cropping
Auto language selection based on personal regional settings.
Automatic overlapped AVI splitting (with optional scren which reads "Go to the restroom, wash your hands and insert next CD". :)
Smart Top/Bottom cropping (i.e., keep 1 or 2 black lines so you don't loose anything at all and still have Mod 4 height).
Automatic video noise reduction (i.e., just when needed)
[/list=1]
But I won't code a plugin without your permission, I promise! :)

[len0x]

Auto split is finally working for external subs (and they are taken into account when splitting video as well).

I reached feature freeze before next stable release. So within a week I'd like to have version 0.8 out. Please test it thoroughly...

[rmagere]

Originally posted by r6d2
Smart Top/Bottom cropping (i.e., keep 1 or 2 black lines so you don't loose anything at all and still have Mod 4 height).

I thought that big discontinuities, such as black lines that are not part of the movie, were expensive in terms of bits allocation for codecs or was that only in the old days?

[r6d2]

Originally posted by rmagere
I thought that big discontinuities, such as black lines that are not part of the movie, were expensive in terms of bits allocation for codecs or was that only in the old days?
:goodpost: Interesting question.
AFAIK, when macroblocks are not filled the output is suboptimal in a way: If you have black lines top and bottom, you may end up with one more macroblock stripe than needed.

However, if you consolidate the black bars together in the bottom, for instance, just to make the macroblock fill, those lines are not expensive, but really cheap.

[nixo]

I tested version 0.74b with "Beavis and Butt-head Do America", PAL. During analysing it was determined that the source was interlaced:

[15-12-2003 18:35:47] Source has percentage of interlacing in motion areas: 2,54
[15-12-2003 18:35:47] Source is considered to be interlaced.

Still, I am unable to spot any signs of interlacing in DVD2AVI. I am curious about the percentage threshold and whether this source should be detected as progressive or interlaced... :confused:

--
Nixo