[FR] Add a LU custom reference in LoudnessAnalizer

[distante]

Right now there is 3 options for the meter reference:
EBU +9 / EBU +18 / EBU +27


Could you add an optional button or box where we can set the reference that we need? When making works for companies that have their "standards" for podcast, music or similar sometimes we need to use a reference where 0LU = -16LUFS, sometimes 0LU = -12LUFS and so on...

Of course we can do the maths and use the closest EBU reference r use the offset, but is a little bit distracting, especially when the client is there, and the LU rule isn't easy to read in that way.

If not in the free version, maybe in the paid one?

Thanks!

[MeldaProduction]

Hmmm, you seem to answer yourself - why don't you simply save presets of the target levels? I mean this is exactly that the offset is for, so if you don't want to calculate the subtraction, you can simply calculate it before and use presets.

[distante]

Fair enough, let me change the request, can we get a LUFS option, so when we need to say "See now we are in -12LUFS as for the AES recommendation for YouTube, just like you (client) wanted", we can have a visible -12LUFS.

Is more about fast readability to people how use another references.

[MeldaProduction]

I quite don't follow, could you be more specific?

[distante]

Yes of course, sorry for not been clear, I'm getting old...

For example, the AES "recommendations for Loudness" uses LUFS as unit, sometimes (my) the clients doesn't understand the underlying concepts and they just want to see that -X LUFS is showing in some place.



If we can also select also a LUFS rulers, we can show easily that we are following whatever given recommendation asked.



I hope i was clear

[steve2KVR]

...+lots for me on this one...I'm already using V's suggestion, and that works...however, having this "tool evolve," as distante suggests, makes total sense (to me). Since streaming is almost always the final goal, and streaming now seems to be measured in LUFS, it would really enhance the plugin's functionality. Instead of having several simultaneous meters on the 2bus, this change would get me back to just the one...imho...hth.../s~

[MeldaProduction]

Well, I'll think about it

[MeldaProduction]

Ok, so here's a question - how about range for the LUFS units? I mean, that's why LU has been defined - to make the target loudness easier to grasp, 0 is quite easier to put onto the scale than -16

[steve2KVR]

...yup, I think that would work, ie using/setting the target LUFS at zero/"0"...now, consider that at the moment the "target" is different for each of the "big streamers"...sooooo, howbout making the "target" a selectable parameter?.../s~

[MeldaProduction]

Ok folks, another angle - if we add not only Offset but also Target, would that be enough? Instead all the madness with LUFS and unit ranges

[DarkStar]

I think that LUFS (and LU) need to be kept. They are what the clients will want to see.

At the risk of confusing things ...

My understanding is:

• There are several different recommended Target levels, including -23, -16, -13 (in units of dbFS or LUFS);
• LUs measure the difference between a reference level and the signal;
• So a signal of, say -20dBFS, would be +3 LU, -4LU, -7LU for those three target levels;
• The Maximum Short-term level is (often? sometimes?) set to Target + 5 LUFS (this = +5LU is all three cases);
• The EBU+9, EBU+18 (and EBU+27) determine the scale displayed on a meter; for a -23LUFS reference level, the scales would be:
  • ‘EBU +9 scale’: range −18.0 LU to +9.0 LU (−41.0 LUFS to −14.0 LUFS),
    ‘EBU +18 scale’: range −36.0 LU to +18.0 LU (−59.0 LUFS to −5.0 LUFS),
    ‘EBU +27 scale’: range −54.0 LU to +27.0 LU (−77.0 LUFS to +4.0 LUFS),
• the Peak and True peak meters in the Loudness Analyzer are dbFS scales and the others are LU scales

If that is correct, then all I would need to select is:
(a) the Target level,
(b) the Maximum Short-term level (this would be new to the Analyzer)
(c) the desired Scale (+9, +18 or +27) - perhaps a drop-down would be better than 3 separate buttons?
(d) I do not think that the Offset control is needed.
(e) presets for each of the 'popular' standards could be provided
-----------------
PS I could not find a reference to -12dbFS as the Target; can someone post a link?

[ZentralmassivSound]

Is it just me or does Analizer sound different than Analyzer

[steve2KVR]

...yes, but it really depends on how obsessive compulsive you are, and whether or not you able hold on to the results until the next trial commences... .../s~

...and a big +plus up on DarkStar's post...im ok with the current maths, but am tired of trying to explain it all...over and over again...

[MeldaProduction]

I think that LUFS (and LU) need to be kept. They are what the clients will want to see.

At the risk of confusing things ...

My understanding is:

• There are several different recommended Target levels, including -23, -16, -13 (in units of dbFS or LUFS);
• LUs measure the difference between a reference level and the signal;
• So a signal of, say -20dBFS, would be +3 LU, -4LU, -7LU for those three target levels;
• The Maximum Short-term level is (often? sometimes?) set to Target + 5 LUFS (this = +5LU is all three cases);
• The EBU+9, EBU+18 (and EBU+27) determine the scale displayed on a meter; for a -23LUFS reference level, the scales would be:
  • ‘EBU +9 scale’: range −18.0 LU to +9.0 LU (−41.0 LUFS to −14.0 LUFS),
    ‘EBU +18 scale’: range −36.0 LU to +18.0 LU (−59.0 LUFS to −5.0 LUFS),
    ‘EBU +27 scale’: range −54.0 LU to +27.0 LU (−77.0 LUFS to +4.0 LUFS),
• the Peak and True peak meters in the Loudness Analyzer are dbFS scales and the others are LU scales

If that is correct, then all I would need to select is:
(a) the Target level,
(b) the Maximum Short-term level (this would be new to the Analyzers)
(c) the desired Scale (+9, +18 or +27) - perhaps a drop-down would be better than 3 separate buttons?
(d) I do not think that the Offset control is needed.
(e) presets for each of the 'popular' standards could be provided
-----------------
PS I could not find a reference to -12dbFS as the Target; can someone post a link?

If all this is true, then I'd personally say "just target level" parameter would be a better solution. To me it just seems idiotic to watch for say -14 LUFS, when you can just say -14 LUFS is my target and then watch for 0...

[DarkStar]

That would work for me - I would pick -14 LUFS as the Target and select a scale (say EBU +9).

The resulting LU scale would be from −18.0 LU to +9.0 LU (and that would be equivalent to −32.0 LUFS to −5.0 LUFS). The Target level would be 0 on the LU meters.

Here are two screenshots showing what it would look like (I had to set the Offset to -10.40 to get a -14dB white noise signal from MNoiseGenerator to register as 0 LU in MLoudnessAnalyzer). And, as you can see, a -11db signal registers as 3 LU (actually 2.9) And, (Feature Request 1) I have add 'LU' to the figures for the LU meters as a gentle reminder what they are indicating

>>> http://i.imgur.com/SuEAXD2.png

The client would see -14 LUFS selected on the Target slider / drop-down / button and see 0 LU on the meters and will be happy (if the audio signal hovers around 0 LU on the meters and timegraph )

(Feature Request 2) I think that it would also be useful if the Max Short-Term level were also selectable (e.g. LU +3) and for that to be indicated on the meters and timegraph. Perhaps like this:

... http://i.imgur.com/YT3YCym.png

With the signal level between Target and Max Short-Term being shown in orange, and red above that.

PS The 0 LU level in the timegraph should be emphasised (a thick line, perhaps?) to show where the Target level is. As should the Max Short-Term level.