MLoudnessAnalyzer wrong Integrated result

[Svama]

Hi,

I´ve compared the integrated result of difference loudness plugins and all have the same result without MLoudenssanalyzer. Vojtech, please take a look what´s wrong?!

Thanks and greets,
Marek

[Hexspa]

I get the same integrated result with RME Digicheck as I do with MLoudnessAnalyzer (-23 LUFS target) when playing 45 seconds of noise. The Loudness Range values update at a slightly different rate but generally are the same.

What I can tell you, from using other loudness analyzers, is that many of them have their own unique calibrations. I forget all the details but I probably wouldn't use MLA if I thought it was wrong. If it agrees with the RME meters then I'll have to assume it's right; or at least it's aligned to my system.

Perhaps what I'm saying is that MLA probably isn't 'wrong' so much as other meters may (indeed, some definitely do) have different settings and/or preset calibrations.

[Svama]

We use it for broadcast television. The clip is about 90 minutes long.
But the mathematic should be the same or not. I’ve compared with youlean loudness meter, grimm level norm and a hardware rtw meter.

[DarkStar]

^^^^
Can you post the Integrated values that each one showed?

Here, I see

• MLA -2.9 LU (on a target of -23
• T-Racks % Metering -25.9 LUFS-I
• TBProAudio dpmeter -25.9 LUFS
• Youlean Loudness Meter - 25.9 LUFS
• Reaper's Loudness Meter - 25.9 LUFS-I

[Svama]

I will do tomorrow at work

[bilrobins]

Hi

Just a quick test: YouLean, MLA, Izotope Insight - all very close (within 0.1 LUFS Integrated).

Seems fine here.

CHEERS

[Svama]

Thanks, but did you try 90 minutes and more. Short audio is no problem here at all, but the long files seems to be. I will send my screenshots in some hours.

[Svama]

Here are the screenshots

[Svama]

This is a really big issue and problem for us. Please give us a fast bugfix for this issue!
I´m really in a hurry in this case, cause we´ve already archived broadcasts with wrong values this way and we can´t change the software on our production systems that fast in our company.

Thanks

[Svama]

For the beatrig level norm screenshot. It shows the divergence from target value -23 Lufs in LU. So it’s -23 LUFS in this case and correct for brodcast television.

[Tagirijus]

This is a really big issue and problem for us. Please give us a fast bugfix for this issue!
I´m really in a hurry in this case, cause we´ve already archived broadcasts with wrong values this way and we can´t change the software on our production systems that fast in our company.

Just out of curiosity: why not just use Youlean Loudness Meter then instead?

[Svama]

Cause we can’t install software that easy on our production systems, they’re configured and installed by our IT Support. They need a change request, which takes long times. Updates are no problems, but changing the software. Because all software needs to be packet for install. Bureaucracy! It’s really cruel. We’re talking about 60 systems and more in this case.

I hope Vojtech can fix this with the next beta or final 15.02 release.
I’ve introduced Meldaproduction inside our company instead of beatrig level norm, which needs a dongle.

[Held]

I don't know much about LUFS, but I can see that the LevelNorm shows EBU R-128 whereas MLoudnessAnalyzer is set to EBU+18. Could that account for the difference?

And if your request is time-critical, you should probably contact Melda directly via their form/email.

[Svama]

That’s not the problem and I’ve already contact him by mail. So this topic can be closed now. Sorry!
Thanks

[DaneJ]

If I am correct, you will need to set the Target to 0.00 LUFS under the settings panel in order to get a proper reading.