Help - Search - Members - Calendar
Full Version: Noise Responsiveness Test on (Ogg, NeroAAC, Mp3, Mpc)
Hydrogenaudio Forums > Hydrogenaudio Forum > Listening Tests
Fileburner
First of all I am not a professional in audio technologies I am just an audiophile who is very strict when it comes to audio quality tongue.gif, so this test might be wrong, the purpose of this test is just to make readers aware about some encoders behavior about noise responsiveness.

The other day I did a test on a wav track which contains some noise effects, the purpose of this test is to determine Noise responsiveness and quality on mainstream audio formats
Test Date : 2009/10/10
Source Format : Wav 44.1kHz Stereo 1411Kbps PCM.
Target Format : Ogg, Mp3, Mpc, AAC.
Settings : default settings of each encoder.
Testing hardware : Sony TwinTurbo Earphones on Realtek HD Audio card (output format : 24bit).
Testing Software : Foobar2k 0.9.6.4 (Encoding and listening) Enabled plugins : Equalizer + vLevel.



From the resulted bit rates it shows the weird responsiveness of Nero AAC and Musepack to noise with Nero AAC being the worst unlike Ogg and Mp3 which responded well and gave a very nice noise quality.
to make sound distinguishable I used Foobar's built-in Equalizer to clarify the sound on each format. equalizer setting file is attached with this post.
it is recommended to use vLevel to be able to hear the noise clearly in all files
Archive contents : Original Wav File + Equalizer setting + 4 encoded Audio files.
best regards.

Archive

Critics or comments are welcome
Tahnru
Perhaps look into ABC/HR and run the test again.

http://wiki.hydrogenaudio.org/index.php?title=ABC/HR
Fileburner
My scoring was according to the scoring noted in the link you provided, NeroAAC and MPC are realy annoying with MPC being better than NAAC
if you mean ABX testing I can easily identify the MPC and NeroAAC encoded track in the first Seconde of the track

Thank you.
Fileburner
I run again the test for MPC and NAAC at Q6 and Q7
MPC showed better responsiveness at Q6 and Q7 124kbps 171kbps respectively but NAAC still have quality degradation even at higher quality

Thank you.
Light-Fire
QUOTE (Fileburner @ Oct 16 2009, 18:10) *
...if you mean ABX testing I can easily identify the MPC and NeroAAC encoded track in the first Seconde of the track

Thank you.


I am just curious. At what bit rate do you stop perceiving the difference between lossy and lossless?
Fileburner
the used track is just 2s length of noise, so the bitrate is almost the same (very low) for nero and MPC
MPC :
CODE
foo_abx 1.3.3 report
foobar2000 v0.9.6.4
2009/10/17 01:35:02

File A: Noise_Test.mpc
File B: Noise_Test.wav

01:35:02 : Test started.
01:35:12 : 01/01  50.0%
01:35:21 : 02/02  25.0%
01:35:28 : 03/03  12.5%
01:35:37 : 04/04  6.3%
01:35:44 : 05/05  3.1%
01:35:52 : 06/06  1.6%
01:35:59 : 07/07  0.8%
01:36:06 : 08/08  0.4%
01:36:12 : 09/09  0.2%
01:36:19 : 10/10  0.1%
01:36:26 : 11/11  0.0%
01:36:33 : 12/12  0.0%
01:36:39 : 13/13  0.0%
01:36:46 : 14/14  0.0%
01:36:53 : 15/15  0.0%
01:37:00 : 16/16  0.0%
01:37:07 : 17/17  0.0%
01:37:13 : 18/18  0.0%
01:37:23 : 19/19  0.0%
01:37:30 : 20/20  0.0%
01:37:35 : Test finished.

----------
Total: 20/20 (0.0%)

NAAC :
CODE
foo_abx 1.3.3 report
foobar2000 v0.9.6.4
2009/10/17 01:38:43

File A: Noise_Test.mp4
File B: Noise_Test.wav

01:38:43 : Test started.
01:38:50 : 01/01  50.0%
01:38:56 : 02/02  25.0%
01:39:02 : 03/03  12.5%
01:39:08 : 04/04  6.3%
01:39:20 : 05/05  3.1%
01:39:26 : 06/06  1.6%
01:39:31 : 07/07  0.8%
01:39:36 : 08/08  0.4%
01:39:41 : 09/09  0.2%
01:39:46 : 10/10  0.1%
01:39:51 : 11/11  0.0%
01:39:57 : 12/12  0.0%
01:40:06 : 13/13  0.0%
01:40:09 : 14/14  0.0%
01:40:12 : 15/15  0.0%
01:40:14 : 16/16  0.0%
01:40:18 : 17/17  0.0%
01:40:20 : 18/18  0.0%
01:40:23 : 19/19  0.0%
01:40:26 : 20/20  0.0%
01:40:28 : Test finished.

----------
Total: 20/20 (0.0%)

as stated above, ~120kbps seem to give good noise quality.
Tahnru
QUOTE
if you mean ABX testing I can easily identify the MPC and NeroAAC encoded track in the first Seconde of the track


