So frustrating....I can not cause it to happen on demand but when I lose audio/midi on an instnce it is the same basic behaviour.  It definitely never happened on version 4.  I have a second room with a similar set up and my assistant has not had the issue yet even though we have very similar set ups....although he has not been terribly busy lately to give it a real good observation.

Hopefully more people can chime in and help identify this.

@dlpmusic said:

This time I think Play has nothing to do with it as I am mostly using Kontakt and believe to be having the exact same problems.  I am almost sure we are having the same problems when you mentioned the "power" button can freeze VE PRO.

I had 2 machines yesterday have this problem......incredibly frustrating to track this down.  I hope the VE PRO programmers can figure this out.

 However, judging by your test, it is PLAY that is causing the crash every time. Two things for you to realise:

1. Spaces is powered by the PLAY engine
2. By having Spaces and Kontakt in the same instances you are in effect putting Kontakt and PLAY in the same instance. Not  good idea.

DG

that is just what I noticed as well. I have had to isolate Play from Kontakt. At one time if I had to have K3.5 with its memory server running, Play's MS (which you can't kill) meant a no-go, period. I don't use Play hardly at all and I'l glad my investment in libraries using it is minimal.

Beyond that, if 'power button' refers to stopping/starting the audio engine, why would you do that?

one other thing to look at per inexplicable loss of connection is a dynamic IP setting.

@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 want to also add that when I have loss of midi/audio on a particular slave pc that it usually is just 1 instance inside a bigger metaframe.  In other words I might be running 2 or 3 instances with about 14-16 Kontakts in each one.  When I notice I am not getting audio/midi on one particular instance usually the 2nd instance with in the same metaframe is still working.  So this makes the problem even more confusing as VE PRO 5 obviously has not crashed and the network is still functioning.

I see that several of you are able to cause similar behavioour with EASTWEST PLAY and SPACES, however I do not use either on my machines that have the problem.

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

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

This issue has been fixed for the next update. We'll do our best to release it as soon as possible. Apologies for the inconvenience.

FANTASTIC news.  I have been reporting this problem for a long time saying that I did not believe this ever happend in VE PRO 4.  I am glad the "PLAY" folks were able to consistant ly show the problem.

Now if you can fix my multiple instances of Halion 4.x VE PRO would be flawless for me.

Thanks for the fix....I can't wait to get it.

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

The solution only applies to the crashes when starting/stopping the audio engine with Play in the project, but may extrapolate to the strange hangs as well. Just to avoid potential disappointments.

I hope that this fix actually fixes my Kontakt hangs, as I stated before that this did not happen at all in VE PRO 4.

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

Support would be me for this particular case. The support case is not closed. I just replied in this thread instead because I knew it was you :).

Ah thanks for the clarification Karel :)

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

Some larger changes are currently being tested, which prevents an immediate release, but we're doing our best to get it out there as soon as possible. I'm sorry for the inconvenience.

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