Unstable 2022.6

[Ride2]

I have following issues with my MacBook Air.

This warning appears very often:
"Pro tools run out of cpu power. Try deactivating or removing native plug-ins (AAE9173)"

Also, the spinning ball crashes the program at least once on hour.
After that the file opens only with the last previous backup. The latest copy will not open the file, because then the following warning appears:
"Could not complete because Magic id does not match"

Anybody idea, what is going on?


Macbook Air M1/2020 16GB
Apollo twin MII
MacOS 12.4
256 samples buffer

Using latest versions (all should be compatible):
Avid plug-ins
Autotune EFX
EZdrummer3
Kontakt 6
Pianoteq7

[Johnny Hulst]

have you checked the compatability chart before you installed 2022.6 on a M1?

Protools is not written native for the M1, it works but it needs rosetta 2.
As long as its not native you can expect problems on a M serie processor, not only protools problems but also plugin problems.
My advice is to stay away from protools on M series if you need huge sessions.

[Ride2]

Oh, I thought UA is using native drivers. Am I wrong in that?

Otherwise, the computer is a supported model and session is very light...only one audio track and six midi tracks.

[Darryl Ramm]

“Help us help you” up the top of every DUC web page.

What sample rate sessions?

You have to do standard troubleshooting.

As has been true of Pro Tools for eternity… always start troubleshooting by trashing prefs, and always suspect plugins… so you are going to pay extra attention to moving all plugins out of the plugin folder, trashing prefs, (pro tools will automagically put back the core plugins). Test if that is stable with no other plugins installed.

With bleeding edge new systems you need to be extra careful with plugin testing. You also need to exclude corrupted sessions and corrupted user accounts… all part of standard troubleshooting.

[Darryl Ramm]

Originally Posted by Ride2

Oh, I thought UA is using native drivers. Am I wrong in that?

Otherwise, the computer is a supported model and session is very light...only one audio track and six midi tracks.

UA and any interface you use on an Apple silicon system has to be running native device drivers to work. That has nothing to do with Pro Tools or plugins that are all running under Rosetta 2 today.

Yes and what you describe is totally expected behavior for plugin problems. You just should be troubleshooting that without needing to ask.

[Darryl Ramm]

Originally Posted by Johnny Hulst

have you checked the compatability chart before you installed 2022.6 on a M1?

Protools is not written native for the M1, it works but it needs rosetta 2.
As long as its not native you can expect problems on a M serie processor, not only protools problems but also plugin problems.
My advice is to stay away from protools on M series if you need huge sessions.

This is just terrible advice, given that 1.Apple Silicon Macs are generally the only ones available to most purchasers and are much better purchase decisions even if an Intel alternative could be found, 2. That many folks have been running Pro Tools on M1 macs since their early availability and 3. There is great discussion on DUC on folks running large post sessions on Mac Studio models. And 4. It is absolutely technically wrong to ever say somebody should “expect problems” because something is running under Rosetta, native code will hopefully run faster, but that does not mean running under Rosetta will cause problems. For many users coming off older Intel based systems an Apple silicon system running Pro Tools under Rosetta will outperform the old system significantly.

But with any new system, latest macOS, latest Pro Tools and extra compatibility hassles caused by all this you have to pay extra attention to careful setup, plugin compatibility and troubleshooting.

[Eric Lambert]

Originally Posted by Johnny Hulst

have you checked the compatability chart before you installed 2022.6 on a M1?

Protools is not written native for the M1, it works but it needs rosetta 2.
As long as its not native you can expect problems on a M serie processor, not only protools problems but also plugin problems.
My advice is to stay away from protools on M series if you need huge sessions.

Compatibility chart, yet. "Expecting" problems due to Rosetta, a BIG no! That's simply wrong and all the evidence states otherwise. When issues arise it's a software tweak that fixes them, but NOT by addressing the mere use of Rosetta.

The OP's issue is also software related; not hardware.

[Eric Lambert]

Originally Posted by Ride2

I have following issues with my MacBook Air.

Out of curiosity, why are you still using ProTools 12.4?

If it were me, I'd create a new blank session and "Import Session Data" to get the tracks from that old session into the new one.

Then I'd delete ProTools Prefs and recreate them from scratch. Not the IOs, just the Prefs.

[Ben Jenssen]

Originally Posted by Eric Lambert

Out of curiosity, why are you still using ProTools 12.4?

That's MacOS 12.4.
The discussion is about him using PT2022.6 - it's in the title!

I urge everybody to make shure when they are replying, that they have read thoroughly what they are replying to. Saves us some time. (You're not alone, Eric.)

[Eric Lambert]

Originally Posted by Ben Jenssen

That's MacOS 12.4.
The discussion is about him using PT2022.6 - it's in the title!

I urge everybody to make shure when they are replying, that they have read thoroughly what they are replying to. Saves us some time. (You're not alone, Eric.)

Haha! Thanks for the check there. Yep, 'twas a case of replying (sloppily) while waiting for an export to finish.

So, current Mac. Current OS. Current PT. A formula for what should be a solid system. Still points to file corruption on some level, and my advice would be the same.