I have just purchased Wavelab Elements 11. The WL Elements 11 Operation Manual (in the PDF version, on page 286) says:
The Loudness Meter is an audio meter for monitoring loudness, according to the EBU R-128 standard.
To open the Loudness Meter, select Meters > Loudness Meter.
However, in the menu Meters there are eight options to choose from, but there is no Loudness Meter (please see the attached picture). There is, it seems, a mismatch between the software and the manual. Am I missing something? Would someone clarify this situation? Thank you.
Does anybody else find it a bit odd that WL Elements still hasn’t got a proper loudness metering? Or even an offline analyzer. I mean today loudness analysis is pretty basic. There are no special algorithms necessary and you have to measure it a LOT of times these days. For example most Podcast platforms require loudness normalized mixes. I think even (or especially) the cheaper Wavelab Cast should have loudness metering/normalization built in. Instead we get multi-channel support. Which is very very nice - don’t get me wrong. Other maufacturers implement multi-channel support in their pro-versions (e.g. RX, Altiverb …). But I have the impression of a strange prioritization here.
Is there a way to insert a metering plug-in like Youlean and I hit render and the plug-in displays the results? Only a lot faster than real time? At the moment the display does nothing when rendering.
I purchased Wavelab Elements a few days ago and immediately noticed it. Loudness analysis is a very fondamental need in every mastering session.
The more strange thing is that I cannot load the Supervision Analyzer in Cubase 12 Pro inside Wavelab Elements 11.2
How is it possible? It seems an unpleasent marketing choice from Steinberg…
Instead of the Supervision Analyzer I can load Youlean Loudness Meter or other third part plugins to analyze the LUFS…
Why? Why Steinberg? Why I cannot use the Supervision Analizer from Cubase Pro 12 inside Wavelab Elements?
I have the same question. Clearly they are trying to force the upgrade to WaveLab Pro, which has SuperVision built in. Unfortunate and obviously poor marketing choice. There are other free options available, so I’ll not be falling for this marketing ploy. No excuse for not have a loudness analyzer (in LUFS) included in a software product marketed as a mastering tool in this day and age.
I’ve always found it helpful to look on a vendor’s website and compare the features of a product before I buy it. That way I know what features are included in the product version I’m buying, and I can make a determination on which edition allows me to meet my requirements.
You’re free to use terms like “forcing you” or “falling for,” of course. But featured-based software edition models have been in place throughout countless verticals for decades. It’s simply a fact of how products are sold. In fact, in this “day and age” it is the “in-app purchase” (what you may refer to as being “forced” to do something) that has transformed the entire economic application marketing ecosystem. So I dispute the validity of that claim.
I take the same approach when evaluating software before purchasing. So imagine my surprise when I tried to load a plugin (SuperVision) that I have licensed (Cubase Pro license) and made by the same company (Steinberg) into one of the available eight master section plugin slots (as indicated in the Wavelab Elements specifications) and it wasn’t available. I understand how feature-based software editions work. The issue here really isn’t the feature set, though I do question the value of WaveLab software without LUFS- based loudness metering. The majority of WaveLab users are musicians looking to master their own music for release on digital streaming platforms, or TV/film composers preparing audio for use in video projects. Both of these use cases require LUFS-based loudness metering, so why have any edition of the software that doesn’t have this capability? But I digress on this premise.
The issue I really take is the inability to use plugins that have already been licensed across products that support the VST standard. If I’ve licensed Cubase Pro, which includes a set of plugins, why am I not able to utilize those plugins in other products that support the VST standard, especially those made by the same company?
I wasn’t really looking for help, just expressing disappointment. Of course, there’s always a solution. My use of terms like “forced to upgrade” are, as you indicated, overblown. Obviously nobody is forced to do anything. There are plenty of loudness metering plugin options available, so it’s not necessary to upgrade to WaveLab Pro to get this capability, and no-one in their right mind would spend the extra $400 to upgrade just for this capability alone. It’s just a shame that, as a licensee of Cubase Pro, which already has a stellar loudness metering plugin in SuperVision, I’m not able to leverage it in WaveLab and must instead look elsewhere for this basic capability.
