Forum

I know a number of you are using Native Instrument's Kontakt 5, hope you have an answer for this.

I can get EigenD VST/AU slots (Alpha) to open Kontakt 5 and load the first instrument with no problem. But when I try to close that instrument (using the Kontakt GUI), it locks up the program (EigenD immediately goes "idle" on Windows 7 machine, with spinning beach ball in Lion on new MacBook Pro.). I.e., I can't close a piano sound and open a guitar sound--EigenD freezes/crashes.

I'm using Stage to interface, of course.

I CAN go back to Stage, click on Browse, select Native Instruments, select Kontakt 5, and safely get a blank instance of Kontakt 5. Then open the GUI in Stage, and load an instrument... This works fine, even though this process means I never shut down either the earlier running instance of Kontakt, and also didn't unload the previously running instrument. But, it works anyway. (Though I may / may not be generating an enormous drain on memory-- I can't tell, and I have 16 Gb of memory in each of the machines, and the samples are loading off of SSD or USB 3 drives, so maybe it just isn't showing...)

Obviously I just want to be able to change instruments in K5, or add a second simultaneously sounding instrument, the way K5 is designed to do.

I've confirmed identical behavior under Windows 7 and OS X Lion, and identical behavior under EigenD 1.4.12 Stable and 2.0.58. I've also confirmed that K5 works as it should as stand-alone on each platform (so probably not a hardware problem here), and that it works as it should as a VST plug in other hosts in Windows 7. Also confirmed that EigenD allows program changes for Alchemy, (which doesn't load samples), and that it properly allows program changes / instrument reloads for Omnisphere, which does load samples...

Those of you who are using Kontakt--how are you changing Instruments?

Thanks!

JD

Keyman is totally right about this. I just want to add a technical remark here. What the tail time parameter does is turn off the processing in the AU/VST plugin when the tail time has been exceeded. This can greatly reduce the amount of CPU usage that EigenD consumes by only processing the plugins that are actually in use. Certain plugins sadly tie their GUI to the actual audio rendering that the plugin has to do, meaning that if you stop rendering audio, you essential stop the GUI also. The NI plugins are especially prone to this. So you either change the tail time for that particular AU/VST agent, or you send it a signal (like a key press) to activate the plugin and in this case also the GUI.

Take care,

Geert