![]() ![]() If, for instance, you are going to create an MP3 file from your final edited version, then it's best to normalise the signal to about -1 or even -2dB before doing so, as encoding has been known to put additional peaks into the output, and the results simply don't sound as 'clean' as they would with a slightly lower level signal to start with. This is the one that is slightly more subtle. ![]() The second use of it concerns the final peak value you set a file to before encoding it to a lossy format. So if you are going to use anything like a limiter or compressor, it means that when you set the threshold level it isn't arbitrary any more, which it would be if the audio was at some other level - you really wouldn't be able to tell what the true effect of the change you made had been. It has two primary purposes: the first is that it sets any signal so that its peak reaches the level that all of the dynamics-based processing is designed to be referenced to - in other words, 0dB. It moves everything proportionally to the value you set, and the results will sound identical. Normalization doesn't alter anything about your file at all other than the overall level of it. ![]() So normalizing to a low value, apart from being pointless, isn't a good idea anyway. If you are processing a 32-bit file, you can normalize to a really low value if you want, and then restore the signal to a more sensible level without loss, but if you do this with an integer-based (8 or 16-bit) signal and save the result before restoring it, you will raise the noise floor in your file irreversibly. You've always been able to do this either as a percentage or a rather more useful dB value it's never been set to any arbitrary value. All normalization does is set the highest peak in a file to a signal level you set. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |