Quote

From the Vorbis listening test and the recent 128 kbps multiformat test, Aoyumi's aoTuV Vorbis tuning was determined to be the best Vorbis encoder and hence it is now the recommended encoder.

Maybe I'm misunderstanding things a bit but shouldn't it state that aoTuV is recommended for lower bitrates and GT3b2 is recommended for higher bitrates?

[Linux:

oggenc aoTuV beta 2 (static gcc compile)

not very static at all

$ ./oggenc-aotuv
./oggenc-aotuv: /lib/libc.so.6: version `GLIBC_2.3' not found (required by ./oggenc-aotuv)

how about 100% static version for those of us without glibc2.3?

well, theres nothing "stable" about it

it doesn't at all address the problems <q4, and tests have shown that >q4 needs better/more tuning to be (more) effective than aotuv is

at this point it should be considered to tune aotuv for higher bitrates and drop gt3 all together... garf doesn't tune it any more, and all later versions from gt3b1 are just hacks anyways...


later

Hi! Could somebody help me? :
I`d like to use a lowpass filter when encoding with low bitrates (EAC). What is the additional parameter for the command line? Thanks in advance.
[a href="index.php?act=findpost&pid=226836"][{POST_SNAPBACK}][/a]

--advanced-encode-option lowpass_frequency=NN

I think it would be nice if some information about possible candidates for next recommended versions is on the first post of the thread. That way people can get some information about them without searching wild. Like information about the Megamix merge and testing of it.
[{POST_SNAPBACK}][/a]

[span style='font-size:12pt;line-height:100%']How do I know which encoder was used to make this Ogg Vorbis file?[/span]
Using either the ogginfo program or file info in your player, you can tell from the vendor tag:

Xiph.Org libVorbis I 20020717 => 1.0

Xiph.Org libVorbis I 20030909 (1.0.1)  => 1.0.1

But if I look at the tag of any given converted file more than once, it displays different information.  One time it may read 'Xiph.Org libVorbis I 20030909 (1.0.1)' and the next time I open it, it may read 'Xiph.Org libVorbis I 20020717'.

Any idea what's going on?  (or what version I'm actually using?)
[a href="index.php?act=findpost&pid=240753"][{POST_SNAPBACK}][/a]

Just would like to add that the compile of 1.1 with the impulse_trigger_profile switch available from rarewares has a vendor tag of Xiph.Org libVorbis I 20040920 and not 20040629 like 1.1 RC1.
[a href="index.php?act=findpost&pid=244294"][{POST_SNAPBACK}][/a]

esa372:
What program are you using the view the tag information?[a href="index.php?act=findpost&pid=241081"][{POST_SNAPBACK}][/a]

The old Winamp Vorbis plugin would overwrite the actual encoder version with its version whenever you changed any of the tags. This doesn't change the quality of the encode, it only makes the encoder string incorrect.

Maybe whatever you're using to tag your Vorbis files has the same bug?[a href="index.php?act=findpost&pid=240781"][{POST_SNAPBACK}][/a]

Thanks for the update, QuantumKnot...  excellent work..!

Just one question:
I see that the default setting for the 'microattack' is 2.7 - what (if any) is the default setting for the 'pre-echo'?

Anybody know?  Is there a way to check this?

Thanks!

~esa
[a href="index.php?act=findpost&pid=244739"][{POST_SNAPBACK}][/a]

The default value for impulse_noisetune is 0   impulse_noisetune is a relative setting.  It will add to whatever is the default for that quality level.  To force more aggressive coding of short blocks, lower the impulse_noisetune to negative values (max negative value is -15).

...the notion that you have to sacrifice something for a gain in speed may not be untrue here and some people prefer the safety and stability of the MSVC builds. If you want to be doubly sure that your new and shiny Ogg Vorbis files are 'stable' and 'safe', go for the MSVC builds.

Here's another question for you:
You said that...

Quote

...the notion that you have to sacrifice something for a gain in speed may not be untrue here and some people prefer the safety and stability of the MSVC builds. If you want to be doubly sure that your new and shiny Ogg Vorbis files are 'stable' and 'safe', go for the MSVC builds.

Can you explain what this "something" is that we might be loosing by using the new ICL compiles rather than the MSVC?  What are the potential drawbacks?

Thanks (again)!

~esa
[a href="index.php?act=findpost&pid=244822"][{POST_SNAPBACK}][/a]

Note 1: There is the possibility that relaxed block switching may cause other quality problems and create suboptimal Vorbis files.  So use sparingly and with caution.

...John33 merged the sources to give us GT3b2, which is now the recommended Vorbis encoder.