I hadn't really thought of individual plugins being programmed to release cpu when there is no audio, but that appears to be exactly the case, and it really complicates the whole Track plugin matter.richardjay wrote: ↑Tue Jul 14, 2020 3:24 pmThanks for the comment but actually I never use Steinberg plugins - mine are all 3rd-party,bob99 wrote: ↑Sun Jul 12, 2020 9:58 amHi Richard. I think if you had some degree of success with this in the past it's possibly because you had one or two plugins that were programmed to cease processing when there is no audio. I've found that appears to be the case with most of the Steinberg plugins (except RestoreRig and CurveEQ).
You could easily test your individual plugins on Wavelab tracks to see if they're programmed to release, using the Wavelab performance monitor and/or the computer built in CPU meters. That's all I did. But fwiw, I didn't find any performance difference between Wavelab 9.5 and Wavelab 10 under the same heavy load on Windows 10, but I don't doubt that you did. Also I'm not using Mac like you are.
You could then test those plugins (that don't release) in Cubase to see if Cubase is programmed to release track plugin processing when no audio, regardless of individual plugin programming. I don't know if that's ever been stated or confirmed in Cubase, but it should be easy to test, using plugins that have been determined NOT to release on Wavelab tracks when there is no audio.
You could also trial BlueCat Patchwork in Wavelab. It's not the least expensive plugin out there, but it's reasonably priced and it should make Wavelab do exactly what you want with your track plugin chains no matter how the individual plugins are programmed. It worked for me on Windows, so I'm only assuming it will act the same on Mac, but worth testing.