Further to this subject, I had a problem just last night.
I had been working on a dance remix which was very CPU intense, but everything ran ok and I was able to render a rough mix. Then I came back to it this morning and as soon as I loaded the project, the CPU went into overload and stayed there - audio messed up and no easy way to understand the underlying cause.
I made a project back-up and worked successfully with that for a while, then closed down. On re-opening, I was back to the same problem.
Eventually, I isolated the issue by removing elements of the project sequentially until I eventually found the culprit…which was Steinberg’s own Roomworks. As soon as I removed it from the project all was well. Alternative patch settings worked. Just this one patch - a longish, but not crazy reverb.
Being able to deselect plugins at project boot up, either individually or in groups would have saved me time and hair. An error dialog along the lines of ‘Roomworks is using an unusually high percentage of available resources’ would have been fantastic. Freezable effects returns would be another possible convenience to stretch resources.
If anybody from Steinberg reads this - here’s another idea. In the Plug in information dialogue, it is possible to stop plug ins by unticking the box to the left of the listing. BUT this only works when the plug isn’t in use. If that functionality extended to plugins used in the project, I could have solved the problem double-quick.
Apologies to Skyko for hitching a ride on this topic.