Normally I wouldn’t install a new OS this early, but I got a new MacBook Pro with Monterey pre-installed. I was working just fine in WaveLab 10 until this morning, when it started crashing to desktop on launch.
I tried holding down Command and opening an empty project, which didn’t help. It gets as far as presenting the dialog box with the option to open an empty project though!
So I figured before I complain here, I should bite the bullet and upgrade to 11, which I did. Unfortunately the same thing happened on launch.
I just tried again, and this time selected a recent audio file from the list of options, and it looks like I’m in! So now I just need to not quit.
Here’s the first chunk of the crash report if someone has any ideas:
Process: WaveLab Pro 11 
Path: /Applications/WaveLab Pro 11.app/Contents/MacOS/WaveLab Pro 11
Version: 18.104.22.168 (22.214.171.124)
Code Type: X86-64 (Translated)
Parent Process: launchd 
User ID: 501
Date/Time: 2021-11-04 12:42:58.1028 -0700
OS Version: macOS 12.0.1 (21A559)
Report Version: 12
Anonymous UUID: 75079B17-6B15-39CC-118B-2DA42C0CD2B2
Time Awake Since Boot: 1600 seconds
System Integrity Protection: enabled
Crashed Thread: 35
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000140
Exception Codes: 0x0000000000000001, 0x0000000000000140
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler 
VM Region Info: 0x140 is not in any region. Bytes before following region: 4300644032
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
__TEXT 10056a000-10385e000 [ 51.0M] r-x/r-x SM=COW …aveLab Pro 11