An audio Unit plug-in reported a problem which might cause the system to become unstable

So we are in March 2024, this is issue is back. I have a Mac mini m2. It is starting to make me very angry. How do I fix this problem or can we get this bug taken care of.

Why logic does not disable these faulty plugins automatically??

I'm having the same exact issue on a macbook pro m2

Any more updates/info? I'm on a M1 MBP, it's my first DAW and computer for music production. Only Logic versions have changed. All my plugins were gone through one by one to update and make sure they run on apple silicon.

Why doesn't Logic at least tell you WHICH PLUGIN is reporting the issue - or in which plugin Logic spotted a condition it didn't like? Are there logs?

This is annoying and I don't recall it happening before 10.8.

Ugh... because I get it on several projects. But if I solve it for one, hopefully would solve it for all.

Side note - that creation date for the plugins is a good hint! I have upgraded every plugin to its latest. I've also searched for people who may have been able to determine their culprit, but not found anything yet. So I might start with the oldest by that date, work my way forward.

Thanks again for helping. I still have to whine - I wish Apple would just get Logic logging these errors so we can find the source.

1. disable Midi 2.0
2. make sure your plugins are compatible, I hope you didn't use Migration Tool to transfer audio stuff to your new computer.

Did you find a solution for this issue? On new MacBook M2 I get the same message, along with the occasional glitch noise. This is on an 'old' Logic Pro X project.

I'm just getting time to start this exercise, but all the plugins have dates in December 2023 - which would have been when I went through each product/vendor and made sure I had the latest versions. One of those, BIAS FX 2 had dates of November 12 2023 when I hit "show package contents". The main point is all of the ".component" files in the default folder had one of 2 december dates: 12/12, 12/29. There were none in my ~/Library folder.

So the hunt and peck process begins. Thanks for your help!

Same issue is happening to me. For me the culprit is Antares I’m almost positive. I might have to redownload dispute the inoperable glitch in autotune just to make it stable in Logic, which should be equipped to automatically disable the plug in methinks. I’ve spent too much money on both companies to deal with this. Very frustrating. While I’m at it, iCloud is lame I would 1000% prefer a backup service.

The issue hasn’t been resolved yet. The culprit seems to be Keyscape, but I am not sure. I use my computer as a mobile keys rig and when the error Pops up, only the Keyscape sounds stop working.

No external ssd is being used in the setup. Just a 2i2 audio interface and nanokontrol 2.

Has anyone found a reliable solution yet?

Software details:

Keyscape software 1.5.1c arm

Keyscape sound sources v.5.0c

Keycape Patches v1.6.0c

Logic Pro X 10.8.1

macOS Sonoma 14.4.1

chip: m3 pro with 12c CPU, with 18gb of ram and 1tb of storage.

I love going on these forums just to know Apple doesn’t care about their customers. “You already spent your money and now we don’t care”

From MCU protocol to plug in issues Apple takes no responsibility (even though the issues are SOLEY with Logic Pro)

When I first got my M1 with LPX I was excited and everything was fine. Every update makes it worse to the point I’m ready to go back to Reaper on a PC.

Apple has been the biggest overhyped disappointment in music production in the last few years.

“No one puts a gun in your face to steal your money anymore”

I am extremely frustrated and disappointed with Apple's lack of attention and support towards professional users like myself. After experiencing recurring stability issues with Audio Units in MainStage, I updated my system to macOS Sonoma following recommendations that this would solve the problems. However, the issues persist.

It’s a disgrace that Apple, with all its resources, seems to focus more on selling products rather than ensuring the reliability of the systems that many professionals rely on daily. I have invested money in original software and supposedly high-quality hardware, but all this seems to be in vain when the technical support falls short and system updates, rather than helping, appear to complicate things further.

I am seriously considering switching operating systems because I am tired of dealing with these continuous problems that not only consume my time but also affect my work. It’s disheartening that a company like Apple does not take the needs of its professional users seriously.

It seems all that’s left for us users is to stop investing time and money in a company that does not seem to care about us. How many more updates do we need before Apple finally addresses these issues instead of introducing new ones?

Out of desperation - under 10.8, I seemed to have no problems as of about March 2024 using Rosetta. Not my choice, but it was working even with those plugins not yet "M1" compatible.

I backed up, then upgraded to Logic Pro 11 - NOT using Rosetta - ANY 3rd party plugin gives me this error, even those whose vendor say they ARE M1 compatible cause the error.

If you hit "recover" (not quit), it shows the plugin as it tries to recover. That's the closest I've come to knowing which plugin was the culprit. The way I know is because it's on a test project that has NO 3rd party plugins.

I've added a ToneKing plugin to a guitar audio - crash. Use the stock amp sims - no problem. Use a Waves MV2 - crash. Remove it - no problem. I've tried several others - VU meter, RX-10 Guitar noise, etc. Just testing one at a time. Each one crashes.

That's all I have - no solution, no diagnosis. Just some info. Good luck all... Reaper is looking better and better.

Why doesn't Logic at least tell you WHICH PLUGIN is reporting the issue - or in which plugin Logic spotted a condition it didn't like? Are there logs?

Logic Pro > Preferences/Settings > Plugin Manager > Compatibility

You can Reset and Rescan failed plugins, sometimes they work after succeeding the scan. But I would rather update or remove the plugins manually from the components folder on your hard drive.

Don't forget to restart your computer.

This is annoying and I don't recall it happening before 10.8.

Create a backup before updating anything. You can also create a backup of the Logic Version before updating, rename the old version, put the old version back into your Application folder and use several Logic Versions.

Back up Logic Pro for Mac - Apple Support

I invested a few hours in updating all my plugins and honestly haven't had a problem since. That was still on Logic 10, and so far Logic 11 is working as well.