Item Auto-Gain Staging - Peak vs. RMS / LUFS

[Nantho]

Yellow everyone !

A month ago, I asked for help on this forum because I wanted to create a script to do something like this :

• Normalize selected items to -x dB RMS/LUFS/LU (x and unit specified by user imput) ;

• If those normalized items have peaks over -y dB (y specified by user), trim them down to peak at -y dB max.

And the amazing X-Raym showed me the way ! Thanks again Man, you're the best

So, before using those scripts (Peak vs. RMS and Peak vs. LUFS), you must be aware of those little details...

• I'm not a "natural born" coder, just a clumsy "script hacker", so those scripts are a little messy, but they work ;

• In order to use them, you must have the excellent "spk77_Get max peak val and pos from take_function.lua" script from the no less excellent spk77 in the same folder as my scripts. This fantastic spk77 script can be found in ReaPack ;

• You will also need the famous SWS extension ;

• By default, the target RMS value is set to -18 dB, but you can change it by running the SWS action "SWS: Set RMS analysis/normalize options" ;

• By default, the target LUFS value is set to -23, but you can change it by running the SWS action "SWS/BR: Global loudness preferences...".

Ok, if you're still here with me, a word about what those scripts do.

When you have a bunch of items selected and you run one of them, you will be asked to specify a "Peak Threshold (dB)" value (default @ -10dB) and an "Under/Over (-/+)" value (default is Over aka "+"). For the purpose of this explanation, let's say that you have kept default values. Selected items will be normalized to RMS or LUFS as specified by the "SWS: Set RMS analysis/normalize options" and "SWS/BR: Global loudness preferences..." respectively, but then if some of those items now have peak over the -10 dB threshold, they are automatically trimmed down to peaks at this -10 dB max. On top of that, note that those items trimmed to -10 are still selected at the end of the script while the others are not anymore.

I hope those scripts can be useful to someone !

Here they are :

https://stash.reaper.fm/v/29005/Nanth...%20Staging.zip

Oh, and by the way, if one of the script guru is kind enough to take a look at those scripts in order to "clean" them, be my guest

[X-Raym]

Originally Posted by Nantho

-- Special thanks to X-Raym

Glad you succeeded it with it ! You can be proud of your work

The code is quite ok too me, but if you want criticisms anyway... :P

• just, one script have "Item" and the other "item" in its name,
• these functions are a bit cleaner than the exp trick ReaScripts-Templates/X-Raym_Val to dB - dB to Val.lua at master · ReaTeam/ReaScripts-Templates
• You could have a switch to let us decide if we want this on take volume (as currently) or item gain (maybe more useful when we have only one take per item, as item gain can be easily modified right from the arrange view)
• You could have pack the spk77 dependency in your zip

But don't worry, it is pretty good already !

[ericzang]

Thanks Nantho and X-Raym! This is helpful to me for initial processing of tracks through a console emulation (nebula).

[Frank B]

This looks interesting, I normally shoot for -20 LUFS on stereo tracks and -23 LUFS on mono tracks.
I wonder if there is a way to code that into the script as well?
auto-sense mono/stereo and apply the setting.

I barely ever have tracks that after running the actions still peak or go into the red.
When it does i never worry about it as I usually limit the track individually anyway.

I should also add that when it comes to audio tracks I use pan law with +3db preference, this makes my tracks -20 within the stereo field.

-20 LUFS is a round about -18 -16 on the VU meter

I'll give these a try a little later tonight
Thanks

[Nantho]

Originally Posted by X-Raym

Glad you succeeded it with it ! You can be proud of your work

The code is quite ok too me, but if you want criticisms anyway... :P

• just, one script have "Item" and the other "item" in its name,
• these functions are a bit cleaner than the exp trick ReaScripts-Templates/X-Raym_Val to dB - dB to Val.lua at master · ReaTeam/ReaScripts-Templates
• You could have a switch to let us decide if we want this on take volume (as currently) or item gain (maybe more useful when we have only one take per item, as item gain can be easily modified right from the arrange view)
• You could have pack the spk77 dependency in your zip

But don't worry, it is pretty good already !

Hi X-Raym !

Thanks for your inputs

I will fix the "item/Item issue" in the next version and I'm definitely gonna take a look at those functions. As for the switch regarding take or item volume, I'm afraid this feature is beyond my "script hacker" skills...

Regarding the integration of spk77 script in my zip, I didn't know if it was ok to do this because I didn't get in touch with him. I was afraid it could annoy him and as I'm a big fan of his work, I certainly don't want to bug him with an unauthorized redistribution of his work. On top of that, pointing potentially users to the fantastic ReaPack seems a good thing to me

Have a nice day !

[scottppf261069]

hi just seen the auto gain stage zip that i would really like to try. ive tried to instal the zip but it does not recognise the actions. how do i instal it into reaper as an action or what do i do with the zip. cheers look forward to trying it

[musicbynumbers]

Thanks guys! This looks very useful

Just wanted to ask, how the peaks were being "trimmed" down though?

Envelope automation or a limiter or maybe I've got the wrong idea?

[Nantho]

Originally Posted by scottppf261069

hi just seen the auto gain stage zip that i would really like to try. ive tried to instal the zip but it does not recognise the actions. how do i instal it into reaper as an action or what do i do with the zip. cheers look forward to trying it

