Logic Pro crashes when clicking on audio FX

Hi,

Whenever I click on Audio FX Logic Pro 11 crashes without warning. No dialogue boxes nothing. It just crashes and then brings up the incomprehensible crash report (at least to me) with the option to relaunch.


I have tried in Rosetta and it crashed instantly in a brand new project not from any template and with just an audio or instrument track. The same keeps happening in Apple silicon mode. This happens 100% of the time when I click on Audio FX in the inspector or mixer in Rosetta or Apple Silicon mode.


This issue first appeared last week when I was about to bounce a project and was just going to activate a Fabfilter L2 on the master bus. Logic crashed instantly as I clicked on L2 in the Audio FX slot.


I started to remove the latest plugins I had installed but it kept crashing. So then I tried removing all 3rd party plugins (moving them to a temp folder from /Library/Audio/Plug-Ins/Components), doing a full rescan, deleting the audio cache (/Users/user/Library/Caches/AudioUnitCache/com.apple.audiounits.cache), rebooted and then adding the plugins back in batches of 20-30, all +800 of them. That took me more than a day, as I was trying to figure out if I had a rouge plugin. I was testing Logic in between each batch by starting it with just one audio or instrument track clicking on the Audio FX slot in the mixer or inspector. It worked every time, indicating that all plugins that I added to the Components folder worked as expected. I didn't get any faulty plugin reports at launch of Logic Pro apart from iZotope RX7, so I put all of the RX7 plugins in a separate "uninstalled" folder (I also have RX8 and RX10 installed). Thus I assumed RX7 was the issue and it is also fairly old.


After that, it all worked without any problems and Logic was running fine for about a day in Apple Silicon mode, until I was just about to finish a song and wanted to replace the Logic EQ that was inactive in the Audio FX slot on one track. I klicked on the little arrows next to the Logic EQ to select another plugin. In that moment Logic crashed instantly, without warning. Since then, I have not been able to click in the audio FX bucket att all, in Apple silicon or Rossetta mode, without these vilent crashes. I still don't get any errors or warnigns when starting Logic about faulty plugins.


I have no trouble adding/changing midi FX or instruments on instrument tracks.

Logic seems to be working fine apart from this issue.

Cubase Pro 13 runs without any issues at all.

 

I have tried to disconnect everything and run on the internal soundcard (MacBook Pro M2 Pro), rescanned all plugins and rebooted. Still the same issue. I also disabled Midi 2.0, which I saw suggested somewhere. Still the same issue.   


Has anyone here come across a similar issue and if so, how did you solve it, assuming you did?

Any ideas are very much welcome, as Logic is pretty useless to me at this stage.



I'm running Logic Pro 11.0.1 on MacBook Pro M2 Pro running Sonoma 14.3.1, with an UAD Apollo Twin X, NI Komplete Kontrol S61 Mk2 and a Dell U3219Q attached on high quality USB-C/Thunderbolt 4 cables and I get the same results in Apple Silicon and Rosetta mode.

I have plugins from:

Antares

Audiomodern

Baby Audio

Cable Guys

Native instruments

Arturia

Fabfilter

iZotope

Korg

LiquidSonics

Moog

Plugin Alliance

Plugin Boutique (Scaler 2 have had issues in the past and crashed validation, but I have completely removed the old version and replaced with a new version and I don't get any crashed valitations after that)

Softtube

Sonible

Soundtoys

Spectrasonic

Synchroarts

u-he

Universal Audio

Vlhalla

Waldorf

Waves

XLN Audio

IK Multimedia

Focusrite

Exponential Audio

Excite Audio

Heavycity

Kilohearts

Mastering the mix

Mixed in Key

oeksound

Polyverse Music

Presonus

Pulsar

Sonarworks

Xfer Records

Youlean

and more... All naturally bought and paid for licences.


/Donald

MacBook Pro (M2 Pro, 2023)

Posted on Jul 21, 2024 3:38 PM

Reply

Similar questions

7 replies

Jul 24, 2024 6:36 PM in response to donlin

So, I reset the preferences (Logic Pro > Settings > Reset All settings except key command assignments). That seems to have done the trick for now.


I've tested under my normal profile creating projects from scratch, adding audio and instrument tracks and adding audio FX to them. 


I also opened the last project that crashed Logic a few days ago, added back the LX-24 and now it all seems to be working like there never was an issue. 


Now, I've been here twice in the last week or so. So, I really need to see this running for a while before I'm totally convinced, but it looks promising so far. I'll be in the studio much of tomorrow, so that should be a good first test. 

Jul 23, 2024 2:39 AM in response to yoyoBen

Hi,

Thanks a lot for your input.

It says Thread 0, but I have a hard time understanding what thread 0 actually says. The only thing I see there that makes any sense to me is.


11  AppKit                        	       0x1a0c3cdcc -[NSWindow(NSEventRouting) _handleMouseDownEvent:isDelayedEvent:] + 3472


Which I guess is just when I actually clicked on the Audio FX "container" in the inspector.

I was hoping it would pop up with a rogue plugin that I could uninstall and problem solved. But that doesn't seem to be the case. What does the crash log actually tell me?


I also see that I have crash logs named AUHostingServiceXPC, AUHostingServiceXPC_arrow and UA Mixer Engine. The last one is just once and the "arrow" is a few times, but hte AUHostingServiceXPC is frequent, but not at the same times as the Logic Pro crashes.


The AUHostingServiceXPS is also crashing at thread 0 and what I can read from this is that it is UAD-2 SDK support that is the issue, if I interpret the below correctly. But surely UAD wouldn't release plugins that cause these violent crashes?


Any good ideas on how to intrepret this?


Wasn't the new AU-architechture build to prevent violent crashes due to rogue plugins?




/Don

Jul 23, 2024 5:33 PM in response to yoyoBen

Yeah, for me too. And I tried to understand how to use Xcode to get them "unsymbolicated", but I must be doing something wrong.

So, you are saying that UAD may have installed versions for Intel based Macs on an M2? Is it the SDK-reference that makes you say that?

I've removed and added back all plugins twice, only for the issue to reappear after a day or so. So, really trying to understand what is driving the issue. Right now Logic is pretty useless to me. Luckily I have Cubase and Ableton ;-) But that doesn't help when I have Logic projects I have to finish.


Jul 24, 2024 1:41 AM in response to yoyoBen

That is an interesting thought. Wonder why that may be in that case, as I've always seen UAD as an "MacOS" company. If that is the case, I'm not sure what to do with that, as I can't really ask UAD to rewrite its code for MacOS first and not use some sort of translation, if that is indeed what is happening. All I've done is to install whatever UAD has told me to install for MacOS. Mysterious.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Logic Pro crashes when clicking on audio FX

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.