Official 3rd Party Plugin Issue Thread

Exponential Audio Phoenix Surround Reverb
→ crash on play with VST2 and VST3
OSX 10.11.6, WL9Pro (9.0.35), Master Section

D16 Group
sticky Mouse cursor (VST2)
with:
Antresol
Decimort 2
Devastor 2
Syntorus

no tempo when on host sync (VST2):
Repeater

crash on click “Tempo”(VST2):
Sigmund

OSX 10.11.6, WL9Pro (9.0.35), Master Section

Eiosis AirEQ Premium VST2:
“Error reported by plug-in Eiosis AirEQ Premium 5.1:
At this insertion point, the plug-in cannot accept the number of input channels.”

direct crash of WL when loading the Eiosis AirEQ Premium VST3 version
OSX 10.11.6, WL9Pro (9.0.35), Master Section

Exponential Audio Excalibur
sticky Mouse cursor (VST2)
→ blank window (VST3)
OSX 10.11.6, WL9Pro (9.0.35), Master Section

Lexicon Total Bundle (VST2 only)
→ sticky Mouse cursor
OSX 10.11.6, WL9Pro (9.0.35), Master Section

Sound Radix SurferEQ2
→ blank window (VST3)
OSX 10.11.6, WL9Pro (9.0.35), Master Section

UVI (VST2 only):
Spark
Relayer
→ sticky mouse cursor

OSX 10.11.6, WL9Pro (9.0.35), Master Section

I can’t reproduce this one. I use AirEQ VST3 often and it’s been stable for awhile now here. Are you using the latest build 1.1.5.3 of the plugin? You can download it here:
http://downloads.eiosis.com/AirEQ/Installers/AirEQ_Premium_1153_Mac.zip

I also get the error message when trying to use the 5.1 version but I’m not certain the 5.1 should be used in WaveLab anyway. I admit that I have very little experience with anything beyond stereo routing/processing in WaveLab though.
I just stick with the stereo version and never use the 5.1 version of AirEQ.

The latest VST3 version is stable here on OS X 10.11.6

Ok, I was short in description. I have the same version here already - but thanks for the link. IMO the surround versions shouldn’t act like this - they don’t in Nuendo/Cubase.
Ok, the crash of the VST3 version is not reproducible right now - but it was the case. Wasn’t it you, who wrote about the somewhat erratic behaviour of plug ins in WL? To restart the app every time for checking out plug ins would be to much really - maybe plug ins render WL unstable somewhat and it has consequences later with other plug ins?
This all is very unfortunate and a time consuming mess.

DMG Limitless in VST 3 is buggy. But, I think it would be fair to say that this is acknowledged by DMG.

However, I can repeatably generate a crash when using the VST 2 version if I remove the plugin from the master section after stopping play.

It will not crash if I first play another track where the master section is bypassed and then remove it from the master section.

Typically, I will only ever have three pugins … plus one or two WL gain plugs to stage the gain.

Limitless (when I use it) is always last in the chain before dither.

It “feels” like the Limitless somehow stores a buffer somewhere and when the plug is removed this behavior causes WL to crash. This does not happen on any other plug.

This is still a 32 bit Windows 7 Professional system.

Whilst this seems to be true, I think it should also be acknowledged that … when compared to other highly specialized mastering only DAWs (like Sonic, Sadie or even Sequoia for example) … it is difficult to maintain an argument that WL is “worse” than any of these and in fact you could make a convincing argument that it could even be probably “better” in terms of its plug in functionality.

Apples with apples and these frustrations could be a function of the fact that not many people actually buy a mastering specific DAW … it’s a pretty small sector.

But that doesn’t mean that a comparison with market leading DAWs such as those listed is not valid or useful. It is.

Apologies if this is straying off topic and I’m happy to delete this post if it is.

DMG Equilibrium

In VST 2 or 3 the plug initially displays it’s configuration screen when opening WL with saved master section plugs.

If you move the display with the mouse slightly and click, this changes to display the EQ GUI as you would expect. It retains and displays all of the correct, saved settings.

The same behavior occurs if you load a master section from the preset menu.

I use this plug practically every session (meaning every day) and I don’t remember this occurring with its previous version/revision.

This leads me to conclude it’s probably not a WL bug as such.

Equilibrium is typically loaded first or second (after a WL gain plug) in the master section and usually in M/S mode set to highest quality in the universe.

It’s been suggested to me that this behavior may not occur on a 64 bit system.

Otherwise, the plug behaves exactly as it should. It is such a minor inconvenience that I have never got around to emailing DMG.

Windows 7 professional 32 bit.

From Jesus Tossas who is having issues logging into this forum:

“I have Wavelab V 9.0.35 Macbook pro Sierra Version 10.12.2. I purchased A.O.M Invisible Limiter V2 in VST2. I use it on the master section and I experience the magnetic mouse effect. With other DAWs I have works fine. Thanks to whoever can post this on that thread.”

Nugen plugins sometimes work on 9.0.35 for the Mac and the PC. Sometimes they don’t. Never could get it to be repeatable. It seem to be completely random whether they run or choose not to.

Window 7 Pro on a very fast “gaming” computer i5 Processor 20 gigs of memory and all SSD drives. OS El Capitan on a fully loaded Mac Pro computer 20 gigs of memory and all SSD drives.

I forgot about NUGEN. I had some serious problems with them. Anything from opening a NUGEN GUI crashing WaveLab, to ISL2 rendering or recalling in it’s default state instead of the way I had it set.

I think some of that was resolved and if you open an old session with the updated version of ISL2, it gives you a warning that it couldn’t recall the old settings.

I’ll have to make sure I have the latest NUGEN updates installed and try again but NUGEN was basically unusable in the recent past.

I get that message, but only with the VST3 5.1 Premium Air, and only if I insert it with a Stereo montage, or with a 5.1 montage before the Master Section is initialized 5.1 (before playing a 5.1 montage). So basically it works as I would expect in Wavelab, since the Master Section only turns into multichannel when you play a multichannel montage, I would expect to need to do that before inserting the plugin.

But strangely here, the VST2 5.1 Air doesn’t seem to care whether the montage and master section are Stereo or 5.1, I get no error messages at all with the VST2 5.1 Air. (but my VST2 5.1 is not called “Premium”, only the VST3 is.)

Testing this on Windows.

So … all these efforts and discussion started by us, the users, and no beep from PG or a Steinberg official about these problems here. Thank you.

and no beep from PG or a Steinberg official about these problems here

Silence does not mean we’re not reading. Actually, there is the plan to make a table about the different cases, as an internal reference to track.

If I am not wrong, I note, however, that there is no problem reported for the 3 biggest plugin players: Waves, UAD and Steinberg.

Thank you for this info. No problems with Waves in WL9 as far as I can tell. I also have UAD plug ins, but I use them more within Nuendo and Cubase, if at all, and therefore don’t know if there are problems with them regarding WL.

I use UAD a lot in WaveLab and can’t think of any issues, though UAD is still VST2 only which I think developers have an easier time with. What’s interesting is that UAD doesn’t officially support WaveLab but they appear to be very stable.

I don’t use Waves very often in WaveLab anymore. The last issue I remember which I believe is resolved was the disappearing cursor.

I also rarely use a Steinberg plugin.

We need to find a way that some of the mid-level developers such as FabFilter, DMG, Plugin Alliance etc are more stable in WaveLab, as well as the smaller or less popular developers.