Crippling VEPro crash

[dragsquares]

Mojave 10.14.5, latest VEPro (Catalina with the update, .922 I think), Peo Tools 19.6.0.370 When I open my rather large template in VEPro, it loads (takes ca. 5 minutes). It’s saved as decoupled and corresponds to the cue I’m working on. I Launch ProTools. Load the session I worked on all day yesterday without issue. As soon as ProTools gets through restoring everything and is building the overview file, VEPro quits. Returns this in the crash report: Crashed Thread: 757 at.co.vsl.viennaensemblepro.ProcessThread.2 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000001a8 Exception Note: EXC_CORPSE_NOTIFY (Skipping down to the thread in question) Thread 757 Crashed:: at.co.vsl.viennaensemblepro.ProcessThread.2 0 com.parallax-audio.Vss2 0x000000011dca3b6b AUBase::DoRender(unsigned int&, AudioTimeStamp const&, unsigned int, unsigned int, AudioBufferList&) + 1899 1 com.parallax-audio.Vss2 0x000000011dc998fe AUMethodRender(void*, unsigned int*, AudioTimeStamp const*, unsigned int, unsigned int, AudioBufferList*) + 46 2 at.co.vsl.viennaensemblepro 0x0000000110036dcb AUPlugin::process(long long, float**, float**, int, float*) + 763 3 at.co.vsl.viennaensemblepro 0x000000010fca177c AudioChannel::processFxRack(long long, int, float**&, float**&, int, float*) + 764 4 at.co.vsl.viennaensemblepro 0x000000010fca2b3d AudioChannel::process(long long, float**, int, float*) + 3181 5 at.co.vsl.viennaensemblepro 0x000000010fd0457a VIAudioEngine::ProcessThread::run() + 1178 6 at.co.vsl.viennaensemblepro 0x000000010fd2495e void* std::__1::__thread_proxy<><> >, void (VIAudioEngine::ProcessThread::*)(), VIAudioEngine::ProcessThread*> >(void*) + 62 7 libsystem_pthread.dylib 0x00007fff7c5152eb _pthread_body + 126 8 libsystem_pthread.dylib 0x00007fff7c518249 _pthread_start + 66 9 libsystem_pthread.dylib 0x00007fff7c51440d thread_start + 13 Took out my beloved VirtualSoundstage 2 and it works again. So my question is - this happened all of a sudden, so has anyone else had a plug-in just spontaneously start killing VEPro? Or might it be a fragment of data or pref that VEPro sets in a plug-in that gets corrupted? I rather miss VSS2 now - all of my AudioModeling winds were going through it. I’d found that MIR was a little heavy on the system and added too much latency to be a good fit, though I liked how it sounded. I’ve replaced VSS2 with an early-reflection program from an algo reverb and the show goes on, but... not insanely great. Thanks.