![]() Whatever note was being held or played at the time of an audio engine stop is held in the buffer until Broomstick Bass is stopped by its "Stop" button. Here is an explanation of what I have just discovered. Or, I can fiddle around in Broomstick Bass until I press some magic combination of buttons and it starts acting right again.Īnyone else using Broomstick Bass see this behavior? I have to close Sonar and re-open it which sometimes doesn't work. Sometimes, and I can't figure out when, the Bass will completely lose track of the chords and start reporting weird things (like Cm instead of Eb, which is kind of understandable, except that even when I play single notes it reports the wrong note). On the MIDI track are basic chord triads (no four-note or compound chords) in whole notes or half notes. ![]() For instance, I have Broomstick loaded as a synth with one MIDI track controlling it. This also carries over into the instrument track. Report Id: 6f2d38d6-1c50-11e3-be8c-68172962638eįaulting package-relative application ID:Ĭ:\Program Files\Avid\Pro Tools\ProTools.Sometimes, when I'm playing in auto mode in Broomstick the vsti enters this weird mode where it thinks that a C that I am playing on the keyboard is actually an Eb. Also sent to support as requested.įaulting application name: ProTools.exe, version: 11.0.1.544, time stamp: 0x51cd882cįaulting module name: Vienna Ensemble Pro.aaxplugin_unloaded, version: 0.0.0.0, time stamp: 0x521727eaįaulting application start time: 0x01ceb05cecda45bbįaulting application path: C:\Program Files\Avid\Pro Tools\ProTools.exeįaulting module path: Vienna Ensemble Pro.aaxplugin ![]() 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. My understanding could also be incorrect. Also tried this with protools songs containing few tracks and with over 50 tracks fully loaded with stock protools 11 effects, instruments, etc. ![]() And, protools will also crash/hang even if VEP is REMOVED before exiting protools.Īnd 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. Please send a crash report to, our developers will have a look.įurther to my crash dump that I sent earlier, I did some more testing with more insight into pt 11 crash/hang problem with VEP.įurther 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |