This part is a small trick. It allows to measure LUFS below -60 LUFS. If you remove that piece of code, you will not be able to measure anything that has value below -60 LUFS. This limitation is part of build-in plugin Loudness Normalization.
(setf lufs (- (- original-peak new-peak) 35))
Maybe you ask why not to normalize to 0 LUFS, but to -35 LUFS??. It is true that 0 LUFS also works. But, only for 32-bit… If someone would use 16-bit or 24-bit, the audio will be heavily clipped at zero level and the measured loudness will have the same value as the peak value. So again this is a simple trick to avoid this. I selected -35 LUFS as a safe level for a standard voice recording, but obviously there can be some very extreme cases when the loudness will be not absolutely precise. This can happened if the recording is extremely low volume but there are some short parts that are extremely loud.
Yes, this is a dilemma for me… I do not use Loudness Measurement with the default settings. It means that I always disable Treat mono as dual mono.
Why? A simple user story goes like this: “For the same piece of audio, I want to see always the same LUFS value, no matter which measurement tool I would use.”
With enabled option Treat mono as dual mono, I do not get the same loudness value. I have compared with multiple measurement tools. For example, if I measure with Insight directly in the Audacity, it looks like this:
But if I disable dual mono option, then my measured value is the same, no matter what tool I use:
I really do not want to say this is good and this is not, I understand that there must be a good reason why the dual mono option is recommended in Audacity. But what can I do, if I want to provide to the users a uniform experience if they would compare with other loudness measurement tools?
Please, I am still learning and there is a lot of stuff that I still do not understand, so I am open to any new knowledge and I appreciate any help to make the tool that would be helpful for other users.
There is. It’s because it is correct
Turning it off is provided as an option only so that it is compatible with the (many) LUFS meters that handle mono incorrectly.
The whole point of LUFS measurements is to represent “subjective loudness” rather than just “amplitude”. When you play mono audio through a stereo system, the same sound plays through both speakers. If you take a pair of wire cutters and cut the cable to one of the speakers, then you will get half the sound (3 LU lower).
Please be aware that when using VST/AU/LADSPA plugins in Audacity, there is an error, has been present for many years
and is still present.
The error is that the audio levels sent to the plugin from Audacity are wrong, they are too high by up to 6dB, and it varies.
This means that any plugin that measures Peak, RMS, LUFS, will report the wrong values.
Also note that this error does not affect built-in effects such as Nyquist ones and the built-in Normalize effect.
I wrote about it here:
Others have reported it too:
The problem/error is present on Windows, Mac and Linux (if not using Jackd).
Under Linux, if the plugin is applied in the Jackd chain (i.e. on the main output of Audacity output, then it’s fine).
There is an update. Because it is now Nyquist plugin, it is posted on a different forum: click
For the best performance, I recommend to continue to use the macro version.
If you want to study ITU-R BS.1770-4 algorithm translated to Nyquist language or you want to implement lufs measurement into your own Nyquist plugin, see the code of the my plugin.
I have been scouring threads on this forum looking for help with my problem and whilst I haven’t found the answers, I feel you are all very knowledgeable and may be able to help me
BACKGROUND: I am editing a podcast and would like to achieve -16LUFS for it to be at the right level for Spotify, apple etc.
I am setting ‘Loudness Normalization’ on each individual track containing dialogue to -16 LUFS
THE ISSUE: However, once all tracks are mixed down to one, the Youlean meter is showing different LUFS levels under the ‘INTEGRATED’ heading as either much lower (-28 to -22 LUFS) or slightly higher (-13LUFS).
NOTE: only one person speaks at a time, except for the occasional agreeance with the speaker e.g. ‘yes’ or ‘ahhhh’
However, I do have intro and outro music (I use auto-duck to reduce the music when someone is speaking.
Could the fact that multiple tracks are creating sound at the same time this be what is affecting my LUFS levels when mixed and rendered down to one track?
I am told that all of the popular streaming services will apply their own loudness normalization, so if that is the case, is it still worth applying ‘loudness normalization’ (to -16LUFS) on each separate track bfore doing the mix and export and doing it again?
Is it better to ONLY apply ‘loudness normalization’ once all tracks are mixed and rendered OR, is it still okay to apply ‘loudness normalization’ to each separate track - AND then again once mixed together?
Yes, absolutely. Imagine if there are 30 people that individually talk with a loudness of -16 LUFS, if the 30 people all talk at the same time, the noise that they make collectively will be louder than any one individual.
To set the loudness of the mix, you must mix the tracks first, then normalize the mix.
I don’t think that is the case. Some streaming services “may” apply their own loudness normalization, but I doubt that they all do. I don’t know if YouTube ever normalizes the loudness but I’m sure that they don’t always, because some YouTube videos are very much louder than others.
Mix the tracks so that it sounds balanced when you listen to it. Adjust the track “Gain” sliders if necessary so that no single track is too loud or too quiet. Then mix down to a single track, then apply “Loudness Normalization”.
Thank you so much for getting back to me so quickly.
Makes perfect sense! thank you for clarifying this!
Is it still worth applying the standard ‘normalization’ and ‘compression’ effects to each track before using Gain?
Also, is it better to use Gain slider than to manually ‘Amplify’ the track?
For the projects where I have already used ‘Loudness Normalization’ to -16LUFS for each separate track- and also then mixed them down - and saved the project, is there any way I can amend the LUFS level for the final mixed down project?
If that’s the case, what is the risk of sending in audio which is above or below the recommended LUFS for each service (for example, if Spotify recommend, say, -16 LUFS and I send a project which occasionally hits -13 LUFS, or hangs around -32 LUFS for a while when playing)?
I guess my concern is that it may cause distortion / clipping or sound weird in some way.
Compression (or Limiting) is used on speech to even out the level. In particular, it is used to push down any peaks that are substantially higher than the rest. It is usually beneficial to have a little bit of compression / limiting on voice recordings. I usually use Audacity’s “Limiter” effect with default settings after Normalizing to 0dB.
This should be done before mixing.
When mixing, you can adjust the track levels either with the sliders, or with the Amplify effect, whichever is more convenient.
I would generally get the tracks “about right” using the Amplify effect, and then tweak the levels using the “Mixer Board” (In the “View” menu). The “Mixer Board” does exactly the same as the track Gain controls, but with longer sliders that are easier to use.
Once the track has been mixed down, it is not possible to adjust the levels of individual voices - you need the voices on separate tracks for that.
You can still adjust the overall level, either with Loudness Normalization, Amplify, Normalize or any other method.
The short answer: Yes you can import the mix track, apply Loudness Normalization, and export.
(A little tip: Avoid overwriting files, just in case you mess up. Export files with a new name, and be organised about how you name things. Example: “FinalMix01.wav”, “FinalMix02.wav”, …)
It can be annoying to listeners when one track is significantly louder or quieter than other tracks on the service.
Some services may reject your work if it does not meet their requirements (Amazon / ACX is know to do this) .