RMS normalization in Sound Forge also causes clipping. I always do peak normalization. I do find that using the Statistics function under Tools, and checking RMS level, can be very helpful in matching apparent loudness from one track to the next.


-----Original Message-----
From: Association for Recorded Sound Discussion List [mailto:[log in to unmask]] On Behalf Of Mickey Clark
Sent: Friday, September 21, 2018 1:40 PM
To: [log in to unmask]
Subject: Re: [ARSCLIST] Normalization Question

Hello-I found that RMS  in Nero would create clipping - setting to maximum 
is preferred-Mickey

-----Original Message----- 
From: David Seubert
Sent: Friday, September 21, 2018 9:39 AM
To: [log in to unmask]
Subject: [ARSCLIST] Normalization Question

UCSB is digitizing Edison Diamond Discs from the teens and 1920s and
putting them online in DAHR. We are normalizing access files using EBU
R-128 to -16 LUFS. When we do this manually in Wavelab it sounds great.
When we batch process using ffmpeg (double pass), files with certain noise
profiles come out sounding terrible, full of volume pumping. RMS
normalization in ffmpeg works fine. Questions are, does EBU R-128 not work
well with noisy content? Why does the normalizer in Wavelab work so much
better than ffmpeg? And finally, is there any reason not to just use RMS
normalization? Our workflow is automated, so using Wavelab isn't an option.

I can probably share files if anybody want to hear.


David Seubert