Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Codecs and settings for 64kbit/s SE listening test (Read 35118 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Codecs and settings for 64kbit/s SE listening test

As SoundExpert now has pretty stable flow of volunteer testers it is time to update codecs in all bitrate sections. After a short discussion at Russian bit-torrent tracker we decided to update 64-96-128-192-256-320 sections first. For the 64kbit/s section five codecs were chosen:

Fhg AAC (2012-06-24) - 59.2 kbit/s (fhgaacenc --vbr 2 se_ref.wav)
QAAC TVBR (v1.42) - 59.6 kbit/s (qaac --he -v56 se_ref.wav)
Nero AAC (v1.5.4.0) - 60.1 kbit/s (neroAacEnc.exe -q 0.25 -if se_ref.wav -of out.mp4)
Vorbis (Xiph 1.3.3) - 60.3 kbit/s (oggenc2.exe -q-0.3 se_ref.wav)
Opus (libopus 1.0.1) - 59.9 kbit/s (opusenc --bitrate 59 se_ref48.wav out.opus)
Conversion chain for Opus: 44.1/16 -->> 48/24(Audition CS6) -->> opusenc -->> foobar2000(48/24) -->> 44.1/16(Audition CS6)

Bitrates are calculated on the basis of nine SE test samples concatenated. Fortunately first two codecs have close values of resulting bitrates at their corresponding discrete quality settings. Other contenders were adjusted to have close values.

Did we miss something?
keeping audio clear together - soundexpert.org

Codecs and settings for 64kbit/s SE listening test

Reply #1
BTW, qaac doesn't contain a codec: it uses AAC encoder from iTunes. So probably it's better to write:
QAAC 1.42 + iTunes 10.7
or something like this.

Codecs and settings for 64kbit/s SE listening test

Reply #2
As SoundExpert now has pretty stable flow of volunteer testers it is time to update codecs in all bitrate sections. After a short discussion at Russian bit-torrent tracker we decided to update 64-96-128-192-256-320 sections first.
It's probably a very daunting task to get good results going beyond 128 kbps. Have you performed successful listening tests at high bitrates in the past?

Wouldn't it be interesting to include MP3/LAME instead of three flavours of AAC?
It's only audiophile if it's inconvenient.

Codecs and settings for 64kbit/s SE listening test

Reply #3
QAAC TVBR (v1.42) - 59.6 kbit/s (qaac --he -v56 se_ref.wav)

-v is not TVBR but CVBR. -V is TVBR and --he is not possible with it.

qaac TVBR settings:

Code: [Select]
Q0 - Q4 (0) = ~40 Kbps
Q5 - Q13 (9) = ~45 Kbps
Q14 - Q22 (18) = ~75 Kbps
Q23 - Q31 (27) = ~80 Kbps
Q32 - Q40 (36) = ~95 Kbps
Q41 - Q49 (45) = ~105 Kbps
Q50 - Q58 (54) = ~115 Kbps
Q59 - Q68 (63) = ~135 Kbps
Q69 - Q77 (73) = ~150 Kbps
Q78 - Q86 (82) = ~165 Kbps
Q87 - Q95 (91) = ~195 Kbps
Q96 - Q104 (100) = ~225 Kbps
Q105 - Q113 (109) = ~255 Kbps
Q114 - Q122 (118) = ~285 Kbps
Q123 - Q127 (127) = ~320 Kbps


BTW, qaac doesn't contain a codec: it uses AAC encoder from iTunes. So probably it's better to write:
QAAC 1.42 + iTunes 10.7
or something like this.

Even better if he adds the CoreAudioToolbox.dll version he's using it (7.9.7.9, 7.9.8.1 etc.).

Codecs and settings for 64kbit/s SE listening test

Reply #4
It's probably a very daunting task to get good results going beyond 128 kbps. Have you performed successful listening tests at high bitrates in the past?

Quote
Ratings above 5-th grade mean that the devices/technologies have some quality headroom, their artifacts are beyond threshold of human audibility. Testing files of such devices are processed additionally - sound artifacts are amplified to the extent when they could be heard by ordinary listeners.

(from soundexpert.org, emphasis mine)

Codecs and settings for 64kbit/s SE listening test

Reply #5
It's probably a very daunting task to get good results going beyond 128 kbps. Have you performed successful listening tests at high bitrates in the past?

Quote
Ratings above 5-th grade mean that the devices/technologies have some quality headroom, their artifacts are beyond threshold of human audibility. Testing files of such devices are processed additionally - sound artifacts are amplified to the extent when they could be heard by ordinary listeners.

(from soundexpert.org, emphasis mine)
How do you algorithmically selectively amplify artifacts, other than modifying the encoders to work worse than they'd normally would?
It's only audiophile if it's inconvenient.

Codecs and settings for 64kbit/s SE listening test

Reply #6
How do you algorithmically selectively amplify artifacts, other than modifying the encoders to work worse than they'd normally would?


IIRC they subtract the encoded signal from the lossless input and then do some kind of processing on it and then add it back to "enhance" artifacts.  The end result is that the encoded files are easier to distinguish from lossless, but OTOH I don't think anyone has ever shown that the differences correlate with actual audio quality.

Codecs and settings for 64kbit/s SE listening test

Reply #7
QAAC TVBR (v1.42) - 59.6 kbit/s (qaac --he -v56 se_ref.wav)

-v is not TVBR but CVBR. -V is TVBR and --he is not possible with it.

accepted, thanks; for 64kbit/s I think HE-AAC is more appropriate setting for this codec. True VBR will be used at higher bitrates.

BTW, qaac doesn't contain a codec: it uses AAC encoder from iTunes. So probably it's better to write:
QAAC 1.42 + iTunes 10.7
or something like this.

Even better if he adds the CoreAudioToolbox.dll version he's using it (7.9.7.9, 7.9.8.1 etc.).

QAAC 1.42 + iTunes 10.7.0.21 (CoreAudioToolbox.dll 7.9.7.3)
This CoreAudioToolbox looks outdated but iTunes and QuickTime are the latest on my system. Is it important to have the latest version of the file?
keeping audio clear together - soundexpert.org

Codecs and settings for 64kbit/s SE listening test

Reply #8
Wouldn't it be interesting to include MP3/LAME instead of three flavours of AAC?

I think 64 is too low for mp3, result is too predictable and the usage scenario is too uncommon.
keeping audio clear together - soundexpert.org

Codecs and settings for 64kbit/s SE listening test

Reply #9
Sounds like a useless test to me. There is nothing to be gained by exposing otherwise inaudible artifacts. These codecs make decisions based on the fact the artifacts this test seeks to expose would be inaudible.

As for including mp3, it's still the most popular codec, and it would be useful to see the bitrate at which mp3 gains parity with the test cases.

Codecs and settings for 64kbit/s SE listening test

Reply #10
Sounds like a useless test to me. There is nothing to be gained by exposing otherwise inaudible artifacts. These codecs make decisions based on the fact the artifacts this test seeks to expose would be inaudible.

Below 128kbit/s artifact amplification is not applied. Outputs of codecs are used as is.
keeping audio clear together - soundexpert.org

Codecs and settings for 64kbit/s SE listening test

Reply #11
As for including mp3, it's still the most popular codec, and it would be useful to see the bitrate at which mp3 gains parity with the test cases.

Preliminary decision was to start testing of mp3 from 96kbit/s, should we really begin with 64kbit/s? There are a lot of outdated mp3 codecs in this section already, btw.
keeping audio clear together - soundexpert.org

Codecs and settings for 64kbit/s SE listening test

Reply #12
Below 128kbit/s artifact amplification is not applied. Outputs of codecs are used as is.


The fact remains I question doing it above 128kbps.. Amplifying inaudible artifacts to the point they become audible SERVES NO PURPOSE. You can't judge the quality of a lossy codec that way. The whole exercise will do nothing but provide misleading reference material which nimrods will use to base inaccurate claims that some codec is better or worse than another because of the INAUDIBLE artifacts this test needlessly exposes.

Each codec should be included in all test samples. If for no other reason than to illustrate how badly mp3 works at those low bit rates compared to the more modern ones.

If every codec other than mp3 becomes transparent at 128kbps then let your study confirm that so that it adds even more to the mountain of evidence that above those bitrates you can use any codec you like with no audible problems, and that mp3 sucks. 

Codecs and settings for 64kbit/s SE listening test

Reply #13
The fact remains I question doing it above 128kbps.. Amplifying inaudible artifacts to the point they become audible SERVES NO PURPOSE. You can't judge the quality of a lossy codec that way. The whole exercise will do nothing but provide misleading reference material which nimrods will use to base inaccurate claims that some codec is better or worse than another because of the INAUDIBLE artifacts this test needlessly exposes.

Please not here, there is more appropriate place for the discussion - http://www.hydrogenaudio.org/forums/index....=85182&st=0

Each codec should be included in all test samples. If for no other reason than to illustrate how badly mp3 works at those low bit rates compared to the more modern ones.

I'm not sure there is a need to prove shortcomings of mp3 at low bitrates over and over again.
keeping audio clear together - soundexpert.org

Codecs and settings for 64kbit/s SE listening test

Reply #14
The fact remains I question doing it above 128kbps.. Amplifying inaudible artifacts to the point they become audible SERVES NO PURPOSE. You can't judge the quality of a lossy codec that way. The whole exercise will do nothing but provide misleading reference material which nimrods will use to base inaccurate claims that some codec is better or worse than another because of the INAUDIBLE artifacts this test needlessly exposes.

Please not here, there is more appropriate place for the discussion - http://www.hydrogenaudio.org/forums/index....=85182&st=0
While the concerns with the basic premise have not been addressed as far as I can tell, this is the thread you asked for input and comments in this thread, so let's stick with this one instead of reviving the old one.

Each codec should be included in all test samples. If for no other reason than to illustrate how badly mp3 works at those low bit rates compared to the more modern ones.

I'm not sure there is a need to prove shortcomings of mp3 at low bitrates over and over again.
I'm on the other hand not sure if there is any need to prove "shortcomings" of lossy encoders by trying to inflate certain, previously inaudible, artifacts in a listening test. How do you make sure thise method doesn't artificially bias towards certain encoders/artifacts? If you want to prove that lossy encodes differ form the original, you're done now, since they obviously do and have to. Another useful metric to me is the binary issue of transparency. Either the (unaltered!) encoder result is transparent or it isn't. In the real world you'll never have weird mixes where you superimpose difference signals onto the encoded signal. This method is completely artificial with no real world application or meaning. Another thing done regularly here are the ABC tests, but those are mainly useful to grade encoders on results with obvious audible flaws, to decide which encoder produces the less annoying results.
It's only audiophile if it's inconvenient.

Codecs and settings for 64kbit/s SE listening test

Reply #15
I'm on the other hand not sure if there is any need to prove "shortcomings" of lossy encoders by trying to inflate certain, previously inaudible, artifacts in a listening test.

At 64kbit/s there is no need for artifacts amplification for sure. Above 128kbit/s meaningful results of ABX testing become more and more expensive (but still meaningful). SoundExpert proposes methodology that makes those tests less expensive. SE quality ratings of devices with small impairments could be considered as results of specially simplified listening tests. Results are experimental which is clearly stated on the site.
keeping audio clear together - soundexpert.org

Codecs and settings for 64kbit/s SE listening test

Reply #16
What I would like to see one day is more CVBR tests. All the previous listening test I have seen were more concerned about offline storage than streaming.

Codecs and settings for 64kbit/s SE listening test

Reply #17
How do you make sure thise method doesn't artificially bias towards certain encoders/artifacts? If you want to prove that lossy encodes differ form the original, you're done now, since they obviously do and have to. Another useful metric to me is the binary issue of transparency. Either the (unaltered!) encoder result is transparent or it isn't. In the real world you'll never have weird mixes where you superimpose difference signals onto the encoded signal. This method is completely artificial with no real world application or meaning.


To add to this point, I notice that the newer version of the site no longer ranks SBR codecs above non-SBR codecs, presumably due to some adjustment of the 'enhancement' process to give less obviously incorrect results?

Codecs and settings for 64kbit/s SE listening test

Reply #18
What I would like to see one day is more CVBR tests. All the previous listening test I have seen were more concerned about offline storage than streaming.

All AAC contenders for this 64kbit/s testing are in CVBR mode.
keeping audio clear together - soundexpert.org

Codecs and settings for 64kbit/s SE listening test

Reply #19
How do you make sure thise method doesn't artificially bias towards certain encoders/artifacts? If you want to prove that lossy encodes differ form the original, you're done now, since they obviously do and have to. Another useful metric to me is the binary issue of transparency. Either the (unaltered!) encoder result is transparent or it isn't. In the real world you'll never have weird mixes where you superimpose difference signals onto the encoded signal. This method is completely artificial with no real world application or meaning.


To add to this point, I notice that the newer version of the site no longer ranks SBR codecs above non-SBR codecs, presumably due to some adjustment of the 'enhancement' process to give less obviously incorrect results?

The only adjustment that was brought into operation last year is post-screening of incoming grades. The reason of instability of high bit-rate ratings (320+) is insufficient number of testing points and the problem still needs some research. Another SBR codec in 192 section never showed higher results.
keeping audio clear together - soundexpert.org

Codecs and settings for 64kbit/s SE listening test

Reply #20
At 64kbit/s there is no need for artifacts amplification for sure. Above 128kbit/s meaningful results of ABX testing become more and more expensive (but still meaningful). SoundExpert proposes methodology that makes those tests less expensive. SE quality ratings of devices with small impairments could be considered as results of specially simplified listening tests. Results are experimental which is clearly stated on the site.


If meaningful results of ABX tests above 128kbps become more and more expensive it's because the codecs are doing their jobs and producing audibly transparent output. At a point where normal ABX results become statistically insignificant then transparency has been reached and we're done. Artificially altering encoder output to highlight normally inaudible artifacts of the encoding process and then trying to assign a quality to a codec based on those artificially accentuated normally inaudible artifacts is a USELSS process. It has no application in the real world, it means nothing, and the results obtained from such "tests" are useless noise and best ignored.

You might as well subtract the lossy output from the original, post the spectrograms, and start running around screaming the sky is falling and vinyl is better than digital..

Codecs and settings for 64kbit/s SE listening test

Reply #21
In short, you need to understand what lossy audio/video encoding tries to achieve. It aims to produce audibly/visibly artifact-free files, and not generally artifact-free files. That is what lossless compression is for.
It's only audiophile if it's inconvenient.

Codecs and settings for 64kbit/s SE listening test

Reply #22
Quote
All AAC contenders for this 64kbit/s testing are in CVBR mode.

Can we also use Vorbis and Opus at CVBR rates?

Lets say we have Codec X and Y
X we do at VBR. With some difficult songs X jumps to 82Kbps for some sections. It is okay for offline, because the average might be around 67Kbit/s for all the songs encoded.
Y we do at CVBR. It stays at +/- 64Kbps.
If Codec X won the listening test people might think X is also better than Y when it comes to streaming (Like internet radio stations). This might not be the case, because the X simply used more bits with difficult sections.

Codecs and settings for 64kbit/s SE listening test

Reply #23
How about, can we have a test worth performing?

If AAC, Vorbis, Opus, and MP3 are all statistically transparent at a given nominal bit rate then they are all audibly the SAME QUALITY at that bit rate. No one codec offers any audible benefit over the others at that point. There is nothing to gain in claiming to judge codec quality by adding distortion to their output and pretending it somehow matters in the real world.

I'm honestly not sure why this thread hasn't been locked/removed. It smells of snake oil and pixie dust, or at the least is ill-conceived. These "tests" of adulterated codec outputs offer us no relevant results on which to base any kind of rational discussion or decisions, other than how NOT to conduct a codec quality test.  It can only serve to spread disinformation and ignorance. IMO it has no place on HA.

Codecs and settings for 64kbit/s SE listening test

Reply #24
This argument is nothing new here (I too am skeptical about the relevance of SE tests).  So long as TOS #8 or any other rule isn't being violated, the discussion can stand.

I was tempted to ask people to refrain from this line of conversation, but Serge did solicit criticism.  I also think those who aren't familiar with SE should be aware that results from SE are not exactly in keeping with the spirit of this forum.