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??

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.

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

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?

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”

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.

I'm currently on the latest Mac OS and Logic Pro 11. This issue started an OS ago and with the previous version of Logic. I did screen share sessions with 3 layers of tech support and they couldn't find an answer. The only recommendation was to wipe the drive, start over with no 3rd party plugins or external devices. I finally gave in with the advent of LP 11 and started fresh. All was great until today, the 3rd day of rebuilding, and the alert popped up again. The only extra software in the system is Audio Hijack and it's not interacting with Logic. Given everyone else's rigs and systems this is affecting, I doubt the culprit is AH. All I can say is it's good I'm retired and just doing this for "fun" at this point. Otherwise it'd be a serious problem. BTW: It's certainly not helping the "fun" factor in retirement either.

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.

There is not really reliable way to detect which Audio Unit is faulty. It is technically not possible. Crashes are not all the same. Sometimes it is obvious, but very often the crash is triggered by some important memory being overwritten and the crash happens later when the memory is used. And because all Audio Units share the same memory, _any_ AudioUnit could overwrite memory of other Audio Units and let them crash instead. Blaming the crashing Audio Unit would be wrong, because the fault lies in a different one – the one that overwrote memory. Having all Audio Units run isolated would be ideal, _but_ it would cost some performance.

What can be done? Well, make sure to use the latest versions of all Audio Units. Minimize the dependencies to Audio Units. Is it really necessary to use several dozens Audio Units in one song? Add new Audio Units one-by-one over time to see if a specific one makes the system less stable.

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.

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.

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.

Hey.

I know this is an older post and I hope you've resolved your issue by now.

I just wanted to mention that I ran into this issue for the first time today and I managed to resolve it pretty quickly, it might help someone else with the same issue.

When opening Logic Pro X normally, I got this exact message but it was when I tried opening in Rosetta 2, Logic just crashed and gave me the whole report, I'll post a screen shot below, it's unfortunately in my own language but you get the idea.

I do not understand much of it but I figured as the only plug in the report mentioned was "bx_console 9000 J", I'd try deleting it. In case you didn't get report pop up, you could go to Utilities > Console.app > Crash Reports and find the latest Logic Pro X crash report.

I deleted the plug in from my computer and I could finally open my project again without a message nor crash. However, when I reinstalled it and opened up my project, the same message came up again even though the plugin was successfully validated and was used in other projects.

I had to delete the plug in again, open the project and remove the plug in from every track, save, reinstall the plugin and redo all the processing, which really sucks as a lot was already done..

I use:

Logic Pro 11.0.1

Macbook M3 Pro

18GB

Cheers!