New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Normalize item(s) to Peak RMS #851

Closed
JustinPerkinsMKE opened this Issue Mar 28, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@JustinPerkinsMKE

See this post:

http://forum.cockos.com/showpost.php?p=1797923&postcount=38

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?

screen shot 2017-02-06 at 9 46 09 am

@swstim

This comment has been minimized.

Show comment
Hide comment
@swstim

swstim Mar 29, 2017

Member

If you have an example RPP of this going bad it would be super helpful. (PS hey from down the road in Madison)

Member

swstim commented Mar 29, 2017

If you have an example RPP of this going bad it would be super helpful. (PS hey from down the road in Madison)

@JustinPerkinsMKE

This comment has been minimized.

Show comment
Hide comment
@JustinPerkinsMKE

JustinPerkinsMKE Mar 29, 2017

@JustinPerkinsMKE

This comment has been minimized.

Show comment
Hide comment
@JustinPerkinsMKE

JustinPerkinsMKE Mar 29, 2017

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:
<sws edit: thanks, got it>

(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.

after
before

JustinPerkinsMKE commented Mar 29, 2017

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:
<sws edit: thanks, got it>

(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.

after
before

@swstim swstim closed this in f556658 Apr 3, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment