Inserted plugin windows taking much longer to open with single click

Cubase
1

Hello,

Something weird happens in Cubas 15 for me where if I single-click an insert, the plugin’s UI takes from 3 to 5 seconds to appear, whereas if I double-click the insert (or CMD+click) the UI opens immediately. This makes no sense to me.

Is a plugin window supposed to open when single-clicking or double-clicking on its insert button? From the manual I would assume single-clicking since it doesn’t mention double-clicking anywhere but if this is the case why is it so slow to open compared to double-clicking?

As it stands, it seems plugins open either way, by single or double clicking, but single clicking is way slower.

Am I missing something here?

Thanks!

2

Confirmed!
Wow, that´s weird, never paid that much attention.

3

Hi,

This is a known topic. It has been discussed here on the forum already. The same speedy plug-in GUI load happens if you Shift+click.

As far as I remember, the difference is that the double-click (and the Shift+click) loads the GUI first (or it loads it asynchronously). But the regular single-click loads the plug-in first. After everything is loaded safely, the GUI appears. So this is the safe way of loading.

6

Hi Martin, thanks for the reply.

I must say, I still find the behaviour strange. I think it’s reasonable to assume not all plugins take the same time to load - depending on the complexity, RAM usage, etc.

I tried opening what I assume are “lighter” plugins, including StudioEQ from Steinberg and it still takes too long to open in the “safe” way.

It just seems way too much CPU overhead associated with loading a “light” plugin. Also, and I realise this type of comparison is always annoying, but this is not my experience with several other DAW’s.

Sorry, I don’t mean to be destructive here, but why is the “safe” way to open a plugin so slow in Cubase?

Wouldn’t be more logical to have the “fast” way be the default without having to either double-click or SHIFT+Click?

Thanks

7

Hi,

This comes from the development safety logic. First, you have to load and start everything properly, then you can show the UI, so the user can operate. If you do it the other way around, the user can work on some parameters, which are not associated/loaded yet, which can bring issues (even crashes).