A CPU error stops playback and then the CPU meter is peaking, rendering the session unusable until we find the problem plugin(s).
Usually it's ONE plugin that is malfunctioning.
BUT, to find that plugin can take dozens of minutes!
Is it possible to automatically colour the likely culprit(s) RED after a CPU error?
This would be such a time saver for so, so many of us.
Of course, we'd prefer no... more »