3rd party plugins greyed out in logic 11.2 during session

To further confuse the issue, I just installed Logic Pro 11.2 on a 2021 M1 Max MacBook Pro running OS 14.7.2.

Kontakt 8, the full range of SWAM instruments, and the UAD instruments all show up and work on this older and less robust machine and… they all work!

I'm guessing it might be an issue with my 2022 M1 Ultra Mac Studio rather than Logic.

Any suggestions? I've already tried uninstalling and reinstalling everything (including Logic) on the Mac Studio.

When I acquired a Mac Studio, I deliberately deleted every plugin that was not Apple Silicon native and I've not installed any plugin requiring Rosetta in the past three years. I don't think Rosetta is causing my UAD instruments issue.

For me, I have issues with Kontakt 8, UAD, Audio Modeling SWAM, and IK Multimedia Sample Tank. It seems limited to instruments not working on a 2022 M1 Ultra Mac Studio (even though they work on a 2021 M1 Max MacBook Pro on the same account).

Last night I updated the OS to 15.5 and today Modartt's Pianoteq 8 is gone.

In Plug-In Manager, Pianoteq shows as compatible and ready to use.

I've enjoyed my 20+ years with Logic Pro but I think the honeymoon is over.

Which DAW is the easiest transition from LP, Cubase or Studio One?

Looks like I'll be installing VST versions of plugins over the holiday weekend.

With hopeful anticipation, I installed the 11.2.1 update two days ago on both the Mac Studio and the MacBook Pro.

Alas, all of the 3rd party instruments mentioned previously are still AWOL on the Mac Studio (and still somehow working on the MacBook).

Has anybody had any success with the 11.2.1 update?

I've noticed that most of the instruments that are giving me problems on the Mac Studio are modeling (MODO Bass, Modarrt Pianoteq, UADx Ravel and Waterfall B3 organ, Audio Modeling SWAM instruments, etc.) rather than sample-based.

At any rate, I can't wait for Apple to address the issue so I sprang for Cubase 14 and, after installing VST3 versions of all my plugins, they all work on the Mac Studio.

It's definitely a Logic issue.

Same issue here, really ennoying to say the least.

My setup is a Macbook Pro with M1 processor, MacOS Sequoia 15.5 and Logic Pro 11.2.1.

I experienced the issue with Slate plugins (those are effects, not virtual instruments), and Waves plugins as well.

I have to mix a whole 1hr30 live session for a band, maybe I will use Reaper while waiting for a bug fix, but I don't know Reaper that well, I'ma lose lots of time...

@dwershba:

Thanks for the suggestion.

Every one of the missing 3rd-party instruments (Kontakt 7, Kontakt 8, Audio Modeling SWAM, IK's SampleTank, UAD's Ravel piano and Waterfall B3, Modartt Pianoteq, IK MODO Bass, etc.) have reappeared on my Mac Studio running Logic in Rosetta.

"Unfortunate" and unexplainable because every 3rd-party instrument I have is the latest version and supposed to be silicon native and not one of them ever disappeared from my M1 MacBook Pro.

We should not have to drive our silicon Macs with the handbrake of Rosetta applied.

I'm having this same issue. I already used the link to report to Apple. Any session I have that used any of my UAD plugins (which are all the latest versions), Kontakt (again, latest), or Soundpaint (latest) causes the same crash mentioned here. I restart Logic in safe mode and it tells me that they are all unavailable on my system.

Then I used the plugin manager and had it do a full rescan. It finds all of these plugins and deems them "successfully validated." I can then do a new test project and use any and all of them with no problem. But the minute I close that project and reopen it, crash, with same error code. I'm at a loss.

I have no way to revert back to 11.1 unfortunately.

Same here - On 11.2.2 now and most of my 3rd party AU Software Instruments don't even show up as avaialble for assignment window. They are all there in the Plug In Manager and show as successfully loaded - I am jumping through all sorts of hoops, but no joy. It is affecting a number of manufacturers' software, but not all so it's odd.

WAVES Electric Pianos; IK Multimedia Pianoverse and Spitfire LABS and BBC orchestra are coming to mind, but I'm sure there are many more I just haven't yet discovered.

Very odd and very frustrating

@dwershba: Very frustrating indeed.

Especially since all of the instruments that fail to appear in Logic on my 2022 Mac Studio are available in Logic on my 2021 Macbook Pro and in both Cubase and Luna on the Mac Studio.

FWIW, Spitfire's BBC Orchestra and their LABS are two of the 3rd-party instruments that are still available on the Mac Studio so it appears to be somewhat random and inconsistent in which virtual instruments get ignored on which system.

To date, I've submitted three tickets to Apple support and received one reply eight days ago asking for more details.

Good luck!

Not sure if you received my response - but in short, things were 'solved' with the unfortunate workaround of running Logic under Rosetta.

Not ideal but at least things are working, just slower than if run native.

Mac Studio

OS 15.5

M4 chip

I've had numerous plugin issues in LP 11 (all different versions).

I had an issue today after installing SSL Channel Strip 2. Logic said it was incompatible, as it has said with many plugins. Deleting and re-installing Logic has always worked for me. The only penalty is waiting while Logic re-indexes the Loops.

Thanks, @Johne154.

I've tried deleting a reinstalling Logic three times in the past month (plus, installing the updates to 11.2.1 and 11.2.2).

I'll give it another shot tomorrow but, to date, the only solution seems to be running Logic in Rosetta.

It's a shame we have to work as if we're still in 2019.

Hi jackinvox,

I have deleted and re-installed Logic probably 3 or 4 times this month and it's so quick I don't even think about it, I just do it. Since installing Logic in May, I've lost track of how many times I've deleted it and re-installed it.

I never had to uninstall and re-install a DAW all the time like I'm doing with Logic. But, I just accept that it's a glitchy part of the process and it keeps fixing Logic and getting it back working for me—through every version of Logic 11. My best advice, don't let it frazzle you, just do it, and expect the best. 😎

Cheers,

John