QUOTE(oluv @ Aug 12 2004, 08:07 PM)
i am quite new to ogg vorbis, to tell the truth i tried it yesterday for the first time, and i was fascinated by the quality it already achieves even at 4 or lower. before i was using lame at 192 to 256kbps.
i tried to compare some of the different ogg builts to hear what the differences are between them.
the first thing i found is, that the original 1.0.1 and the GT3b have a higher frequency response compared to the others, but also have a strange high-frequency amplification. at -q4 they reach around 21khz when looking at the spectrograph.
now aoTuv and megamix2 which i also tried, do not have this HF amplification, but there seems to be some low-pass filter, as at the frequency-response reaches only 19khz at -q4, besides the files-sizes of megamix2 are bigger than all the others at the same quality rate. i don't know why in the latest builts the highest frequencies were cut off, compared to the original ogg.
The original 1.0.1 and GT3b1/2 lowpass filter at 20 kHz while this value was changed in aoTuV beta 2 (which is the base of megamix 2, 1.1RC1) down to 18.9 kHz. Whether this decrease of 1 kHz is audible is a matter for blind listening testers

Just a note that any claims of quality need to backed up by blind listening tests in order to be treated seriously here. It's the only accurate way of removing the placebo effect.

QUOTE
i have no idea what changes and improvements have been made between the codecs, but i would love to know what the things are now. which codec includes the features of the others etc. and which is up-to-date?
is there some "official" release that is gonna come, or do i have to select between all the different ones?
The original 1.0.1 and GT3b1 had some issues with HF hiss/boost on sharp attacks as well as some coarse grainy sound heard in classical music. GT3b1/2 has less pre-echo at q 5 and above, though this is at the expense of 'wilder' bitrate jumps.
aoTuV beta 2 attempted to reduce these HF problems which have been verified in some recent listening tests. aoTuV beta 2 does not include the aggressive pre-echo tunings of GT3b1/2, hence we have Vorbis Megamix which combined aoTuV beta 2, QKTune beta 3.2 (pre-echo improvement at q 2 to 4.99), and GTune beta 2 (pre-echo improvement at q 5 to 10). However, while I was doing the merging, I left out something from GT3b2 which didn't bring out the pre-echo tunings affecting microattack samples. So Vorbis Megamix 2 came about, based on the new 1.1 RC1 from Xiph.Org (which was based on aoTuV beta 2 + bug fixes and tweaks), which includes better microattack handling.
The other versions include the stock 1.1 RC1 encoder plus some additional advanced switches which allow you to "do your own pre-echo tuning". This gives you more choice and control over the compromise between bitrate and quality. Do a search of the Ogg Vorbis-Tech forum to find this encoder with the two special switches.
QUOTE
i have read some things about pre-echo and other problems. which codecs suffer from this problem? i couldn't hear this with my own music-samples, maybe someone could give me a hint which particular sounds and frequencies are affected or give me a link to sample-files.
For pre-echo, look for a sample file called castanets.
http://lame.sourceforge.net/download/samples/castanets.wavIn order to train your ears to this particular artifact, encode castanets at q 0, and try to do an ABX listening test and see if you can recognise the noisy smearing. Then you should be able to pick it out in the higher q's.
As for what versions deal with pre-echo, GT3b1/2, Megamix, Megamix 2, and 1.1RC1 with the special switches. In light of HF hiss problems at medium to low q's, I suggest considering the last two.

QUOTE
my goal would be to use the lowest possible setting and get still decent quality. until now i noticed that 128kbps is already very good, and with some material i could even go down to 96kbps, which i wouldn't do though. i could use 8 or higher, but my concern is the file-size. i do not want 1:1 cd-quality. if i want CD i listen to CD. i only want to archive most of my cds on a portable rig to listen to them on the run at "near" cd-quality.
According to the recent 128 kbps listening tests, which compared Ogg Vorbis with lame MP3, iTunes AAC, Musepack, and WMA, Ogg Vorbis tied with Musepack as the winner. So one would think q 4.35 or even q 4 would be a nice place to start encoding.

QUOTE
besides i have also a question: i use CDex for encoding and until now i was dependent on the dll-libraries, as i couldn't get an external encoder to work within CDex. if i link to oggenc.exe i get an error: Cannot send data to external encoder.
maybe i am missing some setting, but i tried nearly everything. i would appreciate any help.
To rip 'on-the-fly' using an external encoder in CDex, the encoder needs to read from standard input. So for oggenc, use '-' for your input
CODE
oggenc -q 4 - -o %2
You can also add in the other switches to set tag info like artist, album, year, track num, etc.