XviD Version problem

[weaver4]

I like autogk, but I don't like the fact that it uses a non released/standard version of XviD. Since windows only allows one version of Xvid on your computer means that once you install AutoGK you can no longer use 100s of other tools like avi.net, vdub, vdubmod, megui, mpeg mediator, xvid2psp and many others.

Anyone know of a work-around?

[unskinnyboy]

What do you mean by AutoGK uses "non released/standard version of XviD"? It's always a CVS Xvid build which AutoGK uses. And what's wrong with using that same build with other tools? And even if you overwrite the AutoGK bundled Xvid with a newer version of Xvid, 99% of the time, AutoGK should work just fine.

P.S: MeGUI doesn't use VfW Xvid. It uses xvid_encraw.

[weaver4]

I have wild filesize changes when I use Version 1.1.3 and 1.2 with Autogk when I am doing single pass constant quality. I don't think the version of 1.2 that autogk is using is the one found on koepi's site http://www.koepi.info/ which adds to the confusion. I have had no luck using 1.1.3 with autogk.

I don't know; but I thought xvid_encraw uses XviD.

[unskinnyboy]

I have wild filesize changes when I use Version 1.1.3 and 1.2 with Autogk when I am doing single pass constant quality. I don't think the version of 1.2 that autogk is using is the one found on koepi's site http://www.koepi.info/ which adds to the confusion. I have had no luck using 1.1.3 with autogk.Agree that the names could be confusing, but what you get shouldn't happen, because it's not like Xvid's rate control has changed between the builds. v1.2.x in Koepi's site is the v1.2.x of AutoGK + the VAQ patch applied. You weren't using that VAQ build, right? And you sure you are uninstalling the previous Xvid build properly before installing another?

How wild were the file size changes anyway? And does it happen on all sources?

I don't know; but I thought xvid_encraw uses XviD.That's not the correct way to put it. xvid_encraw IS Xvid. But it's different from these builds which we are talking about, in that it doesn't use the Window VfW interface. xvid_encraw exists as a standalone file - xvid_encraw.exe and is the Xvid CLI.

[Brother John]

In a way weaver4 is correct because Encraw requires an xvidcore.dll that may very well come from the usual VfW package.

[weaver4]

How wild were the file size changes anyway? And does it happen on all sources?

When I use 1.2 on other applications like avi.net the filesizes are about 30% larger when I am doing constant quality with a Q=3.

I am not using the VAQ build.