3rd party plugins greyed out in logic 11.2 during session

I have already helped a couple of folks by doing this.

I would remove all 3rd party plugins from your components folder to see if this is an issue outside of Logic Pro. Simply save them to a folder on your desktop. If you need me to show you how to do this, just let me know, and I am happy to walk you through it. BTW hold CMD as you drag these files out so you do npt duplicate but rather remove them from the Components folder.

Logic Pro 11.2 has been kind of tricky so your troubleshooting needs to be methodical.

Once everything is working smoothly. You are going to have to insert components Alphabetically or by Manufacturer. This is what I did and I was able to locate the problem. I dragged in every plug-in that starts with the letter "A" and then I would up up Logic. If everything went smoothly, I would then quit Logic Pro and drag in the next letter "B". Open up Logic Pro and if Group "B" went well, you can continue on with this experiment until Logic Pro hangs. Once things start getting wonky, you can surmise that this is the group giving you the issue.

This is the only way to see which plug-in is potentially causing the issue. If you need screenshots LMK and I will provide.

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

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.

@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.

The temporary solution was mentioned in this thread:

1. Revert to 11.1.2 (If you have a back-up copy) or
2. Remove all 3rd party plugins from your components folder to see if this is an issue outside of Logic Pro. Simply save them to a folder on your desktop. If you need me to show you how to do this, just let me know, and I am happy to walk you through it. BTW hold CMD as you drag these files out so you do npt duplicate but rather remove them from the Components folder.

Logic Pro 11.2 has been kind of tricky so your troubleshooting needs to be methodical.

Once everything is working smoothly. You are going to have to insert components Alphabetically or by Manufacturer. This is what I did and I was able to locate the problem. I dragged in every plug-in that starts with the letter "A" and then I would up up Logic. If everything went smoothly, I would then quit Logic Pro and drag in the next letter "B". Open up Logic Pro and if Group "B" went well, you can continue on with this experiment until Logic Pro hangs. Once things start getting wonky, you can surmise that this is the group giving you the issue.

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.

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

How do you know (for sure) you have not downloaded plug-ins that require Rosetta? Are you using this?

https://apps.apple.com/de/app/pluginfo/id1626412949?l=en-GB&mt=12

FYI, It so happened that after I posted to this thread, my new M4 Mini arrived the next day. After getting it set up and downloading everything, the crashing issue has stopped and all of my plugins work again, whether Apple or 3rd-party. It seems like for me at least, the Logic 11.2 upgrade was only a problem because I was on a much older Mac. Even though I had the latest Sequoia running, the Intel Mac was my issue.

I've installed and run Kontakt 7 and Kontakt 8 players in native mode.

You might try what always worked for me. Deleting and re-installing Logic.

1. Go Here: Feedback - Logic Pro - Apple
2. Feedback Type: “Broken feature/Report a problem”
3. Comment: Please provide a detailed description of the issue you encountered and the troubleshooting steps you have attempted thus far. Include the URL of this thread for reference.

This is a good place to start.

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.

It seems it is a 3rd Party Plug-in issue (with 11.2). I am basing this on the last couple of weeks. So many people have posted about this single issue. I can tell you that it runs much smoother on 11.1.2 for sure and does not happen as often for me on my main rig. I am 💯 staying one version behind (for a while).

When I Produce, I am heavily dependent on 3rd party tools. Logic's plug-ins are useful and impressive but I choose to work with other tools as they have become a staple of my workflow. For those of that need to use other tools, we simple cannot move forward with efficiency.

The question is...

Is this Logic Pro's issue or

The manufacturer that you bought your plug-ins from? 🤔

@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!