Initial post said that news will come in a few days.
It's been 2 weeks.

Considering how the first post and the VEpro page was written, i would have thought it would have been released already.

If you don't know what features you are adding for VEpro 7 by now, you never will. 

Can we get the new features list now please? And a ballpark release date? 

I am using it on a daily basis (release preview or what its called of Win8) and have no other problems than those i had in Win7.

In my oppinion it works just as good in Windows 7 as it idoes in Windows 8. Maybe even a bit better as i seem to get more free RAM in Win8 that in Win7.

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 :)

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

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.

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.. 

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.

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.

Still the same problem here, tho i havent been able to crash it on my slave yet, but the one on my main computer crashed after 10 minutes of normal music making.  So it triggering on the audio engine on/off might have been fixed but the underlying problem seems to be there still.

Edit: going to leave it going over night and see what happens.

Edit 2: ops, there the one on my main computer crashed again, by clicking on the audio engine on/off button. The slave server is still working tho, seems like its pretty stable at the moment.

I would like them to make it an OS too. People running VE on slaves usually only use them for that specific purpouse anyway. So why not create a very limited VEpro OS based on Linux. Or linux support (why on earth is there no linux support?).. either way is fine as long as i don't have to pay for an extra pro version of Windows just to run VEpro ^^,

And after they make it an OS, they can add the sequencer part, then you will have a dedicated audio OS and sequencer that is integrated with eachother for maximum performance and stability :)

Well, it would be nice :)

Super, thanks for the update!

Any news on the update?

Its been over 1 month since i first reported the error.

Best regards Øivind.

:(  i think small fixes and fast pushes rather than large fixes and slow pushes are better for everyone.

Where do i sign up for a beta test?  ;)  And a small feature request, make sure there is a crash log if the program hangs/crashes for any reason in the future :)

Anywho, thanks for the update :)

Sorry, im a bit restless Karel :) Do you know anything about a potential release date?

Got 2 weeks of vacation comming up and would love to be able to use this time to make some music :)

Ah thanks for the clarification Karel :)

I have updated the title of this forum post to better describe the initial problem that has been resolved. Hopefully this will also fix the problems you others are having, if not, hopefully those problems have come to light now that support has read these posts as they do seem very similar.

EDIT:

Removed my previous statement.

Thanks once again everyone for helping solve this problem :D

If you are lookig for a cheap Sequencer to use with VEpro, check out Studio One v2.

The Producer version is pretty low on cost and supports VST3 so you get the most out of VEpro.
And its fast, looks ok and have most features one would need. 

It might not be the cheapest or best sequencer out the, but for the price its very good.
And in my oppinion, its easy to get in to if you are comming from Cubase.

I think its under $250 for the Producer version. http://studioone.presonus.com/what-are-the-versions/ 

And its growing fast, great community and they are quick with updates and have tonns of videos with tutorials and tips.

EDIT: As civilzation 3 said, Cubase Artist is a good purchase aswell, and you can always upgrade to a better version of Cubase later if you need/want to.

This is very awesome news indeed :) Thank you very much :)

Allright, so, i have now recreated one of my templates in VEpro 4 and no craches, cant even force them with the Power Button trick. Its super stable with both Play, Spaces and Kontakt in the same instance. 

But once i load VEpro5, and even if i open the same VEpro4 metaframe, it crashes within 2-10 rappid presses of the power button, or if i just use it normally over a random period of time.

I even tried to limit the midi inns and outs, but that made no difference. 

Seems like VEpro5 really does not like Play or Spaces (play) at all on my system.

Thats all i have on that subject i guess ^^

VSL support was kind and sendt me a demo serial for VEpro4. I am currently testing it out with Play, Spaces and Kontakt running at the same time.

I have now been running it for 15minutes and have not been able to crash it. Will test more because it hasn't allways crashed instantly, but so far things might be looking up.

Will write an update later when i have some definitive anwser if it works or not, to bad you cant import VEpro5 metaframes into VEpro4 ^^

@civilization 3
I start/stop the audio engine to force the problem, the crash will occur anyway just usually not as fast. But the main reason i stop it is when i go to bed, so it does not use as much CPU power, keeping the electricity bill and heat down ^^ Bedroom musician hehe. But as i said before it does happen even if i don't play with the audio engine button, it just seem to happen more quickly when i do.

@DG
I did not know that Spaces was powered by Play, but i had a hunch there where similar code in it as they both crashes VEpro in exactly the same way. But now alteast we know that it seems to be a Play specific problem, or a perhaps even VEpro5 vs Play specific.

I could have lived with it if i could have 2 server instances of VEpro, one with Play and one separate with Kontakt, if it made any difference, but it hangs even if i only use Play, and half my libs are Play :/ What im going to do now tho is set up a server for Play and a server for Kontakt and use Spaces only inside my sequencer. So when it crashes atleast i dont have to reload any samples on the Kontakt server. That should atleast halfen my downtime.

