#385

I use this one. It’s free which is nice and it also has a nice feature for auto compensating to a given LUFS target. This is not always correct as its analysis window isn’t per track but per window of time (which can be arbitrarily sized) but it might give you a good tool to negotiate your ears, the math and your brain.

If you’re at all command line competent ffmpeg can now do correction and it gives you a wide range of options for what your constraints are in terms of range, peak and average. I made a command line tool for doing this with nim.

4 Likes
#386

For LUFS metering I am relying on the one in DMG Limitless, the Pro version of Youlean Loudness Meter (it’s great, the best real time one I have found), and the Statistics window in RX8 Advanced for offline scanning.

3 Likes
#387

Oh and if you need this stuff in Max/SC/pd look no further than flucoma

3 Likes
#388

For physical releases for sure, but the issue is streaming platforms, where most music is listened to these days, enforce these numbers :man_shrugging: sucks for those of us opting out of the loudness war to have our stuff manipulated, but honestly overall I’ll take it so that we can finally deescalate the loudness war and get a hint of dynamic range back in our mainstream culture

2 Likes
#389

I’ve heard great things about Youlean (above). But also, I use Logic Pro and the multimeter and loudness meter do the job just fine for $0.

I’m looking at some of the VU meters as well because they do much the same thing if dialed in correctly. There is a digital VU emulator that also has some handy monitoring switches (phase/LR flopping/MidSides/etc) but I’ve forgotten the name. Or maybe I’ll make a standard patch to hit my Nagra with the monitor signal and use the Modulo there.

I think there are many ways to do this part and whatever you start with is probably alright.

I think some of this comes down to whether the music will be listened to in a playlist or whether it will be listened to on its own/as an album. For the listener, they’ll have to mess with the volume knob every track if we’re not consistent and that won’t be much fun for them. Streaming services will automatically turn the volume up or down to match their target LUFS because they don’t want to lose listeners due to fatigue.

When we’re mastering, we usually are trying to make it sound good for the levels the listener will be receiving. If our masters sound good at our preferred level as well as a few db up and a few db down then it’s probably no big deal where we are on LUFS. But Fletcher-Munson tell us it will always sound better the louder it is and if we don’t use something (whether our intuition or a LUFS target) then we’ll be right back at loudness wars and the accompanying lower dynamic range (which is fine for some tracks of course).

It’s simpler, in my experience, to have a standard target to start with and then make decisions based on the program material, intended effect, and target delivery device. It just takes a lot of the guesswork out if I start from the same place each time.

Definitely a “your mileage will vary” thing though and I’m glad there are people advocating for an entirely intuition-based approach.

3 Likes
#390

The trouble with following streaming guidelines for loudness is that they are a constantly moving target. I stand by my original point, don’t worry about the numbers, just make it sound the best it can be. Mastering is about enhancing the emotional contact between an artist and a listener, not “hitting targets”, IMHO.

I’ve also been using a pair of really big Sifam VU meters for the last decade, they really do help a lot. I haven’t found any plugin versions being nearly as good, although the Klanghelm was the closest.

6 Likes
#391

Thats the whole point of the EBU R128 loudness algo though as it doesn’t specify stringent limits apart from peak. Otherwise you can hit the averages in whatever way you see fit creatively which makes it a much more interprative standard.

1 Like
#392

Yes, that’s right, but then you see audio forums full of people recommending certain LUFS “targets” all over the place recently, so they don’t incur a “penalty”, without even having HEARD the music they are recommending it for… I just think a lot of people aren’t seeing the wood for the trees, or are forgetting why they loved music in the first place. Emotional engagement, not numbers.

4 Likes
#393

Yes, because if you aim to release for spotify you might as well mix to their target which they are going to adjust it to anyway.

#394

Why though? What happens when they change their “target number” again in six months time? I’d rather not keep having to chase my tail. I try really, really hard to serve the music, not the streaming platforms.

