MeldaProduction

tombuur · Post by **tombuur** » Mon Aug 10, 2015 7:22 am

Offset is the word you use in the right lower corner of mloudnessanalyzer. It is the offset from the target.

Your target is always -23 LUFS. So if I want a target of -16 LUFS for iTunes, I have to use an offset of -7 to get the desired loudness. (Not so clear).

Perhaps the simplest thing would be to change your "offset" to "target" and then change the function accordingly, i.e. the user inputs what LUFS level he is aiming at. In my example this would be -16 LUFS or something else as the target, rather than the amount of deviation from your fixed target of -23 (offset -7 in my example). Look at how Nugen´s Mastercheck does it.

... and it would be nice if you could give us similar options to choose the LUFS level we are aiming at in mcompare and other plugins using loudness or metering.

MeldaProduction · Post by **MeldaProduction** » Mon Aug 10, 2015 4:48 pm

True, but how many of these targets there is?

So I'll make you a MLoudnessAnalyzer preset for iTunes, solved

. Creating a special plugin for "A minus B" seems rather weird to me, especially if you need to do that once

. Is there some general site with these targets for different platforms like iTunes?

What other "similar options" are you talking about?

Holy crap the MasterCheck thing costs over 150 USD

. I don't understand how anyone can ever buy that

. There's too much money in the world

. Maybe MMasterCheck would make sense then

.

tombuur · Post by **tombuur** » Mon Aug 10, 2015 5:50 pm

Yes, you can beat Mastercheck. For one thing mcompare will play reference music from disk. Mastercheck can only play from a track inside the DAW. Just let us have the option to choose our own preferred target LUFS, and perhaps some presets for iTunes etc. Maybe the ALC could set the target LUFS too, if you want to match the loudness of your own song to the reference?

MeldaProduction · Post by **MeldaProduction** » Mon Aug 10, 2015 10:32 pm

That doesn't sound good at all. MCompare is for comparison, it should NOT change your audio in any way. And it is not supposed to be a generalized loudness processor. Sure, adding target loudness would be an option (it's not related to this thread at all though), but it should really not change the loudness after that.
Quite frankly, seeing how Nugen is stealing from all of you folks, I'm thinking I should make these stupid tools commercial as well... After all, all you need is a preset in MLoudnessAnalyzer. So if someone is lazy enough not to use a preset or do math like "A minus B", then probably he should pay some money

.

Svama · Post by **Svama** » Fri Aug 14, 2015 8:39 pm

The new, very expensive izotope rx loudness control has a good clear gui and the features we need, but not at a price you need to do a bank robbery.

Tagirijus · Post by **Tagirijus** » Sat Aug 15, 2015 8:31 am

349 $ ... haha

...

"It's the best-sounding automatic loudness compliance processing available today" - a question: how can simple volume control sound good or bad ??

tombuur · Post by **tombuur** » Sun Aug 16, 2015 9:25 am

Tagirijus wrote:349 $ ... haha ...

"It's the best-sounding automatic loudness compliance processing available today" - a question: how can simple volume control sound good or bad ??

In case all the competition has solved the same problem with ugly sounding compressors, I guess a simple volume control would be the best sounding. But yes, it not rocket science to come up with this solution.

MeldaProduction · Post by **MeldaProduction** » Sun Aug 16, 2015 11:14 am

well, marketing is getting weirder every day

MeldaProduction

KVR Audio

EBU Level Normalizer Plugin