A little more information after NOT having the startup “abnormal termination” message a few days in a row, but having it come back today:
Please see my previous message in this thread for more specifics on earlier behaviors and plugins in the project I’ve been working on. Subsequent to the previous scenario, where I’d tried to remove Tonal Balance 2 from the Control Room insert, but it mysteriously reappeared, then removing it (again) and not seeing the startup messages, I had another issue where Cubase started up not recognizing my audio interface as being available. I’m not positive what caused that (maybe the drivers didn’t fully load the first time?), but, in trying to get the audio interface to be recognized again across several starts, including rebooting it a few times, thinking the driver wasn’t fully loading or some such thing – it ended up being that I just had to go do a different place in Cubase Studio Setup than I was finding and reattach it there, after which it was recognized in the other areas – I’d tried restoring audio input and audio output presets in the audio configuration areas with no effect. When things came back to working order, Tonal Balance Control 2 was back in my Control Room Inserts! (This may or may not relate to the problem at hand here, but, in my previous entry in this thread, I was wondering if Control Room inserts in general were related, which is why I mention this since it is also relevant to the next bit of information.)
Because I was going to be tracking vocals, and I had a number of virtual instrument tracks live, I decided to freeze those tracks and also create a single audio track submix of the instrumental tracks, then disable all the instrumental tracks, prior to recording lots of tracks and takes of those vocal tracks, in order to minimize both CPU and disk overhead while tracking. There were basically no plugins active in the entire project during my tracking, with all plugins either frozen and in disabled tracks or, in the case of Tonal Balance in the Control room, just disabled.
Once I did the tracking, I put three Waves plugins on my lead vocal (Vocal Rider, Tune RT, and SSL EV2) to use to help my judgement during comping, disabling all the background vocal tracks I’d recorded in the same session. Despite now having Waves plugins active again (and disabled Tonal Balance in Control Room), I did not get the startup message about abnormal termination that I’d gotten previously. I restarted Cubase several times during a few days of comping, editing, then tuning (with Melodyne as an ARA extension) the lead vocal, and I did not get any further abnormal termination startup messages.
Moving onto the background vocals, I had the same suite of Waves plugins on each of 6 tracks while doing the comping, editing, tightening timing (mostly using VocAlign Ultra as an ARA extension, but also using Variaudio in a few cases), then tuning (using Melodyne again). I did have one Cubase “poof” while using VocAlign Ultra, but that was the only incident to that point – no startup messages, other than in the one case after the “poof” (and that one was obviously expected).
Note that, during all the above vocal work, I’d kept the original instrument tracks frozen and disabled, using the audio submix track for reference on the instrumental accompaniment. Once I’d finished the BGV work I froze the BGVs (with only Vocal Rider and SSL EV2 since the Tune RT was only used for reference while comping), then I also brought back (i.e. enabled) all the instrumental tracks (still with many of those frozen – I think there were only two exceptions, one being SD3 and the other being Kontakt). This took a very long time, and I did see the Waves cursor at various times during this operation (two of the frozen tracks had a couple Waves plugins each in them, with those plugins also being included in the freeze, thus their being disabled in the actual project).
After saving the project, I was working on a Kontakt-based track for a few hours before stopping work for the night. I did note that Cubase took a fair while to close the project last night (and I was concerned it might even hang), though it eventually finished, and I was able to close Cubase with no visible hang. Then this morning I got the abnormal termination message on startup again.
Soooo… What is different and why is it back? Well, that is the big question, but I have a new thought, keeping in mind that these startup messages almost always mention abnormal termination in “Freeze”. Maybe there is something about frozen tracks? Or maybe frozen tracks with some specific plugins? I now do have Wave plugins back in the mix, but there were some points in the past where I was getting this messages where I’d eliminated any Waves plugins. Is it possible there is some relationship to other vendors’ plugins, such as IK (MODO Bass), NI (Kontakt), Toontrack (SD3), or one or more of the others I have on the virtual instruments front? I do know that my previous project, which was the first one I mixed in Cubase 12, had at least some overlaps from the plugin world, including at least SD3, Kontakt, and a bunch of Waves plugins. I know I was also using IK’s Lurssen Mastering Console in that one for a while (but not MODO Bass, and I eventually replaced Lurssen with a Waves plugin)?
Perhaps if I get some experimentation time over the weekend, I can try setting up a simpler experiment relating to frozen tracks to see if I can find something with far fewer variables to recreate this issue. For now, this is just thinking out loud, partly in case anyone else who is seeing this problem may see some commonality (aside from the already-mentioned Waves part, which may or may not turn out to be a red herring).