lets get a new version of AutoGK out

[len0x]

First, let me say I'm still around and finally got to a point when I have a new dev environment set up and compiled current version of AutGK with it. Having not read last year+ of posts it would be good if you guys could brief me if there are any known/outstanding problems with the latest 2.48 version.

I've already updated DGIndex and filters to the latest versions and wanted to see if a new XviD version was out, so I checked out Celtic Druid's version from this spring and couldn't get it to work on my Vista64 box (can't even launch encoder configuration window) while last 12/06 version is working just fine.

I'm not actively resuming development though, but will have some time to work on it this winter.

[budwzr]

Whoo-Hoo!!!!!

[Barough]

Thats great news

[buzzqw]

welcome back len0x!

you will surely do a good work!

even if xvid is a little outdated...

BHH

[Sargon]

Lenox it is a pleasure to read your back . Agk will be improve definitly. There must be a lot of corrections. Since I use Agk, I always enjoy this program, easy to use, simple but so much powerful. There are no others that come close to AGK. My standalone runs always great, and the sound is beautiful and never too loud.... Again, I say thank you Lenox for what you already done in the past and for what's coming next.

[Codex0nz]

i remember using this app back before i went to megui and started annoying this forum with n00b questions :P

AutoGK is a wonderful application and i am very happy to see that the development of it is being revisited, this will surely help a lot of new people ease into the encoding scene and not kick & scream at it

[Taurus]

Boy, it's great to see you back on the tracks!
It was getting a little humdrum without you.
So here are the first todos:
A "new" XviD 1.2 stable just arrived.
And a so called 1.3 branch is open.
Many noobs got confused by video aspect ratios and therefore complaining.
Automatic detection is somewhat buggy.
I think older versions did a better job on this.
And you know, I'm into this since Prehistoric AutoGk..
(GordianKnotItFast4U)
Cheers

Taurus

[len0x]

Originally Posted by Taurus

And you know, I'm into this since Prehistoric AutoGk..
(GordianKnotItFast4U)

Ah, good old times

Anyway, I'm aware about XviD 1.2. Unfortuntely Celtic_Druid seems no longer around and I do need an MTK build of it...

And what about AR detection being buggy? Can I have some relevant threads about this? Cheers.

[CWR03]

How much trouble would it be to add support for episodic disks? I realize that different PGC's are selectable, but the output will always contain all eps in one file.

[linyx]

I know that this is not a feature request thread, but it might be a good idea to incorporate DivX 7 and its standalone profile(s) when it is released (soon, hopefully).

[len0x]

Originally Posted by CWR03

How much trouble would it be to add support for episodic disks? I realize that different PGC's are selectable, but the output will always contain all eps in one file.

That's because DGindex will load the whole vob set. We would need an option to do the cutting via CLI in it (assuming I can get the cut points from an IFO file, although I'm not really that familiar with DVD structure) which we do not have at the moment.

*EDIT* Actually we can select frame range in avisynth script, so in theory its possible even without DGIndex... I'm not clear how to find that frame range from IFO though yet...

[len0x]

Originally Posted by linyx

I know that this is not a feature request thread, but it might be a good idea to incorporate DivX 7 and its standalone profile(s) when it is released (soon, hopefully).

I've been out of the loop with DivX7 - does that still have VfW interface?

[den78]

glad to see you back len0x
thanks for keeping agk alive m8.

[linyx]

Originally Posted by len0x

I've been out of the loop with DivX7 - does that still have VfW interface?

Well, it supports avisynth, which is VfW, correct?

[Mtz]

Welcome back!
I that "old times" I asked you if you can implement "Keep interlaced". Your response was somethink like: "This is a useful feature". Now?
Regarding AR, try to make some test with a DV which was shoot in 16:9 mode. For pal is 720x576 but with 16:9 AR.
Mod 16 will be forever? At least mod 8 to have.

enjoy,
Mtz

[weaver4]

I made a comment a few months ago that I would like to be able to configure the location of the agk_tmp directory.

My reason for this is that I want the output of my encode to be on my media-server next to my TV, but I run autogk on my mainpc. So having the agk_tmp directory on my media-server over the network really slows down the encoding time and ties up my network.

[PoloZ7]

Great news, how long I have waited !

[len0x]

Originally Posted by linyx

Well, it supports avisynth, which is VfW, correct?

Please don't me laugh (no pun intended)

[len0x]

Originally Posted by weaver4

I made a comment a few months ago that I would like to be able to configure the location of the agk_tmp directory.

Valid request. I'll be honest though - now that I look at the hidden options (where this option would go) it doesn't make sense to keep the kind of implemenation it is at the moment (via dot files), but rather make a proper registry entries. And this would not be the first thing I would like to do...

[len0x]

Originally Posted by Mtz

Welcome back!
I that "old times" I asked you if you can implement "Keep interlaced". Your response was somethink like: "This is a useful feature". Now?

I can only assume that should have been "This is not a useful feature", right? I still don't see this as a mass usage option (especially if not all the codecs support it, but I'm rusty in this department do x264/divx7 support interlaced encoding?).

Originally Posted by Mtz

Regarding AR, try to make some test with a DV which was shoot in 16:9 mode. For pal is 720x576 but with 16:9 AR.
Mod 16 will be forever? At least mod 8 to have.

This isn't AR problem, this sound more like "too much cropping" kind of problem...