Hi !

Well, those scripts work like others, you just need to open the action list, use the "Load" button and hit run

Don't forget that you need SWS extensions and the "spk77_Get max peak val and pos from take_function.lua" script to use them. You can find the links in my first post

Hope it helps !

[Nantho]

Originally Posted by musicbynumbers

Thanks guys! This looks very useful

Just wanted to ask, how the peaks were being "trimmed" down though?

Envelope automation or a limiter or maybe I've got the wrong idea?

It uses the take volume actually

[scottppf261069]

sorry about this. ive got both loaded into the actions list and sws extentions , reapack installed. when i try to run the action it says. cannot open file, spk77 file not found does not exsist. i am a true novice at this. 1 i downloaded action. 2 opened zip file. opened reaper and the action list and loaded the actions into the list. run the action on an item and the cannot open file message is shown. if im doing something wrong your input would help me in the future and greatly appreciated.

[musicbynumbers]

Originally Posted by Nantho

It uses the take volume actually

Interesting! Thanks, I'll give it a go!

[ericzang]

Originally Posted by scottppf261069

spk77 file not found does not exsist.

Are the Nantho scripts and spk77_Get max peak val and pos from take_function.lua in the same folder?

[scottppf261069]

ive tried putting both scripts and the spk77 in a folder in the scripts resorce path. and tried. im not really sure what im doing as this is first time ive tried or used such things. tried alsorts. any chance of step by step instructions from the download. its got me stumped and wont rest until i sort it ha ha . would be much appreciated. thanks and have a great new year.

[scottppf261069]

ive done it not sure how but its working. will have a mess with it. thanks for your time. cheers

[Nantho]

Glad to know that it's finally working ! Hope you'll enjoy it

Happy new year Folks !

[SmajjL]

mpl have made a, close media explorer after adding item.
So, can this script be run automatic every time we add an item from ME also?

[Nantho]

Oh Man, I really don't know about that...

As I was saying in the first post, I'm not a "natural born" coder, just a clumsy "script hacker".

Sorry...

[SmajjL]

That means you are 10.735% more skilled than me.
I tryed opening up mpl_Open and Close Media Explorer when item is inserted and just replaced an action code to run another action code, safe to say I suck with no potential of improvement.

[Frank B]

Can someone please add these scripts to ReaPack?
This would solve the issue of having scripts in proper folders etc.

I added these scripts to the script>x-ray>function folder to get them to work proper.
if anyone has difficulty finding the spk_77 scripts

Thanks

[Loulou92]

Hey Nice script that you have here.

I've made a little test, and so it seems to work best when we use a 4,5 pan law (levels are spot on with this calibration).

Would it be something possible to have it to work with a 0dB pan law ?

[Loulou92]

Well no actually it's something a bit more weird that happens.

If you enter false in the "popup = false -- true/false: display a pop up box" string in the script (my understanding is that this allow the script to process audio without the window showing up), then it applies a different correction than what it applies when you put a "true" argument in the script string above. The correction seems correct with a 0dB pan law when the window pops up, and it is correct with a -4.5 dB law when you edit the script to not show the window.

Is this possible ? Or maybe a user error ?

Thanks !!

[Nantho]

Hello Loulou92,

Well I honestly don't know what is happening there and as I was saying in the first post, I'm not a "natural born" coder, just a clumsy "script hacker", so I'm afraid I can't help you on this one.

I mainly use those scripts on mono items so I never had this kind of issue...

[Loulou92]

Hey ! Thx for responding, I'm seeing this only now.

Well it's fine as it is now to be honest, it's super useful, the workaround is to have the window popup each time, but actually if you set a suitable default value beforehand, it just adds one "enter" keystroke.

Thank you for sharing it with us !

[Nantho]

You're welcome

[Chipicui]

Nantho, just wanted to say big thanks for the script and encourage you to keep improving it, because just as it already is, it’s super useful and works really well.
You say you don’t have high programming skills but, at least for this script they are completely ok.
The best part of it is your specific consideration to the peaks issue.
I’ve had this problem in the past when normalizing to -18 and had to go file by file (destructively) limiting the problematic files to a peak value of -1dB... drums and percussion most of the times, as they usually have the biggest crest factor.
Some little things:
is there a specific reason for your choice of a default value of -10dB, instead of let’s say... -9, -6 or -1?
I ask you this because with a value of -10, many quite dynamic files like percussion, drums, etc, are getting a much lower LUFS value than the rest.
Is it considered sound-wise better to leave a such a big margin to 0dB for peak values?
Aren’t plugins easily able to deal with way more than 13 dB of loudness range?
Please, don’t think that I’m criticizing your choice... is just that I’m trying to make my mind up around this somewhat confusing and debatable issue.
Another suggestion: could you make a popup with a list of tracks or items that have crossed the threshold?
Sometimes in Reaper (depending on theme) I find that selected items are somewhat not too easy to spot.
So I was thinking that maybe a popup, with the list ready to be copied to clipboard.
Thanks a lot for your time, really appreciated!!

[poulhoi]

Sorry to revive an old thread but I would love to get this script working. In its current state, though, Reaper crashes when I run it. Reaper 6.18, macOS Mojave 10.14.6