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