Or if you have a truly-clipped file you can reduce the volume so the peaks are below 0dB (which of course doesn’t fix the clipped wave shape) and Audacity won’t show it as clipped. It’s just looking for samples over 0dB, or a few 0dB samples in a row. Audacity isn’t looking at the wave shape. ![]() Regular WAV files, audio CDs, digital-to-analog converters (playback) and analog-to-digital converters (recording) all all hard-limited to 0dB and they will clip if you try to go over.Īudacity shows potential clipping (red). In that case, the actual audio will only be clipped if you feed it to your digital-to-analog converter at (or near) full-digital volume. MP3 can go over 0dB without clipping so your file might not really be clipped. The 89dB default is a compromise that works with more files. If you make it lower, MP3Gain has “more room to work” and fewer files will clip. If you make the target loudness higher you are more likely to clip (or find more files that can’t hit the target without clipping). That won’t change when you normalize because the ratio between loudness and peak doesn’t change. If you don’t allow clipping it will only adjust it as much as it can. The other two clip(Track) and clip(Album) are just warning you of clipping if you adjust to the target loudness. But it usually only peaks about 1dB higher. If you normalize to 0dB and export as MP3, the MP3 peaks may go over 0dB and if you re-import the MP3 Audacity may “show red”. ![]() …MP3 is lossy so it does change the wave shape and some peaks often get higher. That shouldn’t show clipping if you’ve normalized to -3 or -6dB. I have just tried it from the original file to -6dB, and MP3Gain gives the same clipping levels, between 4 and 6dB too highĬlipping tells you if it currently goes over 0dB.
0 Comments
Leave a Reply. |