As of the latest couple of versions, VEpro5 running on my slave computer has been rock solid. 

The On/Off audio engine problem is gone.

I do however still experience crashes with VEpro5 running on my main computer, where i run Cubase.

Its a great improvement, atleast for me.

EastWest is releasing Play 4 this month, or perhaps early next month, hopefully this will fix the rest of the problems.

I will post my findings when i have any new info.

Please just have in mind that the version 5.0.10370 is working completely stable, there are not hapening the " (not responding) error "

working with cubase on the same computer.

This problem are happening within the later vertions of vienna ensamble pro 5.

and this is not only hapening with play from East west, I also experiment the problem without opening play, with other VST instruments like Omnispher.

https://dl.dropbox.com/u/4366697/ViennaEnsemblePro-WIN-5.0.10370.exe

@anotherzen said:

As of the latest couple of versions, VEpro5 running on my slave computer has been rock solid. 

The On/Off audio engine problem is gone.

I do however still experience crashes with VEpro5 running on my main computer, where i run Cubase.

Its a great improvement, atleast for me.

EastWest is releasing Play 4 this month, or perhaps early next month, hopefully this will fix the rest of the problems.

I will post my findings when i have any new info.

Sadly it does not work any better on my system, this version crashes just like every other version of VEpro5 does.

This is very extrange! why it work for me then?

I hope you found a solution

@anotherzen said:

Sadly it does not work any better on my system, this version crashes just like every other version of VEpro5 does.

Indeed, tho as it does work on my slave computer, i might save up for another slave and move the libraries from my main computer to slave #2. Expensive solution but, atleast it will most likely work.

Thanks for trying to help, its very much appreciated :)

 hate to keep bringing this up.....but VE PRO freezes up on me EVERY DAY across multiple machines with Cubase.  I am going crazy.  Every time I export or quit I have to hold my breath if Cubase will lock up because a VE PRO is frozen.

Is NO ONE else having these problems???   I did not have these problems with VE PRO 4.  I do not ever have any freezes on my local VE PROs running behind Cubase on my main machine.  I might not even have any issues with the 32 BIT servers....but EVERY DAY on multiple machines in 2 separate studios I have to force quit VE PRO servers and reload the machines.   NO ONE else has these problems????

are you using dynamic IP?

All machines are assigned a fixed ip.

Hi,

In the past couple of versions of VE Pro 5 I am experiencing a similar issue. After a period of inactivity Cubase will generate midi, the activity light will flash on the VE Pro plug-in but no midi is received at the server end. I am using 1 instance locally and no EW products are included anywhere in the set-up. I have a fixed IP address.

If I attempt to play an instrument in Kontakt using mouse and keyboard no sounds are generated (as if the server is not connected). The server interface shows the 'slave' to be connected - the server instance shows as connected to localhost as does the instance and the instance GUI is responsive - just doesn't receive midi or instruments make sound. Both Cubase and VE Pro are capable of saving.

After that, the symptoms are the same - any attempt to switch engine off and on and so forth will cause both Cubase and VE Pro to crash. If I attempt to disconnect, Cubase will crash. If I hard quit Cubase and re-open the project file, force disconnect the VE Pro server in order to reconnect, both Cubase and VE Pro will crash on attempted reconnection.

The only solution seems to be to force-quit both and re-open the project from scratch. As there have been a couple of updates to Cubase during the same period and I have added new plug-ins there could be a number of causes - but VE Pro is where the symptoms are produced.

Yes......exact same behaviour.

i have been trying for several years to figure this out.

question.....

i think I possibly have it pointing to Kontakt 5 or something on my network.

Do you run Kontakt 5 on the slave machine that is crashing?

i run 2 different main servers accessing different slave set ups.  Do you run more than 1 setup, i.e., more then one main server machine?

By the way I am using Cubase on a PC .

Hi,

I am using Kontakt 5 in all my projects, although for me the problem is more recent - I certainly didn't have it in say the Sept 2012 version of VEP5, but I suppose it may co-incide with Kontakt 5.1 which is about the same time period of the last couple of VEP updates?

In the case I'm talking about, the problem occurs more often in the instance loaded on the DAW not on a slave. I do use slaves sometimes, but I don't recall having had this problem with a slave based VEP server - always seems to be local and always after a period of inactivity (never had it happen while working).

For me it seemed like it started with VE PRO 5.... However that was also about the time Kontakt went to version 5.  I have never had this happen on my local machine which does not have any Kontakt instruments, nor has it ever happened on any slave that does not have a Kontakt instrument.

it appears that we both use Cubase and Kontakt.  I have been trying to solve this for a long time.  It can happen while I am working or after periods of inactivity..no real pattern.  I have several slave machines and it seems like one goes down another will follow shortly.  I then have to force quit out of the ve pro on the slave machine reload and reconnect.

Vienna does not seem to be trying to investigate this as There is no pattern to recreate it on a consistent basis.

David,

Can you tell me how many machines are in your network, i.e., Do you have just one setup (1 master + several slaves, or do you have more than one master on your network-2 complete setups, etc...?).

I have been trying to solve this for a long time.  I do know a couple other guys having this problem and we all have either Cubase or Nuendo with the crashing machines running Kontakt 5.

Thanks,
Danny

Hi Danny,

Barring disasters, I operate a set up that includes one master and three slaves (though I only need all if it's a big orchestral cue with choir and sound design). However, as I already said, I get the problem just running the master PC on its own.

VEP 5 and Kontakt 5 don't seem to play quite so nice together as the version 4s did. They have both made some architecture changes which, as the issue with Kontakt reloading samples when you first selected tracks demonstrated, these have introduced the potential for new conflicts. Of course, as I understand it, you have been having these issues since before those versions were released.

Since Cubase 7 I also have Kontakt issues where instruments spontaneously transpose without showing any settings changes, in Cubase 6 - that used to spontaneously transpose even when the transpose insert wasn't active. And all versions randomly zero the main volume on Kontakt instruments unless you set them to ignore incoming volume & pan messages.

Having said all that, I wouldn't be at all surprised to find that the culprit was Windows! ;-)

I don't know about your midi pan/volume, etc... issues ...I have never seen that.

I can definitely tell you that this never happend in VE PRO, but like I said before that could have been pre-Kontakt 5.  I really wish Vienna would look into this as I struggle with this EVERY SINGLE DAY.

You are the first person to post that has the exact same problem as I do.  I know several others that have the problem b ut do not post in this forum.  If others have this problem I would love to knopw as it would help to get Vienna to look into it.

A couple more observations.....

I have 6 slave machines.  2 of them do not have any Kontakt's and they have never crashed or froze up. 2 of them have a lot of Kontakt 5's and freeze about once a day.  1 of them has a few Kontakt 5's, lots of Kontakt 4's and freezes about once a week.  1 of them has maybe 1 or 2 Kontakt 5's, lots of Kontakt 4's and freezes every now and again.

It seems obvious that the more Kontakt 5's on the machine inside VE PRO 5 the more frequent the crashes.  The crash once again is no audio or midi  coming from that Vienna project.  The transport play button still functions but nothing else.  If I try and turn the project off Ve pro goes all white and locks up.

I believe Cubase is part of the equation as I am not sure I have seen anyone have this problem that does not use Cubase.

This has been a problem for over 2 YEARS......I wish Vienna would chime in and take this serious and try to solve this. Telling us to contact Native Instruments does not seem to be a solution....Vienna needs to figure out what is going wrong.

Teh fact that you are having a problem with it on your specific rig does NOT make it "a faulty application", it just means for some reason or combination of reasons there is a problem on your specific rig.

i use it daily on my Mac AND my PC with no problems.

I just wanted to chime back in on my VE PRO "freezing" problems.  To recap I would "sleep" all my slave machines rather than shut them down every night.  I have 5 slaves at this point.  2 of them do not run Kontakt and never freeze.  The other three would freeze with in hours once the first one exhibited the problem.  All needing a restart and reload.

By chance I read something interesting in a Kontakt scripting forum that lead me to believe that certain scripts are always counting the amount of time running, but it sounded like there was a maximum amount that Kontakt could keep track of in the scripts before it reached its maximum.  I suspect certain scripts running after a period of time hit this maximum and cause VE PRO to freeze.  I since have thrown in the towel so to speak on sleeping these machines and restart and reload everyday.  It has been a couple of months and not one single problem with VE PRO freezing anymore.  For me I concluded this is a Kontakt limitation not a VE PRO issue for what I was seeing.