Update: Still the same problem in Win8.

I have installed Windows 8 Release Preview on my main computer, and VEpro 5 has been stable with no crashes for 2 days now.

So for those who are in the same boat, this might be worth checking out. I have not had any other problems, other than that i had to re-install the e-licenser software after the upgrade to Win8.

For me everything else is working right out of the box, iLok, Cubase 6.5, RME drivers aso. Also freed up a bit of HD space after running the disk cleanup tool, removing the old windows install and old windows install temp files, and a bit more free RAM.

I am a happy music maker once again :)

Tho Windows 8 is still in beta/pre-release or what one would call it, i have not had any issues yet, but you can not roll back to windows 7 once you update.

I´m not changing to another operative system because of the malfuntion of one update.

I just can´t bealive that after all of the time we take writing to the department support acknowledging the problem, they just simply make a new release without even mention about the problem.

For those who want to work with the system normally, please go back to the update 5.0.10370 you will be able to load projects from more resent versions.

Please keep update if Vienna decide keeping giving support to there users and solve this problem.

Update: Still the same problem in Win8.

I hear you, tho i have given up waiting for a update that works, after days of testing on several computers and over a month of lost production time, i'm just glad that i can make music again.

I see, I have done an upload to my droopbox if you want you can download it from here

Copy de link bellow in your browser

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

Best

Francisco

@sacrenouille said:

Where can we download update 5.0.10370 ?

seems like i spoke to soon, just got the same problem crash/hang in Win8 now. 

i gievs up.

Still stable on my slave tho.. 

I don't what to say other than I am running Play 64 bit with Hollywood Strings, Hollywood Brass, and Hollywood Orchestral Woodwinbds in VE Pro 5 ( 7 instances) from an SSD on my slave PC and it is running like butter, connected to Logic Pro on my Mac. 

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?