– I did read this discussion viewtopic.php?t=460241
Where:
DarkStar wrote: Tue Apr 05, 2016 10:49 pm 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.

>>>
...