Slashdot Mirror


2nd Multi-Format 128kbps Public Listening Test

technology is sexy writes "Roberto Amorim has launched his latest public listening test evaluating the performance of different audio codecs at 128kbps, among them Apple's AAC implementation (used in iTunes), LAME, Ogg Vorbis fork auTuV, WMA, Musepack and even Sony's Atrac3 format, which is soon to be used in their own music store. Read more on Hydrogenaudio and check out the results of prior tests. As opposed to most evaluations of audio codecs, this is a scientific test adhering to ITU-R BS.1116-1 as much as possible while still allowing everybody to participate."

62 of 316 comments (clear)

  1. Listening test? by Anonymous Coward · · Score: 5, Funny

    Never heard of it.

  2. Ogg! by gekkotron · · Score: 4, Funny

    Ogg, ogg ogg. Ogg oggity ogg ogg!

    Now that that's out of the way, let the insightful comments begin.

    1. Re:Ogg! by MikeXpop · · Score: 4, Informative

      Here's insightful. Ogg is a wrapper. It has nothing to do with the quality of the sound. You should be chanting Vorbis.

      --
      Etiquette is etiquette. He kills his mother but he can't wear grey trousers.
    2. Re:Ogg! by gekkotron · · Score: 4, Funny

      Vorbis vorbis vorbis!

      Nope, it just doesn't have the same ring to it.
      Plus, vorbisty just doesn't work.

    3. Re:Ogg! by Anonymous Coward · · Score: 5, Insightful

      I wish there was a filter that scored any post with the words "You're new here, aren't you?" -5 stupid joke.

    4. Re:Ogg! by Neil+Blender · · Score: 5, Funny

      I wish there was a filter that scored any post with the words "You're new here, aren't you?" -5 stupid joke.

      I, for one, would welcome our new filter overlords.

    5. Re:Ogg! by Jugalator · · Score: 3, Funny

      Badger badger badger!

      Now that has a ring to it!

      --
      Beware: In C++, your friends can see your privates!
    6. Re:Ogg! by morcheeba · · Score: 4, Funny

      You're not doing it right. Try this:

      Vorb-Vorb Vorbbity Vorb Vorb.
      Bissy Bis... ba bis bis bis.
      Vorbbity Vorbbity va va vorb. bissity bis.

  3. Objective audio analysis by 7Ghent · · Score: 2, Informative

    I know you can do frequency analysis on the output of these various codecs. Just compare that to the average human auditory capacity and you can get an objective measurement of the merits of these various compression methods.

    So uh, why is this necessary, exactly?

    1. Re:Objective audio analysis by trentblase · · Score: 5, Interesting

      Because "human auditory capacity" is not fully understood. Sure we can give standard frequency response graph, but most of these codecs take advantage of psycho-accoustic hearing models -- where certain frequencies mask other frequencies in our perception. Since this is a developing field, objective listening tests could really help determine what's working and what's not.

    2. Re:Objective audio analysis by The+Clockwork+Troll · · Score: 5, Insightful
      That is a great idea in theory, however there is much debate on how psychoacoustics work, i.e. what information really "needs" to be there in music in order to be perceived.

      For example, conventional wisdom says that the human ear cannot detect sounds above roughly 20kHz, yet there is at least some anecdotal evidence that higher order harmonics shape what we hear.

      If "normal" human auditory capacity was a completely decoded topic, there wouldn't be nearly as much a need for different approaches to music compression (it would be a much simpler problem with fewer possible solutions)

      --

      There are no karma whores, only moderation johns
    3. Re:Objective audio analysis by j3ll0 · · Score: 4, Insightful


      Well I could be wrong, and forgive me if I've misinterpreted your post...but

      Don't all of these compression algorithms rely on psychacoustic modeling to remove 'extraneous' information from the bitstream?

      If that is correct, and the algorithms are implemented correctly, then really what we are looking for is the best perceived result.

      Just because the output meets the algorithm input->output specs, justn't mean it's the best output as perceived by humans.

      Maybe think of it as optimizing sort routines? Yep, bubble-sort or b-tree still output a sorted list, but the perceived value is that the b-tree is better because it performs it's function more quickly.

      This isn't an exercise in getting the frequencies algorithmically correct - the end result has to be listenable.

      Humans are analog devices...

    4. Re:Objective audio analysis by trentblase · · Score: 2, Insightful

      They do that with small groups, but the point of making this study public is to get a larger sample size without having to plunk down serious cash to set up a "reliable test environment" for thousands of listeners. Also what kind of codec bias could you possibly be referring to?

    5. Re:Objective audio analysis by Woogiemonger · · Score: 4, Interesting

      Because "human auditory capacity" is not fully understood. Sure we can give standard frequency response graph, but most of these codecs take advantage of psycho-accoustic hearing models -- where certain frequencies mask other frequencies in our perception. Since this is a developing field, objective listening tests could really help determine what's working and what's not.

      From my understanding of MP3 compression and others, the compression protocols take advantage of this frequency masking, so if humans can't hear it, it removes it. It also obviously takes into account frequency ranges of hearing. As a side note, I think it might be neat to be able to compress 30-50% better based on your personal hearing characteristics, but it'd stink if you got old and had to not only wear a hearing aid, but also start collecting MP3's all over again.

    6. Re:Objective audio analysis by Anonymous Coward · · Score: 5, Informative
      The purpose of a "perceptual" encoder such as MP3 is to remove the frequencies one cannot perceive. The frequency graph therefore need not be the same as the original and yet the encoded version may not be distiguishable from the original.

      Also, a frequency plot tells us nothing about the phase or frequency distribution at certain times in the signal. I can make a sine sweep that would match exactly the spectrum of a pop song, but obviously would sound nothing like it.

      There are ways of objectively measuring the performance of perceptual encoders, but frequency analysis isn't really one of them.

    7. Re:Objective audio analysis by tashanna · · Score: 4, Informative

      Frequency analysis only gets you part way there. For those who didn't look around at the articles (I'm not refering to you, of course; just some hypothetical /. reader), there are time domain audio effects that are not visible on FFT plots. An example of this is pre-echo. With pre-echo you get a n echo of an upcoming sound (like a drum beat) before the actual sound happens. This can happen when linear-phase FIR filters are used, but is also an artifact of some frequency domain encoder/decoder systems. The FFT is only part of the story.

    8. Re:Objective audio analysis by k-zed · · Score: 2, Funny

      ..because your hearing doesn't work like that. the sound quality perceived can't be easily told from frequency graphs and so on (ever heard of the PWB effect?)

      --
      we discovered a new way to think.
    9. Re:Objective audio analysis by dewdrops · · Score: 3, Informative

      The different formats don't simply limit the frequencies stored. A given compression format will change the sound in different ways depending on what input soundfile is. Some codecs perform well with some types of sounds, but poorly with others (for example, the compression your cell phone uses is good at speech but lousy at music).

      Also, all frequencies aren't of equal importance to a our ears. Our hearing is best in the middle range (near where the important elements of speech are), and taper off above and below. And, if there are multiple sounds occuring at the same time (a loud guitar and soft violin), our ears don't hear the softer sounds as well.

      You can't simply do a FFT of all of input and output files and simple add up the differences, as all the differences aren't created equally.

    10. Re:Objective audio analysis by jonastullus · · Score: 2, Insightful

      So uh, why is this necessary, exactly?

      hmm, the whole point of the "lossy" compression algorithms is to filter out information the human ear/brain is unable/unwilling to hear (psychoacoustics, ...). therefore just comparing the decoded signal with the original won't do, because the "subjectively" heard difference is what matters.

      and adhering to a certain norm and "scientific method" when comparing those codecs can't be bad...

      so what is it exactly that you find unneccesary??

    11. Re:Objective audio analysis by JTek · · Score: 2, Funny

      I don't know about you, but I don't listen to my music on a spectrum analyser.

    12. Re:Objective audio analysis by badasscat · · Score: 3, Interesting

      Also what kind of codec bias could you possibly be referring to?

      Apparently he doesn't realize that this is a double-blind test - meaning neither the listener nor the tester knows what codec is being presented at any given time.

      I'm taking the test now (well, not right now, taking a break) and it's about as scientific as I think you could make a public test taken in the home. Yes, the samples get compressed and then put in easily accessible folders with proper file name extensions, but you never know what you're actually listening to when you're running the testing program. All you have is a source file for comparison, then two buttons marked "1" and "2", one of which is the source again, the other a randomized codec. You never know which of the two buttons is the uncompressed source and you also never know which codec you're hearing. The results are also encrypted, so it's not as if you can just go into the results files and look at what codecs you favor.

      I suppose someone who's truly got the Ear of the Gods could listen to the samples outside of the testing program, pick various identifiable traits out of each, then listen for those traits in the testing program and vote up or down whatever codecs he or she chose, but that would be exceedingly difficult and more than a little time-consuming. I can't see how it would be worth it, especially as no single test result is going to skew the overall results to any significant degree.

      This is the first time I've ever taken a test like this and I am honestly pretty shocked at how good all of these codecs sound. I am having a really hard time even deciding which is the compressed track most of the time, and I consider myself something of an audiophile. I'm even listening in a fairly controlled environment with a good pair of headphones, at a volume loud enough to hear any background noise clearly but below any clipping whatsoever. I will be surprised if any codec really does significantly better than the others consistently when we see the final test results.

  4. No matter *what* by puargsss · · Score: 2, Insightful

    128kbps doesn't cut it. It's an absolute lossy, disgusting bitrate, no matter what it's in. They should test similar file sizes instead of by bitrate, to determine whether something is good or not- this gives a better impression of quality vs size, instead of a purely comparison based test.

    1. Re:No matter *what* by trentblase · · Score: 2, Insightful
      They should test similar file sizes instead of by bitrate

      Uhh, if they are comparing the same sample at the same bitrate, the files will be the same size. I'm not even going to respond to the other assertions... how is this possibly insightful?

    2. Re:No matter *what* by mrgreen4242 · · Score: 4, Insightful
      128kbps doesn't cut it. It's an absolute lossy, disgusting bitrate, no matter what it's in. They should test similar file sizes instead of by bitrate, to determine whether something is good or not- this gives a better impression of quality vs size, instead of a purely comparison based test.

      Uh, if the sample is the same length, and the but rate is the same, won't the file size be the same as well? A 10 second sample at 128 Kb Per Second should be 1280Kb regardless of the format, no?

      And, just FYI, MOST people, something like 95% of listeners cannot tell the difference between 128kbps sample and the original. I generally can't, even with decent headphones on.

      I think that all you compression elitist snobs work for HD manufacturers, trying to get me to buy a 250GB drive to store the same amount of music as my 60GB will hold!

    3. Re:No matter *what* by Jugalator · · Score: 4, Insightful

      No matter *what*?

      Not even if it's about average quality speakers?
      Not even if it's about some rather cheap speakers?

      I can't say I hear much of a difference with modern codecs, and I own some average speakers. Maybe 128 kbps mp3 can sound bad (although that depends a lot on the kind of music), but that's an aging codec anyway. I think encoded files in the 192 - 256 kbps range is the best, and 128 kbps ogg's often acceptable, especially with the DFX plugin (or similar) for Winamp to compensate for shortcomings in compressed formats.

      I'd definitely not call 128 kbps in modern codecs "disgusting". In ogg's I've found it to be roughly as 160-192 kbps mp3's and that's perfectfly fine for my ears.

      --
      Beware: In C++, your friends can see your privates!
    4. Re:No matter *what* by Gumber · · Score: 3, Informative

      Different codecs and implementations of those codecs may be optimized for different bitrates, so its important to test codecs at various target bitrates.

    5. Re:No matter *what* by Gumber · · Score: 4, Insightful

      And how do you know what you are asserting? Have you done properly controlled listening tests with 128kbps encoding using a variety of codecs?

      The fact is that for a lot of people, knowing the best codec at 128kbps is worth knowing because:

      1) They are using portable devices where they are space constrained
      2) They are using portable devices that may not have the perfect fidelity of a high-end sound system, but can go anywhere with them.
      3) They are using their portable device in a somewhat noisy environment that overshadows any sound quality issues caused by a lower bitrate.

    6. Re:No matter *what* by sysopd · · Score: 2, Insightful
      I guess you don't buy any CDs and only buy vinyl since quantization is inherantly lossy, and the sampling rate can only pick up the frequency range of 0 - (fs / 2). Ie, for a CD something like 0 - 22.05KHz.

      And if you're only buying 'lossless' music, when listening its most likely being reproduced with higher noise than something 'lossy' like a CD or DAT. Unless of course you have a laser-pickup on your turntable, high SNL, low THD, vacuum-tube amplifiers (to get more natural sounding sub-harmonics) and insanely high impedence circumaural headphones to block outside noise. If thats the case, by all means continue to buy 'lossless music'.

    7. Re:No matter *what* by moonbender · · Score: 3, Informative

      I must be deaf, I just did the test on a the kraftwerk sample file, and it took me a lot of relistening to finally pick out 3 out of 6 encoded files (although the first one - whatever it was - was fairly easy). The other 3 sounded exactly like the reference sample to me. This is using Sennheiser HD500 headphones and an Audigy ZX2 sound card.

      Try doing the test, you might be surprised, or conversely if you're not surprised, you might contribute valuable information to the project.

      --
      Switch back to Slashdot's D1 system.
    8. Re:No matter *what* by sysopd · · Score: 2, Informative
      That is incorrect.

      While the sine wave's frequency is known exactly (within the resolution of your sampling frequency) the amplitude is not- you always have loss due to quantization noise. You may be thinking of the fact that the fourier transform will have only one harmonic and thus the quantization noise doesn't come into play.

      Consider the signal to quantization noise rate (SQNR):

      SQNR (dB) = 20log(Vsignal/Vquantization_noise)

      With linear quantization, your quantization is evenly spaced and the noise is 0.5, with a range of -2^(n-1) to +2^(n-1) and a single bit gives roughly 6dB of resolution.

  5. Re:Honesty of responders by Per+Wigren · · Score: 5, Insightful

    Great, now all the ____ fanboys are going to forge results to make their codec look good. Talk about useless tests.

    Not possible. All you will get is a bunch of WAV-files, you have no way to tell which file belong to which codec.

    That said, I don't care which codec wins the test because Vorbis is still the only one free from patents and the margins are so incredibly small.
    Vorbis will win for me even in the unlikely scenario that it comes out last.

    --
    My other account has a 3-digit UID.
  6. Speakers by yuckymucky · · Score: 3, Insightful

    How do you bas a listening test on the web? People with crappy speakers are going to say that all of them sound bad yet the people that have the better speakers are going to have the better responses. This should be something that is done in a controled environment so that the hardware that is playing back the audio is standard.

    1. Re:Speakers by vxvxvxvx · · Score: 2, Insightful

      So what? Sure, the people (majority) with crappy speakers will give the same rating to everything, and if they were the only ones the test would tell you that. However, as the results aren't all the same obviously some people are taking the test who have better speakers. In the end, I'd much rather have the test done on a wide range of speakers to rule out the speakers favoring a certain codec.

  7. Performance is only one more factor by rnbc · · Score: 4, Insightful

    Yes... certainly this kind of listening test is important to access the capabilities of each codec.

    But in the real world other factors may be more important to chose a coded, like for example general acceptance, freely available code and specs, and a large content base available.

    You see: performance will increase allways in all codecs with time... so this kind of testing is only a minute factor amongst others.

    --
    You cannot proceed from the informal to formal by formal means
  8. How about: by rsidd · · Score: 2, Informative
    FLAC! Flac-a-flac-a-flac!

    Of course, if that turns out to be inferior to any of the other formats, it would prove that something's wrong with the tests.

    1. Re:How about: by Carnildo · · Score: 4, Funny

      FLAC! Flac-a-flac-a-flac!

      Aflac? What does a silly duck have to do with sound compression?

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
    2. Re:How about: by iabervon · · Score: 2, Funny

      Actually, a 128kbps FLAC file will probably be inferior, since it is likely to have a low sample rate or few bits per sample.

    3. Re:How about: by djtripp · · Score: 2, Funny

      aac aac AAC AAC AAC
      Sorry... i can't translate the Martian tongue... but i don't think it's Indian Love Call by Slim Whitman... encoding that in AAC would cause your computer to blow up, if the actual playing of it hadn't already.

      --
      "This is you left and that's your left. This is your right and that's your right. You're gonna die!
  9. What's the point of 128kbps? by jfroot · · Score: 3, Insightful

    Why does anyone still use 128kbps? I hate it when I download music (legal ;) and the only bitrate available for the song i want is 128. With 200GB+ hard disks being so affordable these days and everyone having high speed, I think everyone should encode their (mp3||ogg||aac) at 192 or 256.

    1. Re:What's the point of 128kbps? by ll1234 · · Score: 2, Interesting

      Any encoder sounds great if you throw enough bits at it; the trick is sounding good when the bit reservoir is shallow.

      Same deal for MPEG-2 encoders, they all look great at 7 Mbit+/sec but the real test is 3-4 Mbit/sec.

    2. Re:What's the point of 128kbps? by eean · · Score: 2, Informative

      That was my first reaction, who uses 128. What I want is a blind test with experts and thousand dollar audio systems to find at what point the experts are no longer able to tell the difference between the compressed and uncompressed audio.

      I use `lame --preset standard`, which ends up being VBR in with a max of 110-290, hovering mostly around 190-210 range. It's one of the reasons I don't use OGG, it doesn't have any preset's so I'm supposed to just decide on a good level myself. I'd rather use something that it appears someone has put some thought into.

    3. Re:What's the point of 128kbps? by pmhudepo · · Score: 2, Interesting

      I think that's not the case for many people. Not everybody has high speed internet, many people still have dial-up. Many people want their computers to last a bit longer and a 500 MHz PC with, say, 128 MB RAM en 20 GB disk, is still useful for a lot of things, if only for playing music, writing stuff and using the internet. And besides, portable players are not (easily) available in 200+ GB capacities.

      But I admit: when speed and storage are not issues, by all means go for quality. Currently, I use 192 kbps AAC and all my music stores just fine on my iPod. But both my iPod and G5 are very recent purchases and I want them to last for quite a while yet!

  10. Uh, file size *is* bitrate... by rsidd · · Score: 4, Insightful
    a given audio stream, at a given bitrate, for a given length of time, always has the same filesize. What else do you think bitrate measures?

    BTW, I think the difference between MP3 and Vorbis at 128 kb/s is perfectly noticeable. MP3 sounds rather bad, vorbis sounds pretty good. And the point is precisely to tell which format sounds best, so you don't want to do 512 kb/s bitrate where all formats sound close to CD quality.

    1. Re:Uh, file size *is* bitrate... by TheRealMindChild · · Score: 2, Insightful

      That kind of reasoning will be your downfall my friend. Should I have my webpages 100k a piece with 30k images all over the place, just because the majority of people have broadband? Should I insert obscene amounts of worthless features into my application, requiring it to have a 2000+ rated processor and buttload of ram, just because this is what the average home user has?

      When you go above 128kbps, most formats become indistiguishable from the uncompressed sample. I mean hell, most people CAN NOT hear the difference between a 128kbps mp3 and the unmangled sample it came from. For this test to work, it has to be within the threshhold of the subjects to HEAR where the compression scheme lacks.

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    2. Re:Uh, file size *is* bitrate... by afidel · · Score: 2, Interesting

      q6 is imperceptible from redbook in 19/20 samples for me, LAME --alt preset extreme (200-220 kbps VBR for most samples) is better at about 29/30 samples. This was from a double blind computer generated arangement using the same equipment and one listener with good hearing.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  11. What ever happened to r3mix.net? Any replacement? by LintMan · · Score: 2

    There used to be a great site called r3mix.net, which, IIRC, did some spectral analysis on some of the assorted compression algorithms (trying various different options for them). It was focused on the LAME mp3 encoder, but also looked at a few others.

    They also had some great forums for info on music ripping/preferred encoding methods/CD burning/etc.

    Now, that URL goes to some lame "sponsored mp3 links" site.

    Anyone know why r3mix.net died and if there's any new site that makes a good replacement?

  12. Sound quality is in the speakers by Anonymous Coward · · Score: 5, Insightful

    When you listen to compressed audio over inexpensive speakers / headphones, you can't hear the difference. With my Sony Studio Monitor headphones, I lost the difference at about 250k with mp3, so I started using 320K as that was the best at the time. Then I bought $2000 Martin Logan Mosaic Speakers, and the original CD was clearly better than even the 320K bitrate. So now I only do lossless compression. That's fine at home, but in any other environment, there's usually so much noise and distractions that even if you had excellent headphones or speakers, you wouldn't appreciate that little difference lossless brings over 256K or even 128K.

  13. Re:Okay... by sploo22 · · Score: 5, Informative

    DON'T CLICK THE LINK!

    The sad thing is that somebody went to the trouble of putting together a perfectly reasonable, logical post just to throw in a porn link. *sigh*

    --
    Karma: Segmentation fault (tried to dereference a null post)
  14. Re:Honesty of responders by notsoclever · · Score: 2, Interesting
    There is no proof that Vorbis is patent-free. "We didn't consult any implementation documents for patented algorithms" is not the same thing as "none of our algorithms are covered by a patent."

    Of course, proving the patent-freeness of Vorbis requires searching every single patent with a fine-toothed comb, further indicating how messed-up the whole patent system is at this point.

    I just have to wonder how many companies are waiting to pounce on the first major commercial user of Vorbis with a patent suit. (Yes, I know there are commercial users of Vorbis, but none are really big enough to attract patent litigation, especially since none of them are wedded enough to vorbis that they wouldn't be able to just drop it for mp3 support with its well-known and, IMO fairly-reasonable, license fees.)

    --
    There are 10 kinds of people: ones who understand ternary, ones who don't, and ones who think this joke is about binary
  15. Too bad they didn't challenge Apple by Gumber · · Score: 2, Insightful

    I'd read the thread when they were discussing which version of Apple's ACC codec to use for the test, and concluded based on a few samples that the new version was subpar.

    If they'd included both versions of iTunes/QuickTime in this test, perhaps they could have helped shame Apple into fixing what they broke.

  16. Re:The best 128kbps audio format by Carnildo · · Score: 2, Informative

    A .wav file at 128kbps is going to sound absolutely awful. At 8 bits per sample (which sounds pretty bad no matter what), 128kbps gives you a sample rate of only 16khz, so any frequencies above 8khz will be lost. If you up the sample quality to 16 bit (CD quality), the sample rate goes down to 8khz (4khz frequencies).

    And this is for monaural sound. If you want stereo, cut the sampling rate in half -- this might cut it for voice, but it won't work for anything else.

    --
    "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
  17. Re:Honesty of responders by Tribbin · · Score: 2, Insightful

    That is not lamer-proof.

    One could just send in forms with the same ratings to manipulate the test arbitrary.

    --
    If you mod this up, your slashdot background will turn into a beautiful sunset!
  18. Re:What ever happened to r3mix.net? Any replacemen by DeeKayWon · · Score: 4, Insightful
    r3mix.net died because people actually did objective analysis of his recommended LAME settings and found they were crap. IIRC, the main guy behind it wasn't very accepting of criticism. Plus, he was a message board spammer.

    The best replacement for r3mix.net in my opinion is HydrogenAudio . The forums are frequented by a lot of professionals, as well as developers of LAME, FLAC, Nero AAC, Musepack, Wavpack, and other codecs.

  19. Re:Honesty of responders by wfberg · · Score: 3, Interesting

    Not possible. All you will get is a bunch of WAV-files, you have no way to tell which file belong to which codec.

    Check the contents of the sampleXX.zip files; you actually get an mp3, an .ogg vorbis, an mp4 and 3 flacs. If you want to be biased either for or against mp3/oggvorbis/quicktime itunes AAC, you can.

    --
    SCO employee? Check out the bounty
  20. you have no clue ... by porky_pig_jr · · Score: 2, Informative

    You are 100% clueless, pardon my french.

    The bit rate of .wav file is about 1.5Mbps.

    1. Re:you have no clue ... by neurojab · · Score: 2, Funny

      >You can easily convert a 1.5Mbs wav to a 128Kbps .wav.

      >All you have to do is limit the length of the song to .083 seconds!

      good lord. There's TWO of them.

  21. Re:A nice idea by JebusIsLord · · Score: 2, Insightful

    it's double-blind, so you don't know what you're testing. Good gear has practically no bearing on identifying compression artifacts - that you need good equipment to hear slight imperfections is a myth.

    --
    Jeremy
  22. VBR? by twitter · · Score: 2, Informative
    With 200GB+ hard disks being so affordable these days and everyone having high speed, I think everyone should encode their (mp3||ogg||aac) at 192 or 256.

    Vorbis does variable bit rate and you set the quality you want. That way you don't waste lots of bits where they are not needed. My 4MB ogg file sounds as good or better than my little brother's 6MB mp3. The difference is more songs on my 256MB compact flash card. Yes, it's easy to play that music on my Zaurus, which cost about as much or less than DRM gimped portable music players.

    I hate it when I download music (legal ;) and the only bitrate available for the song i want is 128.

    Cry me a river.

    --

    Friends don't help friends install M$ junk.

  23. Re:What ever happened to r3mix.net? Any replacemen by JebusIsLord · · Score: 4, Informative

    The r3mix tuning (--r3mix), while a small step forward, was inherently flawed because of his insistance on tuning based on pictures instead of acual listening tests. As a result, the --dm-presets were invented and improved by Dibrom (the HydrogenAudio founder) along with a multitude of testers. eventually those were included in LAME as the --alt-presets (and in the latest version they just replace the normal --presets). In short, Hydrogen Audio is THE place to go for this stuff now.

    --
    Jeremy
  24. Premise of test is somwhat flawed by goombah99 · · Score: 3, Insightful
    So the whole goal is to find the system that compresses music the best in the smallest number of bits.

    After a while, once you have weeded out bad ways, one is going to reach the following situation. Each algorithm will perform very well for a large set of music and poorly for some small set of music. Barring pathologies, The poor set will be assymtotically fixable by increacing the bit rate. By the way this is not just my opinion. Theres theorems that say this is true of any compression scheme when applied to all problems.

    what does this mean? it means that the end user is never going to work at the truly low end of the bit rate specrrum because they want something that virtually always works. Plus they want a wee bit more just in case they have to transcode it. So if the recommended rate is 128 people will encode at 160.

    So these comparisons need to be done not at the bitter edge where music flaws are easy to spot because NO ONE WILL ACTUALLY MAKE THAT THE OPERATING POINT THEY USE. That is to say everyone knows vorbis sounds so-so at 64KB while MP3 sound much worse. But no one wants So-So they want darn good. So they are going to recors their Mp3 at 160 and at 160 Ogg and Mp3 sound so close that the size of the test you'd have to do to pick up the difference is silly.

    the proper way to do this is the following. Pick the gold standard format, say MP3 and its standard excellent operating point, say 160. now test all the others at lower bit rates than 160, and see which one has the lowest bit rate that scores as good as the Mp3 at 160.

    comparing all methods at a constant bit rate, esepciall a low one, is stupid

    --
    Some drink at the fountain of knowledge. Others just gargle.
  25. Re:There is no satisfying audiophiles by Gumber · · Score: 2, Insightful

    It is really refreshing to see someone so willing to demonstrate their wrongheaded ignorance. Saves us all a lot of trouble.

    I've found most of the people on Hydrogenaudio to be incredibly pragmatic. Perfection isn't the only parameter of importance. If it were, they'd not be wasting time testing codecs at 128kbps, except to demonstrate their unsuitability compaired to losless formats. They'd not be wasting time letting phillistines with their waxy untrimmed ears particpate in listening tests with their $20 sony earbuds.

    As for the vendors lauding useless gear, um, what vendors lauding useless gear?

    But hell, why let any of that get in the place of a perfectly good piece of ranting rhetoric. Still, it would be better if you'd unloaded at a deserving target. There are certainly enough of them out there.

  26. Some known facts by kevinadi · · Score: 2, Informative

    People are constantly comparing audio coding standards, but realize that most of the stuff you hear is marketing speak. Many companies have lots of IP in this area and they obviously want to make their solution the standard.

    What makes one codec sound different than others is the psychoacoustic measures implemented, quantization method, and the windowing scheme implemented before MDCT is performed. Note that all of the coders tested there do not use the same windowing method, but all of them use MDCT in a way.

    MP3 is a subband coding, it slices the audio into sub bands before transforming them. AAC, OTOH, is not. AAC uses straight MDCT and does the filtering there. The criteria for filtering is still the same old, tho. That is part of the reason why AAC at 128 kbps way outperform MP3.

    Psychoacoustic is not new, it's been described extensively in a book "Psychoacoustic" by Fastl. The catch is, audio coders have to take into account the complexity of performing the full model. MP3 uses a very simplified version of it, and it taxes the highest spec of its day. That is also the reason why AAC-LC (low complexity) is more popular than AAC-Main profile nowadays.

    Vorbis can sound better because with new hardware, a more mathematical heavy version of psychoacoustic can be implemented today. Plus, they discard the notion of constant bitrate and use quantization quality instead. This is also evident in FAAC.

    128 kbps stereo is practically the limit of almost-transparent quality audio now. 64 kbps mp3pro is just bull, it doesn't perform anywhere close to modern mp3 at 128 kbps. There is a limit on compression, and that is governed by the entropy (information content) of a signal. You go lower than entropy, you lose information, simple as that. Having said that, the only way to reduce entropy is using psychoacoustic models, and that also have a limit.

    Note also that Dolby-AC3 that is used in DVD and movie theatre compresses 5.1 channels into 384 kbps, or roughly 150-ish kbps stereo. Again, the same lower limit is evident. They do compression by combining the high frequencies > 15 khz and ignore the phase information in that high frequencies. As you can probably tell, AC-3 sounds pretty good.

    If you're interested in this area, I suggest the MPEG-4 book by Ebrahimi, Psychoacoustic by Fastl, Multimedia Compression by Gibson and DSP First by I forgot who :) Those books can provide a good basis of how all the coders tested works.