PDA

View Full Version : Autogk not with built-in xvid codec?


molngab
29th December 2010, 19:08
Hello!

Is possible to use Autogk not with the built-in (bundled) xvid codec, but with a newer, other xvid codec (e.g.: Jawor xvid build)?

What will happen with the AutoGK? The result will be better -or worse?


Thanks!

yetanotherid
31st December 2010, 01:26
I'm not an XviD expert but I'd be surprised if it offers any improvement when using AutoGK. Maybe if you're configuring XviD manually but as the point of AutoGK is to let it configure everything, I assume many of the additions to the XviD GUI would therefore be irrelevant.
Plus many XviD builds are broken when it comes to standalone player compatibility settings (which AutoGK already has) resulting in under (or is it over?) file sizes when using those modes, although you'd hope the build in question isn't broken given the description. The only real question you'd probably need to be interested in is whether the new build can encode to a better quality than the version which comes with AutoGK, which I doubt.

# Dark Shikari's VAQ added to 1.2.2 (1.3.-31 had it already) AutoGK does VAQ which I assume is via the same XviD patch.
# Number of slices parameter for the "unrestricted" profile (if greater than 1, slice-based multithreading is activated)
# Use PSNR-HVS-M metric for VHQ checkbox activating PSNR-HVS-M for distortion calculation in VHQ
# Simple Profile @ Level 4a/5/6 added to 1.2.2 (1.3.-31 had those profiles already) AutoGK would keep using the same profiles it always has.
# "Generic Standalone" profile (just like "Xvid Home", only it allows more B-VOPs and doesn't force Packed Bitstream)
# MTK profiles for better compatibility with MediaTek-based standalone players AutoGK already configures XviD accordingly
# DivX profiles (both current and obsolete) for better compatibility with DivX-Certified standalone players I've never had a problem playing an AutoGK encode in any standalone player, ever (I always have the ESS option enabled).
# Frame Drop Ratio can be set to -1 to disable "real" N-VOPs completely (only in 1.2.2)
(in 1.3.-31 Frame Drop Ratio has been redefined and 0 disables them)
# "INTER4V" macroblock mode can be disabled by unchecking Use 4MV (for really crappy devices)
# VBV parameters can be adjusted in the "unrestricted" profile
# Closed GOV can be disabled in the "unrestricted" profile
# DivX 5 user data can be written in any profile (for better compatibility)
# "DX50" FourCC is forced in DivX profiles (for better compatibility)
# Encoder can use "MP4V" FourCC
# Maximum number of zones increased to 255
# Decoding of additional MPEG-4 FourCCs (3IVX, 3IV0, 3IV1, 3IV2, HDX4, LMP4, RMP4, SMP4) through DirectShow is supported
# VfW and DirectShow decoders recognize both lower- and uppercase FourCCs
# Latest bug fixes
# Many cosmetic GUI changes

Some of the other changes I don't understand fully, many will be irrelevant when using AutoGK. That's one of the reasons I use it, it does the thinking for you, basically making it harder for you to mess things up in the process.
If you open up the XviD configuration GUI and reset it to default, then run an encode using AutoGK (maybe enable a compatibility option) and while the encode is running you open the XviD encoder again, you'll see AutoGK has configured XviD accordingly. That's why I suspect, unless the version under discussion is actually a better encoder, which I doubt, AutoGK will keep configuring XviD the same way it always has and the end result will be exactly the same.

Maybe try the newer build and find out?

molngab
31st December 2010, 10:04
The argument is true.
Only in today's fast world, I find it strange that Autogk do not uses the most latest xvid codec available.
Even if not better. but newer!

netmask
31st December 2010, 20:26
Autogk is no longer supported by it's author since a few years ago. So whilst it is a great program for what it does it's time to move on unless someone can make an arrangement with the author to take it over and develop it further..

yetanotherid
1st January 2011, 04:39
The argument is true.
Only in today's fast world, I find it strange that Autogk do not uses the most latest xvid codec available.
Even if not better. but newer!

You can of course uninstall XviD and install the version of your choice instead, but I learned my lesson years ago. It took me a long time to find out AutoGK wasn't getting the file sizes corrects because of the version of XviD I had installed.

Autogk is no longer supported by it's author since a few years ago. So whilst it is a great program for what it does it's time to move on unless someone can make an arrangement with the author to take it over and develop it further..

Of course that statement must assume it's because there's other encoders which encode to AVI better than AutoGK does, or because for some reason AutoGK doesn't do the job as well today as it did yesterday.
As AutoGK still does what it was designed to do perfectly well, and as it resizes more intelligently than other other GUI I've used, I'll probably still be using AutoGK right up until I convert my last video to AVI.
Not to mention the fact that if you encode for a particular file size rather than quality (and it's beyond me why the practice continues so much) AutoGK will adjust whatever settings it can to give you the best quality for the file size you chose, and it'll also report the quality expected after the first pass. How many of the newer GUIs do either of those things? Aside from the fact I've not found any which do, the plethora of blocky 350MB, 700MB etc. AVIs scattered over the internet would seem to indicate most of them don't.

Just to share the joy..... AutoGK converts AVI to AVI. I also discovered a while back it'll convert other file types to AVI too. All you need to do is change the file's extension from MP4 or MKV etc to AVI, encode the video and change it back when you're done.
You can't convert the audio that way as AutoGK can't demux it, but you can convert the video.
I use foorbar2000 to convert the audio myself as it'll open and convert the audio inside MP4s and MKVs, so while AutoGK is doing it's thing I do the audio and then mux the two into a new AVI with VirtualDubMod when it's finished.

In order for AutoGK to convert other formats to AVI aside from AVI and mpeg2.....
I have the Combined Community Codec Pack installed. You don't have to install the codec pack but I believe it is the Haali splitter included in the codec pack which is enabling the "fool AutoGK into thinking it's opening an AVI" trick to work. You can of course use any program you choose to convert the audio, but for completeness of information if it's foobar2000 look for the "convert 5.1ch audio to stereo" plugin as you can't convert 5.1ch to MP3 without it. Other useful plugins are the AC3 decoder, AAC decoder, the DirectShow input plugin and the AVS plugin (which lets foorbar2000 open audio in other video containers via an AVISynth script).
AVISynthesizer is a handy utility for making those scripts with a couple of mouse clicks, and the LAME MP3 and AFTEN AC3 encoders need to be installed separately.

Given I use AutoGK to convert newer video formats to AVI, and given I use foobar2000 to convert the audio they contain, I guess it'd be fair to say I've moved on while also continuing to use AutoGK. ;)
And in my opinion foobar2000 is the best audio player for Windows out there.