This is pretty infuriating. Using with VEPro 7.
Mostly things go OK - but frequently when I stop the transport (just using the space bar) everything crashes - meaning Cubase instantly evaporates - and so does VEPro 7.
Cubase does not give me a crash log (at least not that I can find) but VEPro does.
If I’m supposed to be able to find the crash logs in Console, then they’re not there.
The probable crucial part of the VEPro crash log is copied below…
I have today erased my entire Cubase 10.5.12 including all the prefs - then re-installed 10.5 again (without the update)
_No issues this time with VSTs having been through them all the other day.
I also re-installed VEPro7 latest version and for good measure all my NI stuff (which really just amounted to Kontakt 5 latest update. )
Still doing it though. I wondered if it might be connected to Quicktime - and if I could run a different video player / engine instead. Don’t ask why I was thinking that, it’s just about the only other common factor I can think of.
It’s not simply a corrupted project because it does it on more than one, unless the template I wrote months ago is the issue.
Does anyone have any ideas??
Crashed Thread: 605 at.co.vsl.viennaensemblepro.EngineServerThread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [8032]
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff67e5bdfa mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff67e5c170 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff2debabf7 __CFRunLoopServiceMachPort + 247
3 com.apple.CoreFoundation 0x00007fff2deb96b1 _CFRunLoopRun + 1329