@brett said:

Thanks Karel for your reply.  I'm using xp64 and cubase4 on a PC, with VEP only on my local computer.  No slaves.

Load VEP server 32-bit.

Load Cubase4

Open a new Cubase project

Instantiate a single VEP from the VST instruments rack

'Connect' to localhost [32] (new)  - I'm not naming the preserved session which means the VEP instance is connected to the host and not preserved

Save the project

Close the project

Re-open the project = crash! (exception in vienna ensemble pro.exe)

In contrast...

Load VEP server 32-bit.

Load Cubase4

Open a new Cubase project

Instantiate a single VEP from the VST instruments rack

'Connect' to localhost [32] (new) and either name the instance (automatically preserving it) or don't name but then preserve.

Save the project

Close the project

Re-open the project = No worries.

[edit - however, if you shutdown the VEP 32-bit server, or delete that preserved instance of VEP after closing the cubase project, and then re-open the project, this will force VEP to load with the project and cause a crash similar to the first example above]

(Also, the problems with cc-instensive patches like the legato LASS patches is not fixed here - I've detailed this in the LASS thread)

Thanks Karel - Brett

Karel - Did you manage to test the above repro?  It happens everytime here.  If I ever load up my current project which had been saved in a disconnected (non preserved) mode, the 32-bit version of the server crashes on load while the 64-bit is fine.  However if I had previously saved the project with all instances preserved, then loading the project (after loading the metaframe files) there is no crash.  This is a 'once a day' problem - I just have to remember disconnect, and to save the meta files for both 64 and 32-bit server versions at the end of the day otherwise my first load the mext morning results in a crash

XP64 with Cubase 4 here - Thanks

Brett

@Karel said:

Yes, I could not reproduce this. I assume you're using Cubase 4.2 or newer when using the VST3 plugin? Cheers.

yes, I'm using the latest release of Cubase 4 and the crash occurs with both the VST2 and VST3 version of the plugin.  I don't know what's unique to my system.  I've tried removing VST plugins from the scan path, and every combination of preference settings.  All I know is that if Cubase tries to load up VEP in the 32-bit server it crashes the server.  The only way I can get it to work is to load the meta file (if I remember to save it) and then connect manually after the cubase project has loaded.

This behaviour was not evident in the previous build.  Can you offer me any troubleshooting suggestions?  Any ideas to try?

Brett

It's happening here with C5.1 (32bit DAW) as well (VEP 64bit Slave). If I load a previously saved project with a preserved instance it loads all samples and when it's done, VE just goes away for good.

So basically the first fix mentioned in your changelog is causing this or at leat seems to be the reason. Since it didn't automatically load in VEP's previous build ( we had to click Load Plugin Data manually) it never occured there.

No problems if I load an .mframe or .viframe first.

@MaD, it sounds similar to my difficulties.  I'm on 32-bit Cubase 4, XP64 but for me it's only the VEP 32-bit server that crashes, VEP 64-bit is fine.  I wonder if it's an XP64 OS thing?  I'll swap to W7 in time but for now all I know is that the crashes aren't evident in the previous VEP build with my combination of OS and DAW.

Brett

Brett (others) - How is this latest build working for you now?   I have the original working solid (master and slaves all running x64) - a little afraid to update fearing any negative change.  Like the new 'features' but not at the cost of stability.

Thanks for your reply.

Rob

I have great respect for the team at VSL, and for VEP which is a wonderful product and a welcome replacement for FXT.  However, for those of us experiencing problems with the latest build on XP64 I think we're stuck with it.  Paul correctly pointed out in this thread http://community.vsl.co.at/forums/t/22729.aspx?PageIndex=3 that XP64 is an unsupported product, disappointing as this may be.  Something has broken between builds for some of us but that's unlikely to be addressed.  Switching to W7 when it is released (23rd Oct I believe here in Australia) is the only way I'll know if the VEP crashes are OS related, but porting over to a new OS is no small task for any of us.  There was no way I was going to Vista.

Brett

Brett, I'm working on XP64 and am getting no crashes at all. If you like you can give me a repro to do, and then if I don't get a crash, we can see what the differences between our systems are.

DG

Thanks DG, that would be great.  My repro is about 9 posts up from here [:)]

it's only the VEP32 server that crashes upon loading.  I can load up a metaframe and connect manually OK, but anything that forces plugins to load within VEP32 while loading a Cubase project causes the VEP32 server to crash.  VEP64 is fine though.  (I'm in 32-bit Cubase 4 latest, XP64, VEP on host machine).  I also still have problems with the LASS legato patches and you can follow my tests in the LASS thread if you wish.  For now not preserving my VEP instances is my workaround there unfortunately)

Brett

I'm not on XP64. Have been using Vista64 but am now running Win7x64... and got those problems. It's not an XP64 thing. Must be something else entirely. Oh and obviously I've only used the 64bit server.

Hi Karel.  No, it doesn't matter if there are any VSTi's loaded or if the VEP instance is emtpy I still get the crash upon loading of any Cubase project that forces VEP32 server to load it's VEP instance with it (repro above).  Are you trying this in XP64 on Cubase 4 or in another OS? (I know that XP64 is not supported).  I'm also using VEP32 locally - no slaves at the moment.  If someone could confirm this is an OS thing I'm fine with that, but something has changed between builds.  I'm also happy to accept that this is something unique to my setup (although others above have described similar problems), however as I mentioned earlier the VEP32 server crashes I experience do not occur with the previous build.

Thanks for taking a look Karel - Brett

@Another User said:

Regarding your LASS  problems, is it LASS or is it Kontakt? Is there any way to narrow this down? I don't have LASS, but will test with The Trumpet when I have more time.  FWIW I use lots of CC with Vienna Instruments (up to 8 different controllers at a time as well as 2 keyswitches) and haven't noticed any problems. Maybe it's the scripting that is not working properly?

Is it LASS or Kontakt or VEP?  No idea.  Generally if I don't preserve my VEP instances and therefore stay linked with the sequencer I don't have problems.  However if for example I save with all VEPs 'preserved' and load the project file the next day then the LASS scripting appears broken. My current cubase project file is a large one, encompassing many cues spread of over a 2 hour film.  Oddly, if I start a new project with only a couple off LASS legato patches, the above behaviour cannot be reproduced.  I don't know if this is to do with the complexity of the project or because I started this project using the previous VEP build, however with my current project, the above behaviour is reproduceable.  However, as I mentioned in the LASS thread I'm not entirely sure that LASS and or Kontakt is isn't at least part to blame as very occasionally the scripting breaks mid session.  There are a couple of threads on the LASS forums where this has happened to users in Bidule also.  However, the fact that here scripting 'breaks' depending on whether a project was connected or not to VEP prior to saving suggests that there is some interaction with VEP....or something...

There's one other thing - could be nothing but the chorus on one of the NI Elektrik pianos I'm using always weirds out when I load the previous night's project.  The frequency of the chorus effect doesn't save properly and always re-loads to fast.  Just a little oddness that I never noticed with FXT (not that I'm mourning FXT mind you!)

Of course, XP64 is not supported so perhaps all the above is due to that..

Brett

@DG said:

 OK, I can repro your crash here. I obviously never worked that way before....!

It's good to know I'm not crazy!

You have me intrigued though...How do you work?  Do you load the metaframe first?  Are you always 'preserved'? How do you avoid the crash?

Easy. I don't usually use the 32bit server. [;)]

DG

@Animus said:

And I am not preserving instance, it's loading up when loading a Nuendo project.

Likewise

That would do it!