foo_abx v1.2 report
foobar2000 v0.8.3
2004/11/23 17:27:59

File A: file://C:\001 Copy of 001 Enola_Gay adjusted.wav
File B: file://C:\001 001 Enola_Gay.wav

17:27:59 : Test started.
17:29:30 : 01/01  50.0%
17:29:41 : 02/02  25.0%
17:30:06 : 03/03  12.5%
17:30:31 : 04/04  6.3%
17:30:37 : 05/05  3.1%
17:30:47 : 06/06  1.6%
17:30:56 : 07/07  0.8%
17:31:03 : 08/08  0.4%
17:31:04 : Test finished.

 ---------- 
Total: 8/8 (0.4%)

Also... after having previously used MP3Trim to adjust some of my albums in the past, I had noticed that its "0" db target reference corresponded almost exactly to a 98db target value in MP3Gain! Why such a huge discrepancies between the two application’s target values? I specifically remember writing to both authors at the time to find out but never received a reply from either ones.

Well thanks for taking the time to steer me in the right direction anyway.  I'll be correcting the information I have posted on my site soon.
[a href="index.php?act=findpost&pid=255881"][{POST_SNAPBACK}][/a]

Result! btw, (as I think I said before I knew you were reading) your software looks very cool.
[a href="index.php?act=findpost&pid=255894"][{POST_SNAPBACK}][/a]

You should note that the default value in MP3Gain comes preset at 89 db, and that choosing a much higher value such as 98 db will show some form of track clipping inside MP3Gain.
I should also mention that I have recently seen and heard proof that in some instances, this resulting clipping will be audible so I am  now recommending a more conservative value of  92 db as the target "normal" value.  If this value still introduces clipping inside MP3Gain, then by all mean use the recommended default value of 89 db or even lower. 

The tradeoff of having to use such a low value in order to completely alleviate clipping is that the resulting mp3 will likely have a much lower sound level compared to exact same CD track.

Quote

Result! btw, (as I think I said before I knew you were reading) your software looks very cool.
[a href="index.php?act=findpost&pid=255894"][{POST_SNAPBACK}][/a]

Thanks, I am also trying to make it fb2k compatible in the future but this might be tougher than anticipated. 
I have a few commands that are working fine with winamp 2.x but have not yet managed to duplicate in foobar.  Specifically the ones dealing with the playlist.

I've posted in fb2k development forum looking for some feedback so I'll be checking that next! 

Again, thanks for the info you've provided!


Andre
[a href="index.php?act=findpost&pid=255969"][{POST_SNAPBACK}][/a]

Quote

Quote

Yes, by Mp3Gain you can repair the clipping that was introduced by encoding...

Yes, it seems that Mp3Gain is doing a great job.
But don't I lose information when clipping is introduced by encoding?
If I lose data, can Mp3Gain really undo it?
I've read the Mp3gain FAQ, can't find the answer there. In fact I hope I'm wrong, and no info is lost. But I want to be sure.
[{POST_SNAPBACK}][/a]

I was surprised that, in five minutes, I couldn't find the answer to this on-line either. It must have been answered many times, but it may be quicker to answer again than to keep searching!

If something is "clipped" it means that the sample value is (or should be) above digital full scale - but gets "clipped" to exactly digital full scale, because there are no larger numbers available to represent the true value.

The mp3 encoded version is clipping because the original CD had sample values were very near, or equal to, digital full scale. Mp3 encoding changes the waveform slightly - so that (often as not) these nearly clipped samples get pushed slightly higher, into clipping.

The reason you can recover these samples is because mp3 files can store values greater than digital full scale. So, they've been pushed up out of the range the mp3 decoder or player can handle, but they're still in the mp3 file. If you can adjust the volume down slightly before you play the file back, everything will come out fine, because the values will be decoded into the range below digital full scale = no clipping.


If mp3 encoding only pushed the values slightly higher, it probably wouldn't be worth worrying about this, but some circumstances cause peak values to increase dramatically - it's not a fault, just a fact of life - there's more about it here:

[a href="http://www.ff123.net/norm.html]http://www.ff123.net/norm.html[/url]


To prove to yourself that what I'm suggesting is happening is happening, try this:

1. Take a file (preferably a nice quiet file) and mp3gain it to some stupid amount (110dB or something).
2. Listen to it - it should sound awful - it'll be full of clipping.
3. mp3gain it back down to, say, 89dB.
4. Listen to it again - the clipping has gone. It was only temporary.

Obviously mp3gain can't do anything about clipping which was present in the original source (e.g. CD).

Cheers,
David.
[a href="index.php?act=findpost&pid=255439"][{POST_SNAPBACK}][/a]

The only real danger lies in applying Max No-clip Gain for Each File, which is rarely a wise thing to do

Madrigal: "The only real danger lies in applying Max No-clip Gain for Each File, which is rarely a wise thing to do."
Why is that dangerous? it sounds like the best thing to do, cos i want each file to play as loud as possible without clipping.
[a href="index.php?act=findpost&pid=257168"][{POST_SNAPBACK}][/a]