Here is a situation. I just mixed a new track. Set the audio volume to -0.01bd with a limiter. Bounced the track from Cakewalk down to a wave file. The wave file is not clipping because of the limiter. Now it is time create the MP3 file.
LAME is the most popular MP3 software used by Napster, Amazon….. and is free. I use it to convert a WAVE file into an MP3 file. So I run the command line prompt like:
Notice the ClipDetect option. In several case I have noticed that despite having created a wave file that is not clipping. Lame has detected a volume above -0.01db which is clipping. So I fix that problem with --scale 0.99 or what ever Lame suggests.
Now I have a MP3 song that is not clipping according to Lame. But I am just thinking that each audio playback software is different and may detect a clip instance even though a new LIMITER has been put on the MP3 file.
So my questions are:
1) Should I bounce the wave file down to some thing less than -0.01db then see what LAME say about clipping? Or is it safe to get right on the clipping edge? 2) When clipping is detected what is lost? 3) Do you lose on the vocal or instrumental side or both?
The measurements you're posting probably aren't producing any audible clipping effect. Personally I don't get crazy over clipping unless I can hear it. And I think it's obvious that today's record industry doesn't give a shite about it, with all the distortion we hear in so much of what's printed for mainstream consumption.
Sounds like you're safe to me, as long as you're not constantly clipping. And bringing down your levels to -0.01dB is great.
I use LAME as well. Can't say I'm always happy with it but it beats the heck out of some of the other hack app's out there that mangle your bits.
The main concern is also does clipping or having to use --scale 0.99.... or what ever LAME suggest in the event of a clip cause a lost of vocals, instruments or both?
RSS Feed
Posted - 01/08/2012 : 5:54:36 PM
