-
Nothing has changed at all here in the past year. VEP crashes and Pro Tools keeps running. To me that sounds related to VEP. Projects with smaller VEP templates and projects without VEP run without crashing. If East West crapped out and VEP was still running then maybe VEP would look less suspect. Are you able to translate the info from the crash log I posted?
-
Tried to setup a new template differently (without using Play's multi-outputs) and got this error message:
Problem signature: Problem Event Name: APPCRASH Application Name: Vienna Ensemble Pro x64.exe Application Version: 5.1.0.11849 Application Timestamp: 50a853d8 Fault Module Name: Vienna Ensemble Pro x64.exe Fault Module Version: 5.1.0.11849 Fault Module Timestamp: 50a853d8 Exception Code: c0000005 Exception Offset: 00000000004d0b39 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 35df Additional Information 2: 35dfe1efe86af831f42d67ed176193e4 Additional Information 3: c3ba Additional Information 4: c3bab3e1664e31469533585def44275b
-
This will not load on my PC but all my Play-based m-frames and v-frames do just fine, so I am guessing it is corrupted.
-
I'm 100% sure it's not corrupt. If I DON'T load VEP server, the pro tools session opens up (without vep of course). If I DO open VEP server I can load all my samples into it. The problem is when I load the server, then launch the PT session- it crashes while trying to "connect".
More proof that the template is not corrupt: If I try to rebuild it from scratch, I get the same crash right when I've loaded 40-50 patches.
Jay, have you spoken to anyone else at East West about it? I have gone the "official" support route and received the auto-generated reply, but that was Tuesday and still nobody has contacted me. Case number: 29868
-
I'll ask, but if I cannot open it they will probably not be able to open it, and anyway, I am not sure any of them use VE Pro.
-
-
Still no help yet from East West- coming up on 3 weeks since I requested support. I did reinstall my entire system twice- once with only the newest versions of Play and VEP and had exact same symptoms- hard system crashes and can't open my main template.
Second reinstall I used old versions of Play 3.0.1 and VEP 5.0.1037 and I'm able to open my main template and play with it. The problems happen once MIDI is recorded. Eventually during stop/playback VEP crashes (Pro Tools stays open) and I get the same error message:
Problem signature:
Problem Event Name: BEX64
Application Name: Vienna Ensemble Pro x64.exe
Application Version: 5.0.0.10370
Application Timestamp: 4f73aaaf
Fault Module Name: play_VST_x64.dll
Fault Module Version: 3.0.15.0
Fault Module Timestamp: 4e14c416
Exception Offset: 00000000001e2c3f
Exception Code: c000000d
Exception Data: 0000000000000000
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: abb2
Additional Information 2: abb23192a1acf8bab854607d477229e8
Additional Information 3: a9a5
Additional Information 4: a9a558b451722e07c3b866480359f1f3
Files that help describe the problem:
C:\Users\Dave Escobar\AppData\Local\Temp\WER99B0.tmp.WERInternalMetadata.xml
C:\Users\Dave Escobar\AppData\Local\Temp\WERD950.tmp.appcompat.txt
C:\Users\Dave Escobar\AppData\Local\Temp\WERD9DD.tmp.mdmp
-
hey, I was having the same problem but using Cubase. I uninstalled MSE and went offline and the problem stopped but after adding Hollywood Brass to my Metaframe the other day the crashes are back with the same BEX error. I was in contact with VSL support ,they responded within hours but said it's a PLAY problem and offered to help EW solve it ,I eventually got in contact with someone at EW and they said they gave Karel at VSL's contact info to the developers and to figure it out,but last time I asked VSL they hadn;t heard from EW. It's a real drag. Maybe they're just not gonna deal with it and fix it with PLAY4 whenever that comes out.
Forum Statistics
197,897 users have contributed to 43,084 threads and 258,681 posts.
In the past 24 hours, we have 1 new thread(s), 5 new post(s) and 55 new user(s).