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!