Slashdot Mirror


Public AAC Listening Test @ ~96 Kbps [July 2011].

The folks at the Hydrogen Audio Forums have for years been benefiting the world with their patience, technical skills, and hyper-focus on sound quality, by comparing the real-world sound of various codecs and bit-rates for audio encoding. Under the scope for the latest public listening test (slated to run until July 27) are the following AAC encoders: Nero 1.5.4; Apple QuickTime 7.6.9 true VBR; Apple QuickTime 7.6.9 constrained VBR; Fraunhofer (Winamp 5.62); Coding Technologies (Winamp 5.61); and ffmpeg's AAC (low anchor).

41 of 277 comments (clear)

  1. Lame by DigiShaman · · Score: 4, Funny

    What, no comparison with LAME? How lame.

    --
    Life is not for the lazy.
    1. Re:Lame by martinX · · Score: 3, Informative

      But is there anything that plays AAC besides the iPod?

      Players
      Creative Zen Portable
      Microsoft Zune
      SanDisk Sansa (some models)
      Sony PlayStation Portable (PSP) with firmware 2.0 or greater
      Sony Walkman
      Nintendo DSi
      Any portable player that fully supports the Rockbox third party firmware
      Mobile phones
      For a number of years, many mobile phones from manufacturers such as Nokia, Motorola, Samsung, Sony Ericsson, BenQ-Siemens and Philips have supported AAC playback. The first such phone was the Nokia 5510 released in 2002 which also plays MP3s. However, this phone was a commercial failure and such phones with integrated music players did not gain mainstream popularity until 2005 when the trend of having AAC as well as MP3 support continued. Most new smartphones and music-themed phones support playback of these formats.
      Sony Ericsson phones support various AAC formats in MP4 container. AAC-LC is supported in all phones beginning with K700, phones beginning with W550 have support of HE-AAC. The latest devices such as the P990, K610, W890i and later support HE-AAC v2.
      Nokia XpressMusic and other new generation Nokia multimedia phones like N- and E-Series: also support AAC format in LC, HE, M4A and HEv2 profiles
      BlackBerry: RIM's latest series of Smartphones such as the 8100 ("Pearl"), 9500 ("Storm") and 8800 support AAC.
      Apple's iPhone supports AAC and FairPlay protected AAC files formerly used as the default encoding format in the iTunes store until the removal of DRM restrictions in March 2009.
      The Motorola Droid Family supports AAC along with several other audio codecs.
      The HTC Dream (Also known as the T-Mobile G1) is described as supporting certain subset of the full AAC format. As of 2009-04-13 at least several forms of AAC files played while others did not play.[citation needed]
      WebOS by HP/Palm supports AAC, AAC+, eAAC+, and .m4a containers in its native music player as well as several third-party players. However, it does not support Apple's FairPlay DRM files downloaded from iTunes.[43]
      Windows Phone 7: WP7's Silverlight runtime supports AAC-LC, HE-AAC and HE-AAC v2 decoding.
      Other devices
      Apple's iPad: Supports AAC and FairPlay protected AAC files used as the default encoding format in the iTunes store.
      Palm OS PDAs: Many Palm OS based PDAs and smartphones can play AAC and HE-AAC with the 3rd party software Pocket Tunes. Version 4.0, released in December 2006, added support for native AAC and HE-AAC files. The AAC codec for TCPMP, a popular video player, was withdrawn after version 0.66 due to patent issues, but can still be downloaded from sites other than corecodec.org. CorePlayer, the commercial follow-on to TCPMP, includes AAC support. Other PalmOS programs supporting AAC include Kinoma Player and AeroPlayer.
      Microsoft Windows Mobile platforms support AAC either by the native Windows Media Player or by third-party products (TCPMP, CorePlayer)[citation needed]
      Epson supports AAC playback in the P-2000 and P-4000 Multimedia/Photo Storage Viewers. This support is not available with their older models, however.
      The Sony Reader portable eBook plays M4A files containing AAC, and displays metadata created by iTunes. Other Sony products, including the A and E series Network Walkmans, support AAC with firmware updates (released May 2006) while the S series supports it out of the box.
      Nearly every major car stereo manufacturer offers models that will play back .m4a files recorded onto CD in a data format. This includes Pioneer, Sony, Alpine, Kenwood, Clarion, Panasonic, and JVC.[citation needed]
      The Sonos Digital Media Player supports playback of AAC files.
      The Barnes & Noble Nook Color electronic-book reader supports playback of AAC encoded files.
      The Roku SoundBridge network audio player supports playback of AAC encoded files.
      The Squeezebox network audio player (made by Slim Devices, a Logitech company) supports playback of AAC files.
      The

      --
      When they came for the communists, I said "He's next door. Take him away. Goddam commies."
  2. FLAC by ThePhilips · · Score: 2, Interesting

    I'm staying mostly with FLACs. Works for me. The difference between AAC/MP3 and FLAC (and CD player *) my hi-fi allows to hear quite clearly.

    (*) Source for AAC/MP3/FLAC is the Squeezebox Touch (via DacMagic) and when compared to the CD player, the difference of sound quality is noticeable. Not out right bad (that would be Squeezebox w/o DacMagic), in fact quite OK, but still far from the proper hi-fi CD player.

    --
    All hope abandon ye who enter here.
    1. Re:FLAC by maeka · · Score: 5, Insightful

      The difference between AAC/MP3 and FLAC (and CD player *) my hi-fi allows to hear quite clearly.

      If you really can easily distinguish well-encoded AAC or MP3 from FLAC you should lend us at HA your golden ears!

      I rather strongly suspect once subjected to rigorous double-blinding you might not come back speaking so boldly.

    2. Re:FLAC by maeka · · Score: 5, Informative

      FLAC sound clearer to me.

      That is not a description of the type of artifact one is likely to find in AAC or MP3. Try again.

      Yes, I have absolute pitch, if that plays any role.

      Nope, that isn't where lossy codecs fail either.

      I do not understand why people get up in arms when somebody says they her the difference: be glad that you do not.

      Up in arms? No. It was an honest inquiry. If you are truly able to distinguish AAC/MP3 from FLAC on a general basis you would be most valuable.

      Ya see, lossy codecs tend to fail in particular ways on specific types of samples. If someone was able to readily distinguish lossless from lossy across a wide (or even moderate) collection of samples they would be damn near unique and quite useful as a tester of dev changes.

      Alas lots of people talk and few actually prove they're swinging the big dick they brag about once subjected to double-blind testing.

    3. Re:FLAC by Velimir · · Score: 3, Interesting

      I heard the difference between an iTunes-encoded 320kbps MP3 and FLAC in 2/7 samples I used. This is through ABXing and using statistics. Granted, these samples were chosen as good examples that show differences between lossy and lossless. I wrote up a series of blog posts on it here: http://www.vel.co.nz/vel.co.nz/Blog/Entries/2009/8/21_ABX_of_Lossless_versus_MP3_-_Part_3_-_Results_and_Discussion.html

    4. Re:FLAC by Pieroxy · · Score: 2

      Not that FLAC sounds any different

      You were THAT close to make a fool of yourself ;-)

    5. Re:FLAC by MarkRose · · Score: 2

      I'm not sure, but I may be one of those people. How do I go about doing a double-blind test?

      In general, I can easily distinguish 160 kbps MP3 or 96 kbps AAC from a lossless encoding, sometimes to the point where it distracts from the enjoyment of what I'm listening to. I consider well encoded 192 kbps MP3 or 128 kbps AAC a minimum for something to sound "good" (not "great"). At this rate I'll often hear minor distortions, but they're generally small enough to ignore and not distracting if I'm focused on driving or coding or whatever. Above this bit rate, I have to be actively listening to hear inaccuracies. I've heard artifacts in 320 kbps MP3s. I haven't listened to any high bit rate (over 128) stereo AAC that I am aware of.

      I was tested in the 90's as having above average hearing acuity, and I often hear things others don't. I'll hear the whine of a flyback transformer 100 ft away in a quiet room. Strangely, I have difficulty understanding speech if it's not significantly louder than background noise, and have a lot more difficulty carrying a conversation in loud places than most people.

      I am interested in pursuing this... do you have any advice?

      --
      Be relentless!
  3. FFmpeg's AAC encoder is not finished by Cigaes · · Score: 4, Informative

    FFmpeg's AAC encoder is not finished (yet?), and flagged as experimental. Including it in such a test is rather a dubious idea: it is likely to give a bad impression of the whole project.

    Having the new vo-aacenc as contender for the Free Software community would IMHO have been more relevant.

  4. What's the point? by ronocdh · · Score: 2

    I'm no audiophile, though I do take the time (and space) to rip everything I buy to FLAC. What's the intended application of encoding around 96kbps? Most audio streams online passed that mark many years ago. All in all, this seems like a question best answered years ago. Can anyone point me to what I'm missing here?

    1. Re:What's the point? by progkeys · · Score: 2, Informative

      Have you ever done game programming? Here's one example: multimedia iOs apps, like games and enhanced books are severely memory constrained. Every kB saved can make a difference. Even in a large console game, memory becomes an issue. Most AAA games have hours of prerecorded music, sound effects and voiceover. If console developers can squeeze their audio by an extra 5%, without degrading the audio too much, that makes a big difference to the the memory footprint (or the amount of audio). I do audio at a flash development company that works with giant media corporations and 48kbps mp3 audio embedded in flash swfs is more common than you might think, due to the desire to keep loading times down.

      Also, one of the biggest uses of AAC is within mp4 and quicktime movies and video streams. I'm betting that the average 360p youtube video is probably encoded at 96kbps aac. Another use might be high participant video/audio conferencing where one has to download multiple simultaneous streams over the same connection.

      Another example might be streaming to remote locations in developing nations. I'm sure there are countless other applications.

  5. Re:And the point of this is? by multiben · · Score: 2

    For you, probably nothing. But some people have inquiring minds. They are the reason we don't all live in caves banging rocks together.

  6. Many claim so and most a quite wrong. by guidryp · · Score: 5, Informative

    Almost no one can hear a difference between loss-less and any of the codecs at high bit rates (256K+).

    Though many think they can, until actually blind tested.

    If you can reliably tell the difference in proper blind testing, you are likely have better hearing/perception than 99.9999 % of the population.

    I think I have great hearing, but when I did some ABX testing, my ability to distinguish drops off completely by 160 K VBR on MP3s and that is in quiet room with quality headphones straining to ID any difference.

    I am skeptical of any golden eared claims these days pooh-poohing modern codecs.

    1. Re:Many claim so and most a quite wrong. by AikonMGB · · Score: 2

      You're right, I can't tell the difference between a CD-ripped FLAC and a high-quality MP3/Vorbis/AAC at high bit-rate encoded from the same source. However, why would I bother with losing any information at all? If I keep the FLACs and CUE sheet, I have an exact duplicate of the original disc, for maybe twice the storage of a high-quality lossy file. I also use fewer resources decoding that audio. I also have the benefit of Vorbis-style comments.

      Hard drives are available at 3TB for wouldn't choose a lossless format these days. If your only reason is portable players that don't support it, then A) get a player that does, or B) encode on the fly. Incidentally, the more people purchase players that play FLAC, the more players will play it by default.

      Aikon-

    2. Re:Many claim so and most a quite wrong. by ThePhilips · · Score: 2, Informative

      Though many think they can, until actually blind tested.

      I listen mostly classics and jazz. MP3@320kbps sounds different from the FLAC. More I can't tell you. Test wasn't scientific and only partially blind: I accidentally picked from my friend's library a copy of my own CD in MP3 and played it. It sounded differently to what used to hear. Upon checking I found that those were not my FLACs, but my friend's MP3s instead.

      But yeah, I will likely fail at a proper blind test: it is simply extremely tiring to listen to all the samples and maintain a concentration for that long. MP3/AAC artifacts they are like cracks and snaps of the vinyl: they do not bother you until you notice them first time. That's why I simply decided to encode in FLACs.

      --
      All hope abandon ye who enter here.
    3. Re:Many claim so and most a quite wrong. by AikonMGB · · Score: 2

      I have a 5th-gen iPod Video, with a spinning hard drive. I installed Rockbox on it so that I wouldn't have to encode my FLACs. In the beginning, battery life was horrible, until they figured out how to use the on-board hardware MP3 decoder. Then battery life was pretty comparable between running Rockbox or the stock firmware. FLAC files, however, have always been better on battery life than either of the other two. The efficiency gains in the CPU must have outweighed the added hard drive access.

      Aikon-

    4. Re:Many claim so and most a quite wrong. by evilviper · · Score: 2, Interesting

      If you can reliably tell the difference in proper blind testing, you are likely have better hearing/perception than 99.9999 % of the population.

      This is not true.

      Frequency-domain codecs have known artifacts that CANNOT be eliminated. Pre-echo is probably the best-known example. A sample with heavy percussion or other complex impulses (like audience applause) will stand out like a sore thumb... Audience applause is one of the standards dating back to the 70s when human audio perception / lossy audio compression research was first beginning. Now applause and percussion samples are often omitted entirely from codec testing, because those paying for the studies just want some amazing, if fake, numbers for their brochures... these are the amazing 3X compression improvements you hear advertised. (See DVB+ marketing nonsense).

      Modern audio codecs don't even try to sound indistinguishable from the original. The very earliest codecs developed (by AT&T, Philips, etc.) fit that need so very well that there's very little room for improvement in that area. Instead they focus on sounding good (not perfect) in low-bitrate encoding, and the old codecs (like MPEG-1 Layer 2) simply continue to be used by broadcasters, and anyone in-the-know. Ever wonder why there's no "AC-4" codec in development?

      To suit modern codecs that don't try to sound like the original, testing methodologies were changed entirely, and you'll rarely hear a mention of this fact, even when marketing folks go and foolishly compare results from recent and 30-year-old tests using the different methodologies. Look-up some terms like MUSHRA and Perceptual Entropy.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    5. Re:Many claim so and most a quite wrong. by julian67 · · Score: 2

      99.9 %? Perhaps true of dedicated music only devices, but these days there are many other devices that play audio and which are making dedicated audio players redundant for many people. Phones and tablets tend to use DSP hardware decoding instead of software decoding. This is the case for my clunky old Nokia devices (2730 phone and N810 tablet) and for my new Archos A43IT tablet. A quick google and visit to wikipedia shows that both the iPods and iPod Touch use hardware decoders - Sigmatel, Wolfson and Cirrus variously. I didn't check every model. The iPads also use hardware audio decoding. In fact almost anything that isn't a simple audio playback device is going to use a DSP because power consumption/battery life is critical and far less predictable when you go beyond audio playback and have a relatively high resolution display, 3G and wifi.

      I'm guessing that you're a Rockbox dev. I've seen other Rockbox devs state extremely forcefully that nobody uses DSPs and it's all done in software these days. Well, the world changed (again) and DSPs are (again) commonly found on stuff that sits in your pocket and plays audio.

  7. Subjective audio comparisons are useless by HonkyLips · · Score: 2

    It is impossible to judge audio codecs through subjective tests.
    Companies that manufacture loudspeakers have spent hundreds of millions of dollars on audio quality research- not in order to make their speakers better, but to understand the psychology behind the sounds that make people choose speaker A over speaker B in a showroom. They have discovered all sorts of quirks in human psychology and perception that they exploit to boost their sales, and they have little to do with overall 'quality'. Decades of expensive, meticulous, scientifically valid studies are responsible for the range of speakers you find at the average hifi shop, and even when several identical speakers are demonstrated (but the listener is told they are all different) most people will say that speaker number 2 sounds the best.
    The same applies to audio codecs. Even if you eliminate all sorts of hardware variables, then just listening to clip A, then B, then C and subjectively deciding which one sounds 'best' is totally unreliable. The results of this type of testing are completely useless. At the very least you would need to set up a triangle test, and to do this properly with 6 codecs in a controlled environment would take a very long time and the results still wouldn't correlate with true 'quality' unless it was repeated many times with different hardware setups.
    Ignoring the psychological weaknesses in these types of tests, the playback hardware would colour the sound enough as to make the underlying test - the codec - invalid. The choice of music, the amplifier, the speakers or headphones, and the volume used for playback will all contribute their own distinctive characteristics to the audio so that person A will not be hearing the same test as person B.
    Forget codec wars. Just buy a decent pair of earphones.

    --
    Putting syrup in coffee is some form of blasphemy.
    1. Re:Subjective audio comparisons are useless by RoFLKOPTr · · Score: 2

      It is impossible to judge audio codecs through subjective tests. Companies that manufacture loudspeakers have spent hundreds of millions of dollars on audio quality research- not in order to make their speakers better, but to understand the psychology behind the sounds that make people choose speaker A over speaker B in a showroom. They have discovered all sorts of quirks in human psychology and perception that they exploit to boost their sales, and they have little to do with overall 'quality'. Decades of expensive, meticulous, scientifically valid studies are responsible for the range of speakers you find at the average hifi shop, and even when several identical speakers are demonstrated (but the listener is told they are all different) most people will say that speaker number 2 sounds the best. The same applies to audio codecs. Even if you eliminate all sorts of hardware variables, then just listening to clip A, then B, then C and subjectively deciding which one sounds 'best' is totally unreliable. The results of this type of testing are completely useless. At the very least you would need to set up a triangle test, and to do this properly with 6 codecs in a controlled environment would take a very long time and the results still wouldn't correlate with true 'quality' unless it was repeated many times with different hardware setups. Ignoring the psychological weaknesses in these types of tests, the playback hardware would colour the sound enough as to make the underlying test - the codec - invalid. The choice of music, the amplifier, the speakers or headphones, and the volume used for playback will all contribute their own distinctive characteristics to the audio so that person A will not be hearing the same test as person B. Forget codec wars. Just buy a decent pair of earphones.

      You're completely missing the point. This test is a comparison between the lossless reference samples and the codecs. You have 3 Play buttons. One is the reference file (and it TELLS you it's the reference file), the other two are randomly assigned to be the identical reference file or the lossy encode and it DOESN'T tell you which. You are supposed to choose which one is the encode and how poor it sounds compared to the reference. It's an objective test that has nothing to do with your hardware because you aren't choosing which one you like best, you are choosing which one is exactly the same as the reference. Most of them I seriously couldn't tell the difference (using a Creative Audio card and Sennheiser HD555s).

    2. Re:Subjective audio comparisons are useless by fbjon · · Score: 2

      These codecs are designed on top of those very quirks of human audio perception. And no sane person runs audio tests in a consumer shop that wants to sell you the expensive gear. Anyway, Subjective audio comparison is the only meaningful way to compare them (apart from models based on human hearing). Controlling for variables is a different problem however, you might argue tests run by random internet visitors are useless, and you might be right. Or you might not, it depends on how large the differences turn out to be.

      --
      True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
  8. Re:And the point of this is? by martinX · · Score: 4, Funny

    They are the reason we don't all live in caves banging rocks together.

    The rock-bangers created Ogg.

    --
    When they came for the communists, I said "He's next door. Take him away. Goddam commies."
  9. Re:And the point of this is? by GrievousMistake · · Score: 5, Informative

    The Hydrogen Audio Forums tests have traditionally used a sound methodology, it would probably be worth reading up on it before you comment, lest you make a fool out of yourself.

    They will not be trying to measure how 'good' each codec sounds, they are trying to measure how close it is to the source material, with a 'perfect score' being statistically indistinguishable.

    --
    In a fair world, refrigerators would make electricity.
  10. Re:And the point of this is? by MightyYar · · Score: 2

    I agree that the results are interesting, but in an age of 3TB hard drives and 8GB low-end MP3 players, I'm sure as hell not ripping to 96kbps! :)

    I have to assume this is for streaming...

    --
    W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  11. Re:No iTunes? by Haifen · · Score: 2

    iTunes uses QuickTime components, which are in the list.

    --
    Look somewhere else for a sig.
  12. Re:PROBLEM IS TESTERS HAVE CRAP GEAR !! by Skarecrow77 · · Score: 3, Insightful

    in my experience, the equipment attached to your skull is more important than the equipment you purchased.

    I've seen people with complete CRAP gear ABX at higher bitrates than I can, and I've got a pretty stout rig.

  13. Re:What? by Skarecrow77 · · Score: 3, Interesting

    I too had this same question awhile back. Why doesn't HA test commonly used codecs at, say, 192kbps or 256kbps?

    The answer? the tests fail because nobody can tell the difference. they make for very boring results.

    they run the test at 96kbps because they get usable results. people over a wide range of sound systems and hearing conditions can provide usable responses.

    What would you do with that data? hard to say. you can't really extrapolate that, say, if codec A is better than codec B at 96kbps, the same will hold true at 192kbps. In fact, I've seen the direct opposite of that in past HA tests, where various codecs trade the lead depending on bitrate.

    So "who is 96kbps for?" I don't know. but "why test 96kbps?" that's easy.

  14. Re:PROBLEM IS TESTERS HAVE CRAP GEAR !! by Kjella · · Score: 2

    Ah the audiophile mindset, if someone can't hear the invisible differences I hear then the problem is with them or their gear, because they differences are there I swear it. First of, you've got more than a passing interest if you sit around ABX testing audio codecs for any length of time, people with crap equipment might try it out a round or two but will have left long before they become more than statistical noise. The other good reason is that they tested this, long ago as MP3s were becoming popular. Top people, top equipment, around 256 kbps MP3 they couldn't tell it apart from the CD. Since then we've had better formats (AAC) and better encoders, plenty of edge cases ironed out... if you seriously think you can tell a 256 kbps AAC from iTunes and the CD apart, I'd pay to see you do it under controlled conditions. On a no cure, no pay basis of course - because I seriously doubt you could.

    --
    Live today, because you never know what tomorrow brings
  15. Re:MS shills by artor3 · · Score: 2

    "Shill" is not a synonym for "people I don't like".

  16. Self Proclaimed Golden ears should really step up. by guidryp · · Score: 4, Insightful

    Rather than typical net snobbery against lossy encoders, the self proclaimed golden ears should really help out, they are the ones that can spot encodes a mile away, they should be able help find really good/bad encodes here.

    I found myself humbled when I attempted to help out before. I had a hard time distinguishing anything but the poor encode used as control.

    Really guys this is a chance to help out, or recalibrate your preconceptions about how good/bad modern encoders are.

    Or would you rather just keep up with the unjustified snobbery?

  17. Re:Also game soundtracks by perryizgr8 · · Score: 2

    which platform has a 40mb install limit? that sounds stupid.

    --
    Wealth is the gift that keeps on giving.
  18. So have you tried the test above? by guidryp · · Score: 2

    This is not true.

    Frequency-domain codecs have known artifacts that CANNOT be eliminated. Pre-echo is probably the best-known example. A sample with heavy percussion or other complex impulses (like audience applause) will stand out like a sore thumb...

    Have you tried the test or is are you relying on something you read?

    I just downloaded the files mentioned in the main post. There are 20 samples I gave them a quick run through inside ABC-HR.

    The low mark (I assume) stands out like a sore thumb.

    But for the other 5 samples, the seem quite indistinguishable on a casual listen.

    There is one sample with a sharp percussive instrument (castenatas?) and really I can't spot the difference.

    And these are 96K files!!

    The state of the art is improving all the time.

    1. Re:So have you tried the test above? by fbjon · · Score: 2

      "I can't hear it" isn't an argument. It's an extremely subjective individual observation which cannot be challenged or refuted.

      If nobody can hear it, then I'd say it is an argument. This is perception we're dealing with, after all, so subjectivity in the test subjects is rather to be expected, no?

      My previous statement, that frequency-domain codecs can never produce transparent audio,

      I'm not sure what you mean by this. A codec operating at what bitrate?

      If I make a codec that simply transforms between domains (hence using the same bitrate as the original signal), it's going to be transparent. Surely you're not claiming that by e.g throwing away only one bit from the entire signal, it will suddenly become non-transparent to human ears?

      "the idea that compression technology keeps on improving is a myth." -- Leonardo Chiariglione (co-founder of MPEG)

      Looking in context, it seems Chiariglione was referring to compression technology in general, while the GP was referring to implementations of codecs. He was somewhat "wrong" too, AAC has received some additions/improvements in low-bitrate applications since he wrote that.

      --
      True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
  19. Re:Hydrogen Audio ? by NetNed · · Score: 2

    Well it's better then methane audio, that just sounds like shit!

  20. Re:What? by fbjon · · Score: 2

    It's not just audio as such that can be encoded at low bitrates, more important is the audio track emdedded in a streaming video. The video is already hogging bandwidth just to look halfway decent, especially if streaming over a mobile connection, so you would want the best low-bitrate audio encoder to go with it.

    --
    True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
  21. Re:And the point of this is? by beelsebob · · Score: 2

    No, it's so they can actually tell the difference. If they used 256k/s they would reveal that there's absolutely no audible difference between the lossy and lossless samples, let alone between the various lossy ones.

  22. Re:What? by goarilla · · Score: 2

    So "who is 96kbps for?" I don't know. but "why test 96kbps?" that's easy.

    Podcasts, internet radio and other streaming media maybe ?

  23. Re:PROBLEM IS TESTERS HAVE CRAP GEAR !! by fbjon · · Score: 2

    Those schmoes don't really frequent hydrogenaudio.

    --
    True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
  24. Re:Also game soundtracks by neo8750 · · Score: 2

    the download limit for the 3gs over the 3g network is 20MB over that it must be downloaded over wifi.

  25. My experience as well. by guidryp · · Score: 2

    The low anchor encoder is pretty bad, but likewise that is the only one I can detect. Good thing it is there or I wouldn't be sure the test is working. I think all the samples are correct. They are not messing with us.

    Chalk it up to some combination of the encoders being that good and our average hearing.

    Too bad none of the guys with super hearing were brave enough to give it a shot.

  26. Re:What? by alphastar · · Score: 2

    I thought 96 kbps was "lo-quality" for internet radio and other streaming audio since at least 2004 or so...

    You've hit the nail on the head. In the old days of MP3, 96kbps was considered a "low quality" bitrate. We're now many years later, and various encoders have matured to the point where some of us feel that it's worth testing to see how they fare.