webkid at webkid.com
Wed Sep 21 19:37:08 PDT 2005
The aoTuV encoders have special tunings in terms of the variables in the
encoder. However, I don't believe that the aoTuV tunings involve
changing the actual engine in any major way. I could be wrong, however.
Most likely, the difference is (as you note) in the compiler. A compiler
makes every decision on what assembly code is generated and inserted
into the binary, and thus has the largest influence on speed and efficiency.
Intel makes a C compiler available specifically for their CPUs, and that
compiler takes great care to generate the most optimal assembly for
Most compilers also have the ability to be configured to optimize their
output for a particular CPU; for example, GCC can be configured with a
large number of individual optimizations (with the -f flag) or groups of
optimizations (with the -O flag), and CPU affinity (with the -mcpu and
By the way... if you're ever interested in using Linux (I can't tell if
you are already) and want the opportunity to try compiling all of the
applications on your system this way, try Gentoo.
[ http://www.gentoo.org ] It's not an "easy" first distro, but it's the
best hands on way to learn about how a system works, with dependencies
among packages, the command line, and so on.
Mario Antonius wrote:
> When I try oggenc aoTuV , it working faster than the
> original oggenc. Because of the difference compiler
> too ? if not, would you tell me where & what are is
> the difference.
More information about the Vorbis