200,354 users have contributed to 43,196 threads and 259,075 posts.
In the past 24 hours, we have 1 new thread(s), 11 new post(s) and 77 new user(s).
I can reproduce this crash anytime I delete more than 3 or 4 instrument channels. It's "almost" a certainty if I delete anything over 4 at once.
This has been the case with earlier builds also and I just put up with it but today it started to annoy me. I can't strip down a channel set without a crash.
Just letting you know.
Hi
I have been doing a lot of deleting recently, no problem for me.
My trick :
I eject VSL HD so VE PRO did not find the samples, so it just load the instrument with NO SAMPLES
I did all my deleting ( I had 80 instruments in a VE PRO instance that I divided into 7 VE pro with less that 16 instruments)
When done I quit VE pro
Re mount my VSL HD
I load my VE PRO SERVER with the 7 VE PRO
and voilà
Best
Cyril
Hi philco,
jut tested here on 10.6.3 with the newest version that will be released hopefully today, 4.0.5436, no problems... Deleted 16 channels multiple times with different sample loads.
Hope the new version does the trick for you, too.
Best,
Paul
@Paul said:
tested here on 10.6.3 with the newest version that will be released hopefully today, 4.0.5436
Hi Paul,
Looking forward to 5436 --
As a relative newbie here, can you tell me if you announce the new builds via eblast, or will the new build automagically appear in the user download area?
Thanks,
Jeremy
PS -- I bought the library yesterday!
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:
Software
1.2.0n
1.2.0n
•
Soundsources
1.0.2
1.0.2
•
Patches
1.2.0
1.2.0
•
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!!
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.
