Loudness Meta Normalizer - Batch Processor

Hi,
I have these settings in Loudness Meta Normalizer - Batch Processor:
Set Same Specific Loudness
Loudness -21.00 LUFS
Reference File Integrated Loudness
Maximu Peak Level
Control Tru Peaks
Maximum Peak -1.000 dB
Problem is when there is a file with no audio (a blank file) the process changes all files to blank files.
Is this a bug or am I misconfiguring the process?

Confirmed. It seems that the presence of a file with silence causes the entire calculation process to collapse, regardless of the parameters set and the content of the other files.

1 Like

Thank you ASM!
I’ve tried with every first option and same problem.

Yes, but this is “normal.” The “Loudness Meta Normalizer” is not the same as the “Loudness Normalizer.” The goal of this plugin is to set the same achievable loudness across all files. The loudness you specify (-21 LUFS) is the desired target. However, since one of the files is blank, its samples cannot be adjusted (since “0 times something” is still 0). This means the maximum achievable loudness for that file is silence !

That said, I agree this is unexpected, and I had not encountered or tested this case before. Therefore, this evening I made a change to exclude a file from the computation if it is completely silent. In WaveLab 12.0.40, this issue will no longer occur. :wink:

However, double-check your requirements. If all you need is the Loudness Normalizer, you can use that plugin instead of the Loudness Meta Normalizer.

1 Like

Understandable. Though the current behaviour seems somewhat arbitrary. The algorithm is
“Match Loudest Audio File: Applies the same amount of gain to all audio files, so that they match the loudness level of the loudest of them as closely as possible.”
So, if there are say 10 files and 8 of them could be raised to the desired level of the loudest (9th) file, I’d expect these 8 files to get the desired loudness and the remainig “silent” (10th) file simply to remain “silent” (because it’s not possible to raise it anyway).

1 Like

Thank you very much @PG1 and @ASM , thanks for the Loudness Normalizer recommendation. Best!

@PG1 the option in the Loudness Normalizer to change the Analysis Reference, returns after closing the window to Integrated Loudness in File, even if Maximum Short Term Loudness is selected, can’t save a preset that stays in Maximum Short Term.

Please explain again, or show screen shot, because I don’t see what you mean.

Analysis References parameter setting is not saved in the Preset. When loading any preset, this setting will stay at its current value.

1 Like

Thanks for the info. This issue must have existed for many years! Actually, this is not that serious because the setting is saved with the preset; hence, it will be used for processing (batch processing + preset being applied from the menu). The problem is that the UI does not reflect the option, and that visible option is saved with the dialog. If you need this setting when the UI is open, you must set the proper option, else the visible one is used. This will be fixed in 12.0.40.

2 Likes

Thank you @ASM and @PG1 !