K4 is still crashing VEPro when reloading a project in Win7 64bit.

I allready have, and they don't care! The moment I run a VEPro server application, any project with K4 and some string patches in it I relaod K4 crashes.

In former versions of VEPro Play runned perfect. But since 4881 I can't use any button on the Play GUI. Like the ongoing K4 crashes this is very bad!!!

On Win7 64 K3.5 works pretty good in X64 mode with VEPro unlike K4 that don't.

Same goes for K4.05

I turned it off because Steinberg recommends this for the use in C5. But my K4 won't run correct with VEPro, always crashing. If you run K4 in standalone mode then multicpu is better turned on, but as plugin, turn it off.

Even with VEPro 4881 I can't reload any project with a Kontakt 4 plugin in it. Starting VEPro Standalone and putting a K4 instrument in it and load some patches is no problem, everything is fine. But then I save the project, close VEPro, start VEPro again and try to load my VEPro project with more then two patches loaded in K4 and K4 crashes and with it VEPro standalone. Another problem : I can't even reload a Cubase5 project with a K4 in the VST rack when a VEPro server is running in the background. As soon es VEPro is running, any kind, a project in which I used K4 is not reloadable!

Still K4 causes VEPro (32 and 64 bit) to crash after reloading a saved project on Win7 64bit

In the NI forum a user said it my crash only appears in the 64bit version of K4.

Kontakt 4.03 is not working at the moment. Crashes VEPro on Win764 after reloading a Cubase 4 project!

4.0.3 din't solve the problem for me either. K4 is still crashing when reloading a Cubase4 project with VEPro.

I too have extreme problems with Kontakt 4 as a plugin in VEPro 64bit 4686 running on a Win7 64Bit slave. My master is a WinXP 32bit machine running Cubase 4.


When I'm loading a C4 project on my master in that I used Kontakt4 in VEPro (connected via the VST3/VST2 Server Interface Plugin, happens on both) either Kontakt 4 is playing no sound or in the worst case crashes completely the VEPro Server. It is so frustrating.

And why doesen't work Wordbuilder/k3.5/SC with the VST3 version of VEPro. Any VSL statement about this? MS any? This is important.

In C4 I have already Play issues with the Vienna Instrument VST without VEPro, if I load up the Vienna Instrument VST first and then the Play VST. So in VEPro if yo load the Vienna Player, or not delete it because it is the first instrument loaded, you will have problems running Play. First load up Play then the Vienna Instrument and everything works fine. And yes I'm running VEPro over lan with a winxp32 master and a win764 slave.

For me Play works fine even with VEPro. Im using VEPro with EWQL pianos on my Win7X64 slave and have no problems with it. These pianos are too big for my 32 bit main-DAW.

Ok I found it out: It is not working with the VST3 version of the VEPro server Interface VST plugin. With the VST2 everything is fine even with the Choirs coming from my slave computer. Can someone from VI check on that. Which plugin do you use Ralf? Anybody knows why? I'need the VST3 because the VST2 has only one midi channel!

How come it dosen't work on my system? I'm using K3.5 too in VEPro. How'd you set up your VEPro?

Has anybody Wordbuilder/SC running with VEPro?

Even if it would run on a x64 computer, VEPro dosen't support midi plugins dosen't it?

So I startet a new Cubase4 project only on my winxp 32bit master with a VEPro server on my master so that the winxp master is master and slave at the same time. Same problem: the midi signals arrive at the K3.5 instance in VEPro but no sound is playing. It dosent matter where your samples are. Somehow the midi data arrives wrong on VEPro or ... I don't know


I'm trying to use my slave computer for choirs with the non-play kompakt library of ewqlsc.

Master : WinXP32-->Cubase4->VEPServerInterface->miditrack-Wordbuilder

-------------->LAN/Crossover Cable-------------->

Slave : Win764->VEProserver32->Kontakt3.5->BoysWBMulti

It should work. But it doesn't even run on a single x32 machine so the problem has nothing to du with WB/EWQLSC not running on X64. Mayby I have some setup mistake I'm missing. But everything works very good with all the other plugins even Play.

Master: WinXP32, Cubase4

Slave: Win7 64Bit / VEPro 32Bit w K3.5 32bit

I've tried to get the old EW wordbuilder to run over VEPro. Slave instance of Kontkt 3.5 with a WB multi and the wordbuilder midi plugin inserted in the corresponding midi channel on the master in Cubase4. But no sound is coming. Does anybody know something about this issue?

Is it 4 GB (old limit) for the 32-Bit server service app or 4 GB for each VEPro instance running on the 32Bit server service app?

I tryied Lennardigital's Sylenth1 v2.2 from a master and a slave instance and it'is running pretty well through VEPro. WinXP32, Cubase4.52

Nice would be a favorite mount of a specified metaframe in the VEPro server application at startup.

I already mailed the issue to the vsl support and got a ticket from Martin. Let's see if he/they can track down if that is a bug or if my system is just messed up. I'm also using C4.52 and that error seems only to occure with the VST3 plugin. It is neccesary because I will change up m workflow back to the cubase VSTRack and multitimb. And I like VST3!