No, you've missed the point I think. Let's review:

ABX testing, in an audio context, provides evidence as to whether or not an audible difference exists.
ABC/HR testing also provides evidence as to the audibility of a difference, and ALSO (important point here) provides a blind way of measuring perceived quality.

An ABC/HR test is the appropriate way to measure quality difference between several lossy samples. ABX and sighted tests are not. I recommended you re-conduct the test using this tool because, properly done, it will strengthen the usefulness of your results. And it's good practice to use the appropriate test and tools for a given experiment.
Axon
You've got one hell of a smiley-face going on with your eq. -6db to +11db? What makes you think this is valid eq setting for real listening situations? Such a configuration just seems like it is defeating the equal-loudness curve, which all encoders rely upon. So even if your results are confirmed by ABX testing, they may not apply to anybody who does not have as vastly a poor of a frequency response as what this test utilizes.

Why is vlevel necessary?

Besides that... I tend to support this general kind of listening, insofar as codecs ought to be configured so that they allow for transparency under any kind of linear distortion operation (such as eq and to a lesser extend dynamic range compression). But it is highly unlikely that can be achievable at these sorts of bitrates. After all, it's dangerously close to perceptual transparency in the first place.
Fileburner
QUOTE (Tahnru @ Oct 17 2009, 03:26) *
An ABC/HR test is the appropriate way to measure quality difference between several lossy samples. ABX and sighted tests are not. I recommended you re-conduct the test using this tool because, properly done, it will strengthen the usefulness of your results. And it's good practice to use the appropriate test and tools for a given experiment.

can you please tell or point me to a link on how to conduct this test because the link you gave me above does not discribe the way of testing.

Thank you.
QUOTE (Axon @ Oct 17 2009, 04:06) *
You've got one hell of a smiley-face going on with your eq. -6db to +11db? What makes you think this is valid eq setting for real listening situations? Such a configuration just seems like it is defeating the equal-loudness curve, which all encoders rely upon. So even if your results are confirmed by ABX testing, they may not apply to anybody who does not have as vastly a poor of a frequency response as what this test utilizes.

at least it's my favourite setting tongue.gif.
the audio file was encoded to different format directly without using any DSP plugin, but while listening I used Equaliser and vLevel to amplify the noise and make it clearer.
Thank you.
pdq
If you listen with a lot of equalization then the proper way to do lossy compression is to apply the equalization first, then encode it. That is the only way that the encoder can rationally determine what will be audible and what won't.
Fileburner
what surprises me in this test, is why NeroAAC and MPC behave differently to Lame and Ogg in same circumstances, regardless of filters.
does NAAC and MPC ignore Noise purposely ?
sld
Isn't it supposed to be a good thing that noise isn't given much bits?
Fileburner
I think sometimes noise should be kept as is, no ? I think it's quality problem here not bit rate problem
thank you
sld
Why should noise be kept, or not kept, as is? What's the rationale?
Fileburner
what if noise is put on purpose on an audio track, should it be neglected because noise is mostly neglected ?
IMO when encoding to a given quality level everything should be encoded at this level whether it's noise or anything else <-- Just an opinion
lvqcl
This noise is inaudible at normat listening conditions. So there's no need to keep it.
Lossy encoders don't assume heavy postprocessing of encoded files.
Fileburner
it's seems that NAAC ignores signals at a low level
I tried to encode the same wav file but these time by applying vLevel filter at encode time
result is : better responsiveness with 201kbps rate
sld
You mean you originally encoded noise at a very low level and then wondered why the encoders weren't keeping them? unsure.gif
After you increased the volume of the wav and encoded it, you found that the encoder exhibited normal behaviour? Gosh. This seems to show that Nero AAC and Musepack are better than the Vorbis and LAME encoders you used.
Fileburner
1 - Musepack showed responsiveness to noise at Q7 but NeroAAC didn't at Q7
2 - NAAC showed responsiveness but only after normalizing the sound (vLevel Filter)

In my opinion signals shouldn't be ignored or given low bitrate whether they are low level or noise, everything should be encoded according to the given quality setting. But I might be wrong wink.gif

Thank you.
sld
Your points 1 and 2 indicate to me that Nero AAC is actually more advanced than Musepack, LAME and Vorbis... part of the job description of an efficient lossy encoder. If it can't be normally heard, it doesn't need to be encoded. Then again, we've been so used to Replaygain values that are negative that I wonder if encoders are already able to deal with samples that eventually require highly positive RG values. Without further information from the various codec developers, we won't know for sure.

And if we don't know for sure, we'll be foolish to present our opinions as facts.
Aoyumi
These results are differences of the designs (or/and tunings) of the encoders basically.

The libvorbis(include aoTuV) assumes that sound of the small volume is played at big volume .
Since an encoder cannot prescribe play volume beforehand, I think this supposition to be be a necessary thing.
However, the behavior may be superabundant in 16bit source.
Fileburner
Thank you very much for your comments, I was able to understand many things from this topic
Thank you.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.