Hi guys, I have a statically linked aoTuV b5 oggenc binary lying around, so just in case anyone needs it, here's a link: oggenc-aotuvb5.bz2

Thanks - just dropped it into /usr/local/bin to not mess with my system's Vorbis libraries.

He added a link to it in the wiki also.

Just when I was too busy to make my own binary. Thanks!

Yeah, static binaries are great, because they don't mind your distro's libraries. I hope, that someday Lancer will become GCC compatible, so that Linux guys would have some speed on their side as well

Thanks man, I was planning to compile my own. Just recently switch over to Linux, it has quirk here and there but if you work them out it can replace windows easily.

hm-hm.. thanks mate, however i use my own binaries & packages (slackware rulez! )

anyway compiling these shouldn't take more than 3-5 minutes

Yeah, after using it a while, I go and compile my own share libs to overwrite the system libs so I have aotuv5 everywhere.

it wont necessarily overwrite your current files. it depends on your PATH settings. for example, slackware binaries are usually installed in /usr/bin, but a default compile will install binaries into /usr/local/bin, which is just great to have both of them.

oggenc for encoding with the old encoder
/usr/local/bin/oggenc for aotuv

simple and great. of course, you can run a configure to install them with the /usr prefix instead of /usr/local, its your choice. under linux you usually have choices

shameless plug -

rarewares/debian hosts many libvorbis tunings and drops the libs into their own lib dir (e.g. /usr/lib/libvorbis-aotuv/ ) and i package oggenc from vorbistools for each tuning that will use these libs dynamically...

(aotuv, gt3, megamix, mt, qkt, svn, etc)


later

what kind of tuning? speed-related, quality-related or both?

Just in case anyone still needs this, the binary is updated:

• oggenc is taken from svn
• there's NLS support
• international tag values now work correctly

I recommend everyone to compile on his own with an appropriate -march flag so it's optimized a bit for your own CPU (the GCC info pages have a list of CPUs for the -march flag) and -O3 -fno-strict-aliasing.

But anyway, thanks for the upload; some people might need it.

http://gentoo-wiki.com/Safe_Cflags