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

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.

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.

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.

Being on an M1 MBP, so far I no longer get it on Rosetta. However, there ARE some plugins whose website say they are not yet compatible with Apple silicon or that Rosetta must be used. Not obscure plugins, but still. One is Grandeur, a beautiful piano I bought after seeing Sanjay C do his comparison. Spitfire’s BBC Discover orchestra is another. If I go off Rosetta, I get the error, even if I delete those plugins. Still trying to figure this out.

Is there a log or anything to indicate which plug-in is acting up? It seems a bit weird that they don't give any indication (or that they don't know which one it is).

Glad you got a clue as to which plugin is causing the error, even if it doesn't solve your problem.

Contact Brainworx support.

AGREE AGREE, What is the point of an error, if you don't know what is causing the error.

and again: Go to Utilities > Console.app > Crash Reports

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.

Thanks for the response but

1) i already rescanned long ago when it first started and all passed

2) There were no “failed” to remove

2) this doesn’t speak to Logic identifying the culprit.

As for the back up, the method you described was more than I understand was needed. I DO have a Time Machine drive always connected. I understood that was all that was needed. I’ll look into pulling that.

thanks again

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.

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!

This is exactly why so many people turn away from logic, I've been using it for many years - I would say the most frustrating thing is that when a plugin becomes unstable they don't tell you which one is not compatible, this means you now have to go through all your plugins and narrow down on which one isn't functioning.

It's an extremely poor system and I wouldn't put my money on logic fixing something like this.

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