Vst Plugin Youlean Loudness Meter 2 (vst)

[Darci Carlton]

Youlean (Julijan Nikolic) is also part of the FL Studio alpha team, and many of his work like Patcher presets and ZGameEditor Visualizer effects are already part of FL Studio.Why Youlean Loudness Meter?Once I learned about loudness metering using LUFS, I was really fascinated. The problem was that the plugins for measuring it were (and still are) really expensive and there were no free ones that can get you started.

Get results in just a few seconds!A/B statesCompare two totally different measurements in just one click.Export everything in PDF, PNG or SVG fileEasily export PDF, PNG or SVG of all your measurements.

In combination with system time coding, pinpoint the loudness problems in live events, or just make a wall poster of your favorite song!100% accurate meteringThe plugin is calibrated and tested against ITU-R BS2217 testing materials.

TPKnowing the true peak value is really important since it indicates the true maximum level of audio after conversion to analog or different digital form such as conversion from WAV to MP3. If your audio goes above 0dB TP you might get clipping in converted audio.Lifetime FREE updatesEvery PRO User gets lifetime FREE updates!

*For more answers go to the FAQ pageCan I install Youlean Loudness Meter on multiple computers?You can use the plugin on multiple computers as long as these are your personal machines and you are the only user.

This option is not applicable to companies, organizations or schools, they need to purchase a multiple license version.Can plugin alter the audio so that it fits the selected standard?No, currently the plugin is only doing the analysis, and it can not alter the audio loudness.

This feature might be added in the future though.Is there an EDU discount?Yes, if you are a student or a teacher you can qualify for an educational discount of 30%. You need to contact me before the purchase.

Following on from Open Mic 10, some questions were raised about optimum loudness levels and how to achieve them. I had been having a side bar conversation with @davidp following his recent OBS experiments and some of this was centred on using loudness meters.

Another Loudness Meter, which I believe Mr P has been using provides similar functionality, so I will include a link for that as well. Orban Loudness Meter which is completely free but imho less functionality.

I found using the Loudness Meter allowed me to get an good set up much quicker than in the past, with the knowledge on what True Peak level was required and what my target Integrated LUFS level should be for YouTube.

Audio Input (Guitar/POD Go, Vocals/PlayAcoustic and Drum & Bass BT/Trio+) are connected to my audio interface and fed into OBS as an ASIO Input Capture source. The AIC then has Gain, Limit and Youlean Loudness Meter added (the latter as a VST plugin). With reference to what was said in the above video, I set the limiter to -2 db.

Once those initially levels are set up I will record a video practice run in OBS with all parts and again monitor the levels and tweak the gain in OBS as required. What is also helpful is to convert the OBS video into an audio format (WAV MP3) and drop it into the Youlean standalone meter on the desktop, as you can see the wave form and levels for the whole song. See screenshot of Should Have Listened recorded in OBS.

Interestingly, when the same set up was then recorded in Zoom (from OBS) the overall level dropped. Integrated LUFS for OBS 16.5 and Zoom 19.7. This is something a few of us have suspected for a while but now backed up by evidence. So I could have actually boosted the OBS audio gain by 2-3 db and have still fallen just short of that magical -14 db figure when the audio passed through Zoom. Worth bearing in mind that there is some headroom!

FWIW - in the past many of us have referenced the YouTube Nerd Stat figure of -6 db being the optimum level to aim for (right click on YT screen) and both my OM X songs, recorded using the method above came in at -5.7 db when I did my final Dry Run videos before the show. If I had hit that figure in the past by trial and error, that would be the time to step away and leave everything ready for the show.

I would say that should be the average for YouTube but other streaming services differ level wise. Spotify (not that I use it) seems to be the same as YT at -14db (at the moment). The True Peak limit should stop any overall clipping and I think YT will dial down volume if its too hot. But as the video says YT does not increase DB like other platforms (Spotify) so getting as close as you can is the target.

This video will make more sense of that where there is reference to the loudness levels, used by Spotify -normalization
YouTube would appear to use similar values from what I have seen on various sites.
I was going to include it above but thought it might muddy the waters.
The difference is, Spotify (and others) will raise or lower loudness for consistency but YT will only cap if too loud, not raise. So aim for an Integrated LUFS setting of -14 if uploading to YouTube. I use -16 for wriggle room and also that I can come in a little hot on the OMs because of the style I tend to play or in the last case knowing I was going to let rip on the vox at the end of Turn and I was clipping at the higher level.

The OM X video is showing -2.9db on the Nerd Stats, so I might create an MP3 version and drop it into Youlean LM and see what the stats are for the whole show. That could give us a better target for the future, assuming @adi_mrok did not tweak the audio levels on the Zoom video before posting ?

I dropped an MP3 version of the show into the Youlean Loudness Meter and saw some interesting results. Across the whole show we averaged -17.3 Integrated LUFS, so a little down on the optimum -14 LUFS for YouTube.

Move the volume slide on the YT page and the Volume/Normalized levels will change accordingly. But it still does not explain what a negative or positive db value means ie is the sound short of YTs optimum level or above? Remember YT does not adjust loudness/volume up only down. So I am trying find that answer next.

The first part of this stat is simple. The volume shows where the volume slider currently is as a percentage, with 0% being all the way to the left, and 100% being all the way to the right. The second part of this stat is a little trickier to explain, however.

It is this value that is used to determine the normalisation amount, as YouTube attempts to bring this video in line with their reference volume. This value will not change based on any action taken by you, such as moving the volume slider. In fact, it is fixed at the point of upload, and would only change if the video was edited to adjust the volume, or YouTube changed their reference volume.

Finally a good video from Kenny Gioia using in YouLean LM in your DAW in his case Reaper but should apply to all DAWs. So this could be useful for folks mixing multi tracks and not just prepping for Open Mics. Mr P may have shared this in the past but relevant to this thread.

I have given up on the chase as to why the Nerd Stat of -6 db Loudness level was recommended in YouTube but it was banded around some years back. But these platforms are changing all the time, so it may well be redundant. Certainly if you hit that figure your YT post or OM audio will have a pretty good sound level but you would have some scope to push a little louder. But if you see a positive number, best to dial it back below zero.

Anyway, plenty of stats, figures and tech info for those who like that stuff but at the end of the day a simple Loudness Meter like the one from Youlean, should mean you can optimise your levels for posting or live performances much quicker - with out the constant need for YT uploads and constant stat checks (which I did in the past).

A good article JK. I think if we had been able to put a -1 or -2 db limiter on the shows audio, all those clips on the screenshot would have been avoided. Interestingly, I just drop the OM MP3 into and the Spotify reading came out bang on the money at 0.0 db. And given YT and Spotify have an ILUFS level of -14 it was spot on for YT.

Youlean Loudness Meter 2 which can be obtained as freeware and upgraded to pro at a reasonable price (mho give the tools capabilities). It can be added as a VST plugin to OBS or can run a desktop standalone program.

But the results were surprising. Given the Stats for Nerds result of around -3.5dB I expected Integrated LUFS in the region of -16 to -14. But it was way way softer. Turn on Orban and I see what I expected.

And I should add, the key for me, is to meter the integrated output of OBS. It is helpful to meter individual sound sources but mostly what I want is a view of the final mix. It is a pity that OBS does not show the master mix anyway and allow one to apply filters to that, like one would in a DAW like Reaper.

I love this plugin. I use it for every master I got.
(Also for gain matching and compensation of different tracks when mixing).

But there is one thing which so unbelievably annoys me every time I'm using it:

I use the plugin only for the meters to the left (without the histogram) and like to use it in vertical mode (that is: 'Histogram graph - OFF' in the view settings), pinning it to one side of my screen. In this way I can always look at the meteres on the fly, without wasting any space unnessary and have the place empty for my DAW and other plugins.

Now, the problem is that every f***ing time I initiate one instance of YLM2, I need to switch back over to the settings at the very top left corner, click on the switch to disable the histogram view and again close the view settings.

Why can't the plugin remember that state or have a preset with my preferred visuals?

A great plugin, but that is absolutely worth for me to take one star away from a 5/5 review.

My to-go loudness measurement tool. It is accurate, well designed, gives the best and most needed visual feedback and makes mixing fun! It even lets me export the loudness and dynamic range into a fancy PDF file - nice! I recommend it 100% - even the pro version, to at least support the dev, which would be well deserved. By the way: dev replies to feedback (any issues or FRs) quite fast. Thanks for this tool and that support!! (=.

c80f0f1006