Could you please also open up the "Console" application, goto "User Reports" and copy any crashes from "pluginscan"?
Please send to me at [email protected] - I'll have a look.
I have VEPro7 on two Mac slaves and a third instance on my PC master with is also running the latest version of Cubase 10. Before installing VEPro 7 Cubase hardly ever crashed. Last night it crashed at least a half dozen times when just trying to do a simple midi edit. Anyone else experiencing DAW problems that may be VEPro7 related? One step forward, two steps backward...
Smart, and as you know, there's the leading edge and for early adopters there's the bleeding edge...This is why I'm holding off this time until the bugs are sorted out. I immediately upgraded to 6 when it was released, only to discover it deleted all of my DNS settings. VSL reeled the update patch a couple of days later, but I learned my lesson the hard way. Let us know if you get it sorted out.
I have VEPro7 on two Mac slaves and a third instance on my PC master with is also running the latest version of Cubase 10. Before installing VEPro 7 Cubase hardly ever crashed. Last night it crashed at least a half dozen times when just trying to do a simple midi edit. Anyone else experiencing DAW problems that may be VEPro7 related? One step forward, two steps backward...
I installed 7.0.778. I have Kontakt 6 player and Kontakt 5.8.1 full version. They both passed the scan on install, but only Kontakt 6 is showing as an available plug in. I haven't yet checked every other plug-in from the VST folder but most seem to be present. However at the moment I cannot access any of my Kontakt instruments that require Kontakt full version.
This sounds like a variation on my issue. All I can suggest is to open a ticket and pass the the details and your plugin log - you can find that (if you are windows) by putting %appdata%\VSL\Vienna Ensemble Pro\logs into the Windows search bar, and the file is called pluginscan.txt .
I installed 7.0.778. I have Kontakt 6 player and Kontakt 5.8.1 full version. They both passed the scan on install, but only Kontakt 6 is showing as an available plug in. I haven't yet checked every other plug-in from the VST folder but most seem to be present. However at the moment I cannot access any of my Kontakt instruments that require Kontakt full version.
I've tried a reinstall and a re-scan, but the result is the same. Any advice on what to try?
and the promise of Wake On Midi to come, outstanding.
Yes, this is exactly what I have done after reading the pluginscan log and seeing instances of Kontakt 5 "destroyed". Vepro seems to get Kontakt dll instances confused. Anyway it is a workaround for now.I have this problem occasionally with VE PRO 6....the only work around I have found (as dumb as it sounds) is to make a new folder where your Kontakt plugin resides and then put the Kontakt plugin inside that new folder. Rescan or relaunch VE PRO and you will most likely see the missing plugin. Unfortunately you have to leave it in that new folder. If you take it out and put it back in the old location it will not show up again.
yea? That will be kind of major if so...