I can't even say now how many crash reports I've sent to your company regarding continuous random crashes, primarily when starting up the program. THis was happening on VEPro 6, so I eventually went back to VEPro 5, and now still having random crashes. The only thrid party plugin I have loaded into VEPro is Kontakt (latest version), and no libraries loaded. Since 95% of my libraries are written for Kontakt, I have to have this working. I'm currently on a MacPro desktop (mid-2012) running Sierra 10.12.6. Funny is that I don;t recall these issues when running version 5 under Yosemite, however, I cannot go backwards due to software incompatibilities at this point. I've attached a few crash logs if any one care to take a look. So far, anyone that has looked at the crash logs has said they cannot determine the cause (which seems to make the crash logs rather useless). I understand that VEPro 5 is old at this point, but version 6 has been out long enough that it should not have all these problems. And from looking through many other posts here, I can see I'm no the only one having issues.
CrashU0020Log.doc-1696337573100-9m5vn.doc-
VEPro - Crash, Crash, Crash & Still No Fixes
-
Me too, The same issue. Crashes all the way. Relaunch the VEpro and pro tools hundred times per day. Please fix it ASAP.
-
I can only tell you guys that here on my iMac with Logic Pro X (High Sierra) & VE Pro 6 , it crashes maybe once every three months.
-
Hello I have a similar issue. 2013 mac (black trash can). When I load matrix or presets, they VEPro crashes out
CrashU0020Log.doc-1696337573648-bfjet.doc
-
I am using deminsonal strings and the library data is spread across two seperate ssd drives. Does this complicate things too much? Maybe its the apple HD format with High Seirra?
-
Here's another crash log. It seems different that the first one I posted yesterday.
crashU0020VE6U0020v2.doc-1696337574015-ydyt5.doc
-
No particular reason I think it was opperator error. I have Upgraded to VEpro 64 and and It's working now.😃
-
Since the recent update (Jan. 2018), I have been having crashes as well. Recently it's gotten worse!
Currently running VEP (64 bit server) with the latest Pro Tools, Kontakt and Spectrasonics releases.
On iMac Pro - 8 core - 64g ram - OS 10.13.3
External SSD drives via BM Multidock.
Is there a proper way to trash prefs or should I delete VEP completely and reinstal?
Thanks in advance!
-
No solution or response to this. Is it safe to uninstall/reinstall the January release update of VEP?
Currently, after quitting PT 12, VEP will not quit thereby leaving no other choice but to engage Force Quit. This happens every time now, in addition to other issues described on my other post above.
Please advice. Thanks.
-
No solution or response to this. Is it safe to uninstall/reinstall the January release update of VEP?
Currently, after quitting PT 12, VEP will not quit thereby leaving no other choice but to engage Force Quit. This happens every time now, in addition to other issues described on my other post above.
Please advice. Thanks.
I had issues with the latest VEP6 crashing too. I went back to Vienna Ensemble Pro-OSX-6.0.16502 version and all is good and no crash thus far.
-
Sadly same here.. totally useless.. the January build is really messed up.
It crashes all the time.. especilaly when sending CC info.
viennajan_crash.txt-1696337575219-uzaty.txt
-
Update - just playing notes from my midi controller will crash it.. i tried both latest version.. then uninstalled and tried prev. version ..both crash. I open vienna it loads all instruments.
i open ableton it connects... i hit notes on my keyboard.. and its crashes.
Happens almost everytime..
-
I had issues with the latest VEP6 crashing too. I went back to Vienna Ensemble Pro-OSX-6.0.16502 version and all is good and no crash thus far.
Hi
I can only download 6.0.15864, Can't found 6.0.16502; Where do you dowloaded ? thanks
-
-
I seemed to narrow down my issues with using AU's.. I swapped to VST's only and its behaving for the moment.