Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
BUG: Normalize item(s) to Peak RMS #851
See this post:
Sometimes for no apparent reason an item will normalize to an insanely loud level even though it's more or less just like all the other items in a group that were normalized.
Can you look into what might cause this?
Hi Tim, I didn't realize you were in Madison. In the morning I'll revisit this session and try to reproduce. If I can do that I'll pass the files along to you. Thanks, Justin…
On Mar 28, 2017, at 10:19 PM, Tim ***@***.***> wrote: If you have an example RPP of this going bad it would be super helpful. (PS hey from down the road in Madison) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
OK, sorry for the large zip file but I wanted to get you the RPP file and all the source audio files. Also, ignore the terrible song titles for this project. It's not mine, just something I mastered recently for a client.
Here is the zip file you'll need:
(At this time it still has 20 minutes to finish uploading)
The zip file contains my REAPER configuration, the original WAV files for the project (32-bit FP/96k), a folder of two screen shots (before and after I run my custom action containing the RMS normalize action), and then the folder with two RPP projects, one before the custom action is run, and one after. The Audio Files folder in the REAPER project folder is meant to be empty because it's pulling the audio files from that "original files folder".
As you'll see if you load my REAPER configuration, I have a custom action that does a few things by pressing F13. One of those things is the "Normalize item(s) to Peak RMS" action.
As mentioned, now and then I'll have a project where an item gets normalized by an insane amount. In this project, the item named "Asshole_24bit_96k.wav" gets boosted by 72.1dB. The file itself is actually a 32-bit/96k WAV but the original file came is as 24-bit/44.1k so that why it has that confusing name. It appears to be just a normal WAV file like all the rest but something causes an incorrect normalization.
I see this happen now and then and I'm not sure why certain files trigger such a bizarre normalization level.