1 Like
#395

They’ve moved their target 3db once. The difference of a bot changing your master 3db (maybe if you’re caught on the change) is going to be way less drastic compared to just doing whatever you want.

#396

The thing to know is that some of these services only turn down if you are above the target (they don’t amplify). so for example with YouTube if you master quieter than their LUFS target it will sound quieter than other videos.

I use HOFA’s free 4U meter plugin which does both integrated LU, as well as offline checking (when you drag a file onto it). It can also allow you to turn one side of the stereo field down which is a nifty utility sometimes. I find LUFS a useful figure to know sometimes, but don’t master to a specific value. What works for me the best is having a target monitor setting I use consistently, getting close to -12 RMS on ableton’s meter (ball park) and then getting it to be the right volume now that I know that monitoring value

1 Like
#397

I think of LUFS numbers as a handy ballpark way to keep an album levelled fairly consistenty, given that I can’t do the whole thing in one session with the same “ears” throughout.

Of course perfect equality of all the songs on an album isn’t the goal. If something sounds right in context at -15 when everything else has been closer to -11, so be it.

4 Likes
#398

Thanks so much for the help from everyone :point_up_2: there!!!
I am going with Youlean Loudness Meter 2 and at 39$ for the pro version it seams well worth it. And with it having the file drop analyze and being a visual person I’m just sitting here dropping songs into directly from iTunes and getting a good sense of what music I would like to compare to number wise and visuals. Im finding that for this project -12LUFS is about as high as I would like to go as its kind of chill kind of minimal kind of beats and kind of ambient all mixed up into one album and it was all written on the op-1 so its not the most hifi sounds to be amplifying.

1 Like
#399

This was new for me…

1 Like
#400

I’ve been recently using ADPTR AUDIO Streamliner for checking streaming service ”compatability”. I’m no mastering engineer and don’t really know anything, but I feel it gives me certain verification that the tracks should not suffer from streaming service loudness standards (at the moment) dynamics wise. For one master to rule them all I think I would prioritize Bandcamp because the biggest drop in quality comes from streaming bitrate, and focusing on Bandcamp would at least give me one place to stick best possible product, as Spotify even on Premium is quite notable difference to my ears compared to Bandcamp downloads.

#401

so if i put a song into this “Loudness Penalty” that is already on spotify it tells me its going to lower it by -3 db’s if i open spotify play the track and route it into ableton with loopback what my meters tel me is its has not been turned down and the number are like 99% the same as the master but maybe there isn’t something im understanding here.

#402

There’s a lot about this that I don’t understand. Most importantly none of us (not even loudness penalty) knows the algorithms the various distributors use.

The main thing I took from discovering this is that I should not try to push gain to be louder than everyone else anymore (actually never did). As far as I understand it, the streaming services with their algorithms have ended the loudness war, and music can go back to being dynamic again.

But as I said, I don’t know much about any of this :slight_smile:

3 Likes
#403

maybe I’m misunderstanding it too, but I feel like if you don’t get a small negative number or 0 on this loudness penalty site and you are targeting one of these services, realistically, you are putting the music you are mastering at a “disadvantage” (as if you play stuff next to each other, music that is played louder is more “engaging” than music that is played quietly…same reason why when you A/B changes it’s very important to do so at the same volume to actually be able to hear the difference and not just pick the louder one) , as some/(all?) of these services do not turn things up to reach their loudness target, they just turn stuff down if it’s above.

so in essence, I think there still is a reason to master “loudly” (enough), it’s just that it’s not based on peak limiting anymore, it’s based on a more complex algorithm.

for some music/targets this is probably not a big deal at all, as “loudness” is not the most important thing, but I think it’s important to understand what is going to happen so you can make that decision.

also, if someone knows more and sees some fault in my logic here, please let me know

1 Like
#404

Ended the loudness wars or loud won and these are the rulez :wink:

1 Like