Same problem in 4.0.6150. Could not load plugin if Kontakt 4.1 instanciated as a last plugin in the chain.
Workaround is to load a "ghost" Vienna Instrument at the end.
But it's just a workaround.......
-A
182,893 users have contributed to 42,261 threads and 254,944 posts.
In the past 24 hours, we have 0 new thread(s), 10 new post(s) and 44 new user(s).
I am also having this problem when I load up a new project in DP7.2 (and all the previous version of DP) using the latest VE Pro. It only happens when I'm actually loading the DP project with VE Pro open. And if I have another K4.1 Player, only the first instance says it cannot load the plug-in. I'd be happy to send a console report. Please let me know if you want me to.
Interestingly, a way around this problem is to save the metaframe and open VE Pro and the saved metaframe AFTER the DP project is open. When I do that, the metaframe loads just fine. But it is a hassle.
@anton said:
Same problem in 4.0.6150. Could not load plugin if Kontakt 4.1 instanciated as a last plugin in the chain.
Workaround is to load a "ghost" Vienna Instrument at the end.
But it's just a workaround.......
-A
Make sure Kontakt Memory Server is OFF. Also, in a host, do not use multiprocessing option in Kontakt.
Also, if you are instantiating Play engine, it has a memory server and the two memory servers on OSX will probably not work together. It will crash at the last instantiation of one or the other, was my experience.