When working with a Kontakt 8 VST, you can only use a Layer VST Instrument Editor one time. If you touch it a second time the Kontakt native editor will never appear. You must exit the VSTL session to use it again.
This was never a problem for Kontakt 6 or 7 and the VST Instrument Editor always starts the native editor for Steinberg and all other VST plugins.
NI may have altered their access method to call up their plugins. What can Steinberg do?
I have the same experience with a new Komplete Control version.
Workspace - user interface of a loaded plugin suddenly disappears. I have to reload the project, then it’s there again for some time.
This definitely needs a fix!
btw. Maschine 3, with its 16 inputs (mono) turns VST Live into buggy conditions, can not store any projects anymore, do not respond for some minutes and eventually shuts completely down (crash).
MacOS 13.7.1 - Komplete Kontrol 3.3.3 - PreRelease VST Live 2.1.29.263
Can you give me some hints about it? When does it happen? Do you know that an Instrument-Editor of a Layer will be closed if you select another Part?
We only have access to “Maschine 2” which runs fine. We are sorry if their new version turns VST Live into buggy situation. Give us some time to get access to “Maschine 3”. Meanwhile …
Yes, should not when it’s a shared layer? … think about this:-). First: NI did update Komplete Control to 3.3.4 because of some windows updating problems, I was checking new and what I see now is for some internal NI instruments inside the plugin window is: - the first time opening a plugin window with a layer everything is working as expected, second time opening - what I see is now is still a blank plugin window. Will try it in Cubase to observe behavior there.
Copying al layer resets the view and I can see the plugin inside the window again!
This was tested with Komplete Kontrol - Audio plugin.
You’re doing it right, Spork. Thanks for your help jrose.
The VST Instrument editor will usually bring ukp a Kontakt 8 plugin only once per session, but sometimes more than once.
BTW, I’ve never trusted using the Red X to close an open plugin. I always use either of the two Virtual Instrument Editor icons in VSTL. If you have tested that it is indeed the same result either way, you can let me know. I happen to know that it is a completely separate handler from C++ Windows code, so the developer must ensure that all relevant code for a clean and complete plugin editor exit.is called for either the VST Instrument Editor or the (Windows) Red X.
It seems that Instrument Editor is now working as expected after a complete Windows 11 Pro update from old 23H to the very latest version of the operating system. Therefore, I think I was wrong to assume that NI may have altered anything on the critical path that loads a performance view.