Hi Paul, unfortunately it's still crashing with this new build. 

Here is a video..........paste the address into your browser.

http://screencast.com/t/Y2I4Zjdh

What you see is actually one instance of Stylus RMX with 7 other input channels...........so only one VI.

VEPro has always behaved this way. Could it be something specific to my computer?

I always uninstall before I install a new version.

Regards

Phil

Phil,

I tried to crash 5436 like your video (love Jing!) -- but I was not able to. 

MacBook Pro OS 10.6.3

32-bit VEPro server build 5436

I added 30+ instruments and inputs. VIs, Spectrasonics, assorted AU VIs. Selected all, delete. Works. Did not try RMX though... what if RMX is not in your test?

Hi Jeremy, unfortunately Omnisphere does it as well. They are both the latest versions. I'll do some more tests today and see if it's only Spectrasonics VI's.

Very strange though. My machine only runs VEPro and Safari. No other apps run on this machine.

The video is when the slave is NOT connected to the master.....but the crash happens either way, connected or not.

Regards

Phil.

I tried to crash it again, this time with Omni.

http://www.screencast.com/t/NGY4NDIyZ

During this test, it was NOT connected to the master. 32-bit server running on MacBook Pro, OS 10.6.3

Omnisphere version:

I also tested while connected to protools. Works both ways for me. I wish I could reproduce your test.

Well I may have figured it out. It will always happen if I open a "old" (that is pre this build) Metaframe. If I make a new 32 bit Metaframe I can't create the crash. If I open and old Metaframe....................and I save every song as a separate Metaframe (so I have about 20 saved) I can recreate the crash every single time.

Here is another one from my very first Metaframe............probably January this year...........opened in the current build.

http://screencast.com/t/ZjE3MDA5Yj

I thought perhaps it was the Vienna plugs but it crashes without them.

I just have to make some new template Metaframes I guess!

Ok two more tests.

Load suspect Metaframe. Delete entire Metaframe from server window. No crash.

Load suspect Metaframe. Save all channels as a channel set. Delete Metaframe and instantiate new 32 bit Metaframe. Load saved Channel set. Delete RMX.

Crash!!

So it's in the channels..............or something!!

So what do you guys think? Is it just my machine or are my saved Metaframes somehow faulty?

Is no one else seeing these crashes?

Would you like me to send a Metaframe?

I'd really like to solve this problem.

Phil,

Did you ever resolve this?

I am able to reproduce this now, using build 5436.

mac OS 10.6.3

The channels of the viframe were:

1 instance of Kontakt 3.5, routed to 8 outputs

3 input channels (source: outputs 3-8 of Kontakt)

1 Bus

1 VSL VI with a 6 cell matrix - maybe 600megs of ram in use

If I select the instance of Kontakt and the 3 input channels, I can crash the viframe consistently.

WHAT IS DIFFERENT NOW (as compared to before?)  - the VSL VI !

When I tested this last month, I did not yet own any VSL instruments -- now that I have 8 big libraries, I am pushing VEP much harder. So yes, I can reproduce this. Did you find resolution?

Thanks,

Jeremy

Hi Jeremy, I have become used to not deleting anything in VEPro so I have avoided the problem.

After reading your post I opened up some of the metaframes from the start of the year...........all with Kontakt 4 present. It won't crash. As far as I can remember I have changed nothing.

I've opened 4 metaframes now from different times of the year and none will crash.

If I was going to point the finger I would point directly at Kontakt. The only crashes I have with VEPro are when I'm doodling inside Kontakt.

Not that I can reproduce it.

Oh!!! I just remembered that the guys at Vienna told me to turn off multi threading in both Kontakt AND VEPro. So in the preferences in VEPRo I only have 1 thread chosen. And in the prefs of Kontakt you can turn off the option that mentions threading.

It seems to make no difference to the CPU usage at all.

Maybe that's the solution?

Good luck.

I also have often crashes when deleting instruments or busses.

But with a little trick I can prevent the crashes: I move the intrument which I want to delete to the end of the list (by drag and drop). Then I can delete it without problems.

This bug should be fixed in the upcoming update. We were not able to reproduce it, but found the cause for the problem and fixed it.

Hi Karel,

deleting several instruments at once still crashes Ve Pro (using Public Beta 4.0.5814). It doesn't matter for me, but I think this info would be interesting for you.

Best regards,

Peter

Is it possible to narrow down the problem, or does it happen consistently?

@Karel said:

Is it possible to narrow down the problem, or does it happen consistently?

Hi Karel, I will test it this evening when I am back at home.

Hi Karel,

i created a new instance (32-bit), inserted 6 instruments (6 x RealGuitar2), selected all instruments and deleted them at once -> and VE Pro crashed at the first try. The same on the second try.

Best regards,

Peter