here is a thread i found on normalizing vs compression:
http://homerecording.com/bbs/showthread.php?t=37683
[QUOTE]Normalization finds the highest peak in your track and raises that to whatever setting you are normalizing to (usually 0 db). It also raises the rest of the track by the same amount. So, for example, if the highest peak in your track is -2db, normalizing to 0db will raise everything in the track by 2db. If you normalize to 0db (or something less, like -0.3db) you should not be getting any “red lights”, since by default all material will be below that point.
Compression, on the other hand, squashes (compresses) your peaks, and reduces the dynamic range of the material (the difference between the lows and the highs). How much of a reduction will depend on the threshold setting (where the comrpession kicks in) and the amount of compression you use. Doing this generally allows you to raise the overall volume of the track more than you can do by just normalizing (since your peaks are now lower, you have more room to go up). Using the example above, if your highest peak is -2db, you might be able to knock that down to say -6db by compressing the track, then you can apply 6db gain to bring the peak back up to 0db. So your track volume has been increased by 6db, as opposed to the 2db that normalizing would have given you.[/QUOTE]
here is another one:
http://www.gearslutz.com/board/so-much-gear-so-little-time/346395-normalize-compress-get-consistent-levels.html
this one talks about when and why normalizing can be used and also why sound engineers don’t like it.
here is a good thread too with this quote:
[QUOTE]" you look at normalizing as the process of making your loudest peak, your loudest possible peak, then it isn’t really useful. But if you look at normalizing as setting a level, and then all audio gets turned down and/or up to match that level then it can be really useful in certain situations, especially if you can not only normalize by peak value, but by RMS as well.
A good example of RMS normalization is Dolby decoding. Every piece of audio encoded with dolby has a “dialnorm” metadata tag. This tag tells the decoder what the average RMS level of the material is. The decoder then adjusts the output volume to match your current output levels, basically eliminating the need for “volume wars”. Ever notice how TV commercials are insanely loud compared to a movie you might be watching on cable? If you run your cable through your audio receiver that has a dolby decoder instead of plugging straight into the TV (and the audio from the station is dolby encoded) , then the commercials will playback through your system at the same level as the movie you were watching.
Another very handy use for normalization is when putting together a library of sounds or sound effects. You recorded them all, but there might be slight variations in volume from day to day… so instead of making them all as loud as possible, you set the normalizer to a median level, that way the few that were a hair too loud get brought down and the few that were a hair too soft get brought up. This way you still maintain the dynamic range and low noise floor that you originally recorded, but have slightly adjusted the files so they are all the same average level.
[/QUOTE]
http://duc.digidesign.com/showthread.php?t=236798
the last use is what’s its being used for one samplers.
we are all trying to help but there are so many things that could be affecting the audio in question. It maybe as simple as needing volume leveling something like mediamonkey can do where all your tracks are brought up or down to the same level.
good luck
edit, not trying to come out blasting with all these links, just sharing this info, not trying to booster my side’s argument or anything…there is a right way and a wrong way do use most of this stuff.