What is your exact version of Pro Tools : PT11.0 or PT11.0.1 ?
-
Hello I am having the exact same problem in Pt 11.0.1. When exiting PT 11.0.1 after using an instance of VEP 5, PT gives me the (PT not responding), and promptly crashes/closes. The problem signature is as follows: Problem Event Name: BEX64 Application Name: Protools.exe Application Version: 11.0.1.544 Application Timestamp: 51cd882c Fault Module Name: Vienna Ensemble Pro.aaxplugin_unloaded Fault Module Version: 0.0.0.0 Fault Module Timestamp: 51c88c97 Exception Offset: 000007feeee1b1fe Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 6.1.7601.2.1.0.768.3 There are additional Information code lines (1 through 4), I can provide (though quite long), if you feel it can be helpful. I am using a Gulftown Core i7, 6 Core, 3.33GHz, 12 GB DDR3/1333 Win 7 64-bit SP1 (PT Certified Computer) with Vienna Ensemble PRO 5 (Windows) build 5.1.12337. Thank you, Lou
-
I have apparently resolved this problem, at least on my Win 7 system. I suspected it could be a problem with Win 7 as opposed to PT 11 and VEP 5. I always install Win 7 security updates but never install optional recommended updates. I connected my computer to the internet, performed a Windows Update search and noticed there were some 28 "recommended updates" I had not installed. I selected all recommended updates, downloaded and installed them. Note that before installation Windows creates a Restore Point so you can "hopefully" get get back to where you were should the updates not work for you. After installation and reboot the problem was gone. I have used VEP 5 seven times in PT 11.0.1 since and upon exiting PT 11, no crashes so far. I do not know which update or updates fixed the problem on my machine but it did. Anyways, I thought I would pass along what worked for me. Your mileage may vary. Best, Lou
-
anyone else getting this with pt11HD.01 or is anyone running VEP with protools 11.01HD and not getting any problems?
I'm consistently getting a bex64 crash on exit anytime a VEP is loaded. No bex64 crashes when there's no VEP. I think it is also corrupting the protools driver or something because now after second re-install it keeps crashing with runtime 6025 errors with not muchloadedat all.
I'm able to change from one song with VEP to the another without VEP with no bex64 crashes but now that protools is corrupted somehow i get crashes all over the place.
-
Further testing shows that when I use a Scope card and change from a song with VEP and a song without VEP it crashes (I think due to flakey ASIO drivers of Scope) but when doing the same thing using the RME there is no crash at that point. But when I finally exit PT it crashes.
If in any one session with PT I dont load a VEP instance there are no crashes.
-
Anyone? Please give me a clue.
Is anyone running VEP with 11.01HD without crashes on exit?
1) If so are they both latest versions?
2) Is your network set to a static ip?
3) Have you tried low buffer settings like 64 or 128 samples?I'm now running RME digiface instead of Scope, VEP v5.1.12377 on main DAW and on 2 remote servers
-
I'd love to tell you that I'm crash free. But,,, no such luck?!! I have PT's 11.0.1, W7 64, all VSL on latest updates, and no matter how I exit, PT's crashes now every time. Not sure whats up? And although I don't think its that big of a deal,,, it would be nice if it were fixed. Since I fixed my eLicenser prob, it starts up again every time without a hitch! I'm sure they'll figure it out soon, till then I'm fine as long as it works! Mike
-
IE ver 10. I clicked on the icon in IE on top to change it to blue. It did not work first time. Closed the tab and opened a new tab. This time clicking on icon seems to have worked.
I am running PT 11.01, vepro5, windows 8, 16gb, i7-4700mq. PT only crashes on exit if vepro servers are running.
Thanks
-
Here is the crash report. Also sent to support as requested.
Thanks
Log Name: Application
Source: Application Error
Date: 2013-09-13 4:42:34 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: test
Description:
Faulting application name: ProTools.exe, version: 11.0.1.544, time stamp: 0x51cd882c
Faulting module name: Vienna Ensemble Pro.aaxplugin_unloaded, version: 0.0.0.0, time stamp: 0x521727ea
Exception code: 0xc0000005
Fault offset: 0x000007fb4003b87e
Faulting process id: 0x3bec
Faulting application start time: 0x01ceb05cecda45bb
Faulting application path: C:\Program Files\Avid\Pro Tools\ProTools.exe
Faulting module path: Vienna Ensemble Pro.aaxplugin
Report Id: 6f2d38d6-1c50-11e3-be8c-68172962638e
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-09-13T08:42:34.000000000Z" />
<EventRecordID>4991</EventRecordID>
<Channel>Application</Channel>
<Computer>test</Computer>
<Security />
</System>
<EventData>
<Data>ProTools.exe</Data>
<Data>11.0.1.544</Data>
<Data>51cd882c</Data>
<Data>Vienna Ensemble Pro.aaxplugin_unloaded</Data>
<Data>0.0.0.0</Data>
<Data>521727ea</Data>
<Data>c0000005</Data>
<Data>000007fb4003b87e</Data>
<Data>3bec</Data>
<Data>01ceb05cecda45bb</Data>
<Data>C:\Program Files\Avid\Pro Tools\ProTools.exe</Data>
<Data>Vienna Ensemble Pro.aaxplugin</Data>
<Data>6f2d38d6-1c50-11e3-be8c-68172962638e</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
-
@Paul said:
Hi goodplayer,
Please send a crash report to , our developers will have a look.
Best,
Paul
Further to my crash dump that I sent earlier, I did some more testing with more insight into pt 11 crash/hang problem with VEP.
Further testing revealed that protools 11 (ver 11.01) will only crash/hang upon exit if VEP has been INSERTED as an AAX64 plug-in in protools atleast once, regardless of whether that protools session is saved or not. And, protools will also crash/hang even if VEP is REMOVED before exiting protools.
And further, protools 11 does NOT crash/hang upon exit from a session into which VEP has never ever been inserted as a plug-in insert. Protools will EXIT NORMAL each time. Also tried this with protools songs containing few tracks and with over 50 tracks fully loaded with stock protools 11 effects, instruments, etc. And each time protools exit was normal.
Here is what I think. My understanding could also be incorrect. It seems to me that VEP as an AAX plug-in once inserted into protools, leaves something in protools (regardless of whether the song/session is saved or not), causing exit of protools abnormal. That is my two cents worth.
I hope this helps for a fix in some way.