Locked GUI / no input on certain 3rd party Plugins

I have two reverbs that don’t always work in my Cubase 13 projects. EW Spaces II and Seventh Heaven both often have locked GUIs (it opens, but no controls can be manipulated) and there is no audio coming in or out of the plugin. In my sessions they live on FX send tracks. If I put a Steinberg or Native Instruments plugin right below it, and disable the problematic plugin, the new Plugin will behave as expected.

All plugins are running in VST 3 mode.

Anyone see this have some tips? It’s happening both on my old system and a fresh install of Windows, so it must be related to my project file somehow. Another common denominator is both EW Spaces II and Seventh Heaven use iLok. Both are registered on my machine and I see no issues within iLok manager itself.

Have you tried uninstalling and reinstalling the plugins?

Yah, first thing I tried. I even loaded these projects on a new windows install and see the same issues. Its intermittent, which is always the most frustrating bug to track down.

Hi GPNicolett

I have the same issue with some other plugins. (Tai chi, but NOT 7th Heaven, Baby audio, UJAM, Arturia)

The GUI does actually work in my case (or at least parts of it do) as you can see eg if reverb Time is changed the changes show in the mixer history, though the GUI image remains fixed.

I find that if I leave the offending plugins GUI open when I save the project, it works on reopening. But this can be a real pain in the ass if there are a lot of affected plugins and the GUIs have to be reopened before saving on each occasion.

I also noticed it seems to be triggered if there is an instance of the plugin (particularly Tai Chi) disabled in the insert chain. Reenabling cures it…

It seems to be a graphics issue. I have a PC with built in graphics (Intel UHD 630)

Did you ever get to the bottom of it?

Best
Lee

Yes , it had something to do with Console 1’s floating window GUI.

Never really got to the bottom of it but the bug was so massive it inspired me to move away from the console 1 ecosystem, and move towards using stock plugins wherever I can in my workflows!

That sucks. I doubt its Softube’s fault. I think its CB not playing nicely with Intel and/or Windows Graphics. Not an option for me to just ditch a load of third party plugins though…should be able to use Liqidsonics, Baby audio, Arturia etc

I’m going to put it to steinberg support but I’ve a feeling even if they confirm that’s the case they dont have a workaround for it and possibly/probably arent trying to find one if its related to this issue.

I’ll let you know if I make any progress with it.

Lee

@Coppolaman @GPnicolett Did any of you ever find a solution to this problem?

This same problem happens with various reverbs like Seventh Heaven, Tai-Chi and VSS3.

For me, it seems to always happen in a full template with loaded plugins such as kontakt.

Thanks!

Sorry never did. Moved away completely from Softube.

1 Like

I never did. It doesnt seem to happen all the time - not sure what triggers it - whether its project size (maybe something to do with available shared memory for graphics on a system without a dedicated GPU like mine) or combinations of plugins…my hunch is that under certain circumstances the ‘engine’ for a plugins GUI isnt initiated but thats just a very modestly educated guess. As it happens Kontakt isn’t affected by the issue but it does feature in the projects that are displaying these types of issue and it has shown other issues in the past - it has crossed my mind that its in the mix somehow. I dont regard it as rock solid thats for sure, which it should be from a Co. like NI. If you have built in Intel graphics as the OP and I do its probably the root cause somewhere.

I’m planning to ditch Windows soon and as it isnt hindering me that much (when it does I can usually resolve it by removing any/all affcted tracks and then undoing it ) I havent pursued it further. I might pull my finger out and take it up with SB if it ever gets more in the way though. good luck if you do the same and let me know the outcome…

1 Like

I stumbled on this one too. Here represents in some plugins that uses JUCE framework (or in combination with opengl) with mostly busy projects.

  1. Load freezing/locked plugin on any track (Here UVI shade locking)
  2. It freezes gui and you can see the knobs but when you try to move them it dosent graphically move anything and keeps gui frozen.
  3. When you close and open plugin again you can see that knob you previosly moved is actually set how you (blindly) moved in step2, and when you try to move another or the same knob it still looks locked until you again close it and open again. Basically you can see change only if you close and open plugin everytime.
  4. Audio normally passing through and nothing is muted, so plugin actually works since you can move knobs but its just looks frozen/locked.

happening with arturia pigments too(but the gui is white) and few other plugins mostly with JUCE framework.
P.S I tried to see if there is difference when i switch on or off open gl acceleration in UVI Shade, nothing works.

Does the same looks on your end too?

Can you try following:

  1. Check if you can turn off or on openGL for particular plugin (Softube has it)
  2. Turn off VST2 button from Studio/Plugin Manager:
    image
    Or just temporary move VST2 Plugin folder so there are no vst2 plugins loaded in project.

Win 11

1 Like

I’m on Win 10, Cubase 13, with a Nvidia RTX 3060.

I tried disabling OpenGL for Soothe2. The plugin does load the gui, instead of blank white, but I still cannot interact with the plugin.

I may have to substitute plugins until this problem is fixed.

Did same happens when you temporary move vst 2 folder so Cubase reads no vst2 plugins?

Did this happens on busy project?

I didn’t try moving vst2 folders yet.

And yes, this problem always happens on busy projects/templates