Quote:
Originally Posted by glasswing
This is why I think the tedious process of loading a plugin, test - then load the next (and test etc) is the best path at this point. I would bet most of the nightmares we hear are triggered by funky plugins. Seems to work great for the folks that go through the tedious cold install, one plugin at a time route
|
Make it less tedious. Just try removing large groups of plugins. Starting with the obvious one of VIs.
Then do a binary tree walk, adding/removing plugin files in large groups until you home in on the suspect plugin. A linear test across plugins is super painful and hopefully not needed.
Pro Tools by itself on Rosetta 2 on Apple silicon does not use this much memory, so first thing to suspect and exclude/include as a problem (as nearly always) is plugins.