Blank plugin window

[wibem]

With some VST2 plugins, I get a blank plugin window, if I open them in Studio Pro. It might be an issue with the graphic driver. I disabled the hardware acceleration, but that didn't help. The plugins are e.g. Mulab plugin v 10 ( which is brand new) or Nora and others. Any idea, what could help?

 

[Lukas]

Is Mulab v10 compatible with Fender Studio Pro? What does their support say?

 

[wibem]

The support of Mulab doesn't have any idea about the reason for this behaviour. MulabPlugin is a regular VST2 plugin, so it should be compatible withStudio Pro.

 

[Lukas]

MulabPlugin is a regular VST2 plugin, so it should be compatible withStudio Pro.

That's not how things work in software. Different plug-in use different frameworks (e.g. UI frameworks) and need to be tested in compatible hosts.

 

[wibem]

I don´t understand what's behind the plugin. The plugins , which have an issue inside Studio Pro, work without problems in other DAWs like Cubase and Reaper. So, it must be an issue of Studio Pro .

 

[Lukas]

No. This is exactly what many people misunderstand: compatibility is always the result of an interaction between different pieces of software. Studio Pro may support features or interaction patterns that Cubase or Reaper do not. As a result, certain code paths in the plug-in may never be triggered in those hosts but may be used in Studio Pro. If there is a bug in that part of the plug-in, problems can occur only in Studio Pro, even though the plug-in appears to work correctly elsewhere.

Studio Pro cannot be expected to fix issues inside thousands of third-party plug-ins. It is therefore primarily the plug-in developer’s responsibility to ensure that their plug-in works correctly with supported hosts and to investigate host-specific compatibility problems when they occur.

 

[wibem]

Unfortunately that doesn't help me any further. I don't want to discuss who has to be blamed for this issue. I have contact with the developer of the Mulab plugin and he will investigate , what can be done on his side. My hope was that somebody in this forum has an idea , what could help.

 

[Lukas]

I was not trying to blame, but just to clarify why the fact that the plug-in works in Cubase or Reaper does not necessarily identify Studio Pro as the source of the problem.

Since this is most likely a bug rather than a configuration/usage issue, there may not be much anyone here can do beyond suggesting possible workarounds (like avoiding AU versions of plug-ins) and recommending that you report it to the plug-in developer. It is good that they're investigating it. Could they reproduce the issue?

 

[wibem]

There is no AU and no VST3 version of this plugin. The developer is working on this. He wrote that he has not much time at the moment and can't look into this issue deeper.