Xvid 1.2

[weaver4]

According to this post:

http://forum.doom9.org/showthread.php?t=125307

the 1.2 tree will not be released.

Anyway AutoGK could go back to using XviD 1.1.2 release? When I uninstall XviD 1.2 and install 1.1.2 I have odd results with AutoGK.

[weaver4]

bounce

[BigDid]

According to this post:

http://forum.doom9.org/showthread.php?t=125307

the 1.2 tree will not be released.
Hi,

I read:
There was no official releases from the 1.2 tree
... No real plans to release it
A denegation, yes; a strong and final one NO.

Also the Xvid 1.2 CVS is updated (at least by Celtic_druid): http://esby.free.fr/CelticDruid/mirror/XviD/
use: XviD.cvs.head.MTK.exe /March 2007


Anyway AutoGK could go back to using XviD 1.1.2 release? When I uninstall XviD 1.2 and install 1.1.2 I have odd results with AutoGK.
Try clearing the registry after uninstall than install the 1.12 from Celtic, same link as above ...?

I have no issues with the Xvid 1.2 installed with AutoGK and I believe I even use (not at home ATM) the last 1.2 March CVS from Celtic.
A dual core will benefit only from the 1.2 branch not from the 1.12 actually...

Did

[Bigmango]

@ OP:

1.2 is much better, if only for the fact that it supports SMP. Why would you want to go back to 1.1.2 ? You didn't say you are experiencing any problems with 1.2.

[weaver4]

The problem is that you can not have 1.2 and 1.1.2 installed at the same time so every other program on my system that want to use the latest release can't. These include programs like MeGui, staxrip, fuw, avi.net...etc. So I am having problems with many other programs once I install XviD 1.2 with AutoGK.

If I uninstall 1.2 and install 1.1.2 and use a constant quality of 67% the files come out 30-40% larger than then did with 1.2. They are also 20-40% larger than the filesizes of other programs that use 1.1.2. And yes I do clean out the registry.

Correct me if I am wrong, but I don't believe any future changes to XviD (1.1.3) will show up in 1.2 since it is on a different branch of the tree.

It is my feeling that if AutoGK installs a system wide resource (like a codec) that it should be a release/tested/supported version of the product. It would not be a big deal if registered itself as a unique codec that only Autogk uses.

But, I really love AutoGK.

[burfadel]

Staxrip works fine with newer codecs and programmes! just set it to use the new version and not to show the message again. I am using an updated:
mp4box
x264
autocrop
dgindex (1.4.9 rc1)
etc etc. with Staxrip no problems!

[weaver4]

Staxrip works fine with newer codecs and programmes! just set it to use the new version and not to show the message again. I am using an updated:
mp4box
x264
autocrop
dgindex (1.4.9 rc1)
etc etc. with Staxrip no problems!

Staxrip does not work well with 1.2, sure you can tell them to use it, but it does not do single pass cq correctly.

[celtic_druid]

The status of Xvid 1.2 hasn't changed since AutoGK started using it.

[FishTank]

The problem is that you can not have 1.2 and 1.1.2 installed at the same time so every other program on my system that want to use the latest release can't. These include programs like MeGui, staxrip, fuw, avi.net...etc. So I am having problems with many other programs once I install XviD 1.2 with AutoGK.

If I uninstall 1.2 and install 1.1.2 and use a constant quality of 67% the files come out 30-40% larger than then did with 1.2. They are also 20-40% larger than the filesizes of other programs that use 1.1.2. And yes I do clean out the registry.

Correct me if I am wrong, but I don't believe any future changes to XviD (1.1.3) will show up in 1.2 since it is on a different branch of the tree.

It is my feeling that if AutoGK installs a system wide resource (like a codec) that it should be a release/tested/supported version of the product. It would not be a big deal if registered itself as a unique codec that only Autogk uses.

But, I really love AutoGK.

i had 1.12 installed and then installed autogk, so now i have
2 xvids in vdub.
when i encode in vdub, it only uses 50% cpu (so it uses 1.12)
while with autogk, its uses 100% cpu (so 1.2).
bit odd, but it works lol

[weaver4]

Unfortunately most programs don't let you select.

People in this forum highly recommend that you completely remove 1.1.x before you install autogk, even remove the registry entries.

[FishTank]

that certainly is the "clean" way to go.
i had no idea agk comes with xvid 1.2 or else
i would have done it too.
well, im happy as long as it works :D