The bridge doesn't come "free", the translation from 64-bit to 32-bit does cost some CPU power.
Understandably, but in version 2.17 (or previous ones) there was no such issue.
I remember very well that I could load several 32bit plugins with Fxs in the channel strips without causing immediate CPU overloads turning red on the readout... And I had a full concert of different keyboards setup loaded.
Now with v.2.2.2, with a clean new empty concert (without even any controls yet), with only one channestrip, the audio pref set at the minimum (1024 samples and buffer safety On), just the fact to instantiate a single 32bit plugin (which ever brand/type) in Mainstage (64bit mode) automatically turns the CPU overload to red and crackles the sound when/if I can play it few single notes!
Is there an easy way to revert to previous version (2.17)?
Any caveat in proceeding in that way?
Is this possible to have both version (2.17 and 2.2.2) on my MBPro? So I could eventually update to a corrected version (2.2.3... when available), since I already paid extra for it; and use in the meantime a working version (2.17)...
LogicPro 10.6.3, MainStage3.5.3
MBPro 17", Core2Duo, 8G, OSX 10.12.6
MacPro, Xeon 6Cores, 64GB, OSX 10.15.7
ULN8, MOTU MIDI TP-AV, C4, MCU Pro, KorgNano, Novation SLMkII
AAS, NI, Celemony, Spectrasonics, Korg, Arturia, etc...
PC, iPad3(V-Control & LogicRemote), AtariST(Notator SL), Several vintage gear