@dlpmusic:
I might try and do some tests with VEpro4 if i can get VSL support to give me a version hehe, atleast then we can see if the problem is VEpro 5 and Play spesific.

Thanks everyone for chiming inn with comments :) I really appreciate it.

I just got an e-mail from the VSL support and they where not able to reproduce the problem. :(

I have contacted EastWest support now in hope of getting some information.

I don't know if its only PLAY but i had a hard time trying to get the same hang/crash with only Kontakt.

But the instance i but the plug-in Spaces on a Kontakt instance, i was able to crash it. And every time

i used an instance of Play (even a single instance) i was able to crach it withing 2-3 minutes. It might

be that Play and Spaces are in the habit of triggering the problem more rappidly than for instance Kontakt.

This was also on my slave so it did not become unstable because it was on the same machine as

the sequencer.

Ill report back when i hear from EW Support :)

EDIT: Im posting the tests i did. I also performed a test with Presonus Studio One v2, ended up with the same ressults.

TEST 1:
On the same computer as Cubase:
one instance of VEpro5 with only Play
one instance of VEpro5 with Kontakt and Spaces running. 

Slave computer:
one instance of VEpro5 with only Kontakt
one instance of VEpro5 with Play, Kontakt, Spaces and Fabfilter

It seemed to work fine, then i clicked on the Audio Engine button on one of the instances that where
on the computer that Cubase is on and it crashed, just like it usually does, but just this time it seemed 
like i forced it to crash rather it doing it randomly. I had 2 instances connected to this server and they 
both died at the same time. The Slave computer followed closely after and crashed within a minute.

Hi everyone and thanks for taking your time to answer.


I have an SSD for Hollywood Strings, but the main reason i bought VEpro was to not spend the insane amount of money on SSDs :)


As with dlpmusic, i never get a crash log either. When the sound stops (or midi info stops passing back and fourth) it only hangs when i try to click on the power symbol or try to open a vst. I can click on the menu or minimize/maximize the mixer, but if i click on the power symbol or try to open a vst it instantly goes white and then i have to force close it, there is no crash log except if its saved somewhere from VEpro itself. So it seems like we may have the same or a very similar issue.


Blaming PLAY is a valid argument hehe, and for more reasons than one, i would love them to start using Kontakt or have a Kontakt version. Tho as many of serious PLAY users probably use VEpro because their libraries are so huge, i find it weird that not more are complaining about it. I have disabled the SPACES plug-in (because older versions of it has been known to be unstable) to see if that helps, will report back later if it has any effect.



Will report the problem to now. Thanks again everyone :)

Update: VSL support have said that this will be fixed in the next patch. :)

Update2: I have updated the title of this forum post to better describe the intial problem that has been resolved. Hopefully this will also fix the problems you others are having with the Kontakt hanging and similar issues. If not, hopefully these problems have now come better to light with Karel from support reading these posts.

Problem:
After a time, either one or both of the VEpro instances will hang. When i click on a button in their interface the whole window wil go white and a Not Responding message will show in the header of the window. Then it just hangs like this forever unless i close the window and end the prosess. This is kinda irritating because it defeats the purpose of using VEpro when i have to reload all the samples 2-3 times a day on 2 computers. This can happen at any time, either after a day or a few hours, either when im making music or when im away from the computer. I have had this problem since i bought VEpro 5, and it has not gotten better with updates, not worse either. I have tried running decoupled but it does not have any effect. I have turned off that hard drives can go to sleep in the power options on both computers. It works perfectly when it works, but im getting really tired having to wait 20 minutes to load samples every time each of the instances crash. No error message is given.

If i disconnect the VEpro instance in Cubase when it has hanged on the other computer, Cubase will hang as well.

Anyone have the same problem or any knowledge to what could be the problem on my end? I have heard that running Play before Kontakt or the other way around is better or worse, but can anyone confirm that they need to be in a special order before i use 3-4 days setting a new template? ^^

Setup:
All drivers and programs updated.
Both computers running Windows 7 Pro 64bit.

Main Computer:
Cubase 6.5.1 (had the same problem with 6.5)
RME Babyface audio interface.
1x Vepro5 instance with Kontakt 4 and Play 3 instances, Fabfilter and Spaces effects added.
Using about 20GB RAM out of 24GB.
Core i7 950.

Slave Computer:
1x Vepro5 instance with Kontakt 4 and Play 3 instances, Fabfilter and Spaces added.
Using about 28GB RAM out of 32GB.
Core i5 2500k.

Thanks for any help you can give.
Sorry if the formating in this post is weird, this forum software is obviously very out of date and i have to use html brackets to make new lines ^^