CUBASE PLUGINLERI SOFTWARE
CUBASE PLUGINLERI PSP

CUBASE PLUGINLERI SOFTWARE

In particular, plugins (and any support software they use) wouldn’t be likely to be cached in memory the first time after a boot, but loading them a subsequent time after that boot will likely have them cached in memory. The reason I ask is to rule out any additional first time startup overhead for loading a plugin after a reboot. One sanity check on your tests, though: Were these tests both done after a clean boot session or, if not, were they at least done after having loaded the plugin in question in one of the versions of Cubase, then close that version of Cubase and run the tests in each of the versions. I have not done any comparison tests on my system in this area (and really haven’t gone back to Cubase 11 since starting with Cubase 12). loading a different kit in Superior Drummer 3), but I haven’t noticed that recently (at least in 12.0.20), though that could also be because I’ve treated this sort of area as walking on eggshells and only made those sorts of changes with playback stopped. Early on, I was also seeing some hangs when making major changes in some plugins (e.g.

CUBASE PLUGINLERI PSP

until killed with Task Manager) on loading a plugin (I know one time was PSP InfiniStrip – I don’t recall if that was in 12.0.10 or 12.0.20, and that plugin usually loads with no problem). I have a few times, however, had Cubase 12 hang permanently (i.e. I can’t say I’ve noticed any difference here between Cubase 12 behavior (in any of the three versions to date) from Cubase 11 behavior. One other possibility could be, if it is the first plugin load of a specific plugin in a bootup session, and your plugins are on hard disk (like mine), and the first load is slow but the second load of that specific plugin is fast, the difference between having the plugin cached in memory versus having to be read off hard disk. (PSP uses iLok, but the others use their own mechanicsms.) I’ve also seen this with non-Waves plugins, such as Arturia, NI, and maybe even PSP Audioware.

if you were to load SSL EV2) may need a different authorization. I strongly suspect it has to do with software protection, where one authorization is needed for a specific set of plugins, but another set of Waves plugins (e.g.

For example, let’s say you load something in the CLA collection, maybe first the vocal plugin, which takes a very long time to load, then the mixdown plugin, which now takes a shorter time as do further instances of the vocal one. It’s not necessarily the first time loading a specific plugin, but rather the first time loading a plugin in that specific group of plugins, at least in the Waves case. I’ve seen the sort of thing you’re talking about, as well.

Cubase pluginleri