I have two plugins, Fors Pivot (v1.1.0) and Synchrony Symbolic Music (v1.0.6), that have been successfully installed, show up no problem in the plugin manager, but just don't show up in the plugin list. Both are instruments, so it's not like I'm looking for a surround processor in a stereo track or anything. If I use a chainer like Blue Cat's Patchwork both load from the AU versions without issue. They just aren't in the plugin list. In the case of Pivot, I also have installed another synth, Junior, from the same dev, and it works no problem. I'm not about to die on a hill for either of these, but I'm intensely curious as to whether anyone else has had this problem with these or any other plugins.

Mac Studio M1 64GB, Sequoia v 15.7.5

 

The plugin list of what?

 

Did you try xattr/codesign fixes? Hopefully you already did..

sudo xattr -cr "/Library/Audio/Plug-Ins/Components/Plugin.component"

codesign --force --deep --sign - "/Library/Audio/Plug-Ins/Components/Plugin.component"

Go to Logic Pro → Settings → Plug-in Manager and look at the developer list on the left side first. Since it’s alphabetical, it’s often the fastest way to see whether the developer is even being detected by Logic at all.

You can also click the “Compatibility” column on the right side to sort the plugins. The successfully validated plugins will group together, and anything that failed validation, crashed during scan, or was skipped usually becomes easier to spot near the bottom.

Since it loads fine as an AU inside PatchWork, the plugin itself probably works.

On Apple Silicon Macs, another thing worth trying is launching Logic itself under Rosetta once, letting the plugin scan there, then switching Logic back to native mode afterward. Sometimes that’s enough to get plugins recognized.

Otherwise, rebooting or clearing Logic’s plugin cache and forcing a rescan can also fix it.

I'm on Catalina, so these are just some tricks you can try.

 

Yes, I have. Other than @clone's excellent advice and tips, I can tell you that I've encountered a similar issue with some of my Roland plugins (D-50 etc) when I updated my OS and Logic. I could load and use them (the D-50 and others) in DSP-Quattro, but not in Logic.

The issue seems to have been that Logic relied (then) on some files/libraries that came with iTunes. When I updated my OS, and my blue iTunes icon was replaced by the red Music App icon, those libraries were no longer available - and Logic apparently relied on them.

Eventually, Roland Cloud released an update, which I installed, and which restored all Roland plugins access in Logic - all good now.

The above background and preamble for the only tips I've got that :

• 1) if you're not using ware'd versions, contact the developers and ask them for an update (or manual installers)
• 2) if you are using ware'd versions, then try to find a standalone iTunes installer, install it, re-install the two plugins

 

Just to be clear, the plugins are not rejected by Logic, or somehow incompatible - they both show up in Logic's Plugin Manager as compatible, and I can load them in Logic through a plugin chainer and they work fine. They just don't show up in the plugin list when I go to select an AU plugin. And yes, I did a batchmod and a deep codesign on both of them. In the case of Pivot, I had an earlier version installed before and it behaved the same way. Anyway, thanks for the suggestions in any case.

 

could it be something as silly as just being categorized / grouped in the wrong section? Or named something different. Instead of being Pivot, its FPivot. Or something dumb like that.

 

Spoiler: Perplexity KI

What you’re describing usually points to a Logic cache or registration quirk rather than a true AU compatibility problem, especially since both plug-ins pass validation in Plug-in Manager and load fine inside Patchwork. On macOS/Logic, the most common fix is to do a full Audio Unit reset, clear the AudioUnitCache, and then restart the Mac so Logic rebuilds its plug-in inventory cleanly.

What this likely means
If a plug-in appears in Logic’s Plug-in Manager but not in the insert/instrument list, Logic has generally already found the component and just isn’t exposing it correctly in the UI. Apple’s own troubleshooting for missing Logic plug-ins recommends using Plug-In Manager’s Full Audio Unit Reset, then clearing the AudioUnitCache and restarting the computer so Logic rescans everything. Similar vendor guidance says to delete com.apple.audiounits.cache from ~/Library/Caches/AudioUnitCache/ and then relaunch Logic.

Why those two synths may be different
The fact that Junior from the same developer shows up normally suggests the issue is not simply the developer, the signing, or Apple Silicon support in general. Since both Pivot and Synchrony work as AU instruments inside a chainer, the most likely explanation is that Logic is mis-categorizing or failing to surface those specific AU entries in its browser rather than rejecting the plug-ins outright. That pattern is consistent with cache corruption or an outdated Logic plug-in database rather than a broken install.

Best things to try

• In Logic’s Plug-In Manager, select each plug-in and choose Reset & Rescan Selection.
  
  
• Use Full Audio Unit Reset in Plug-In Manager, then quit Logic and reopen it.
  
  
• Delete the Audio Unit cache file at ~/Library/Caches/AudioUnitCache/com.apple.audiounits.cache, then restart the Mac.
  
  
• Check whether the plug-ins appear if you launch Logic after a full reboot rather than just relaunching the app.
  
  
• Confirm the .component files are in /Library/Audio/Plug-Ins/Components/ and not just present in a chainer’s AU scan path.
  

What your details suggest
Your mention of batchmod and deep codesign makes it less likely this is a quarantine or signature issue, though those can still matter in some cases. Since Logic’s manager says they’re compatible and Patchwork can instantiate them, I’d treat this as a Logic registry/listing problem first, not a plug-in failure. If they still do not appear after a cache reset and full rescan, the next most plausible explanation is a developer-side issue with the plug-in metadata that affects Logic’s category listing even though the AU itself loads.

Practical read
So yes, other people do run into the “shows in manager but not in the list” problem, and the standard fix path is exactly the cache/reset/reboot sequence above. Given your setup, I’d expect the answer to be “Logic is caching something odd” more than “these synths are fundamentally incompatible.”

 

-Reformat your computer
-Use bootcamp to install Windows
-Allocate the largest part of your hard drive possible to Windows
-Set windows as your default OS to boot into (can't remember the proper terminology anymore)
-Install Reaper
-Never look back

 

This sort of clarifies it - sort of confuses me, tbh. If they load and they play, the only issue is selecting them manually and individually from a list then? Is that it? (Some screenshots would help greatly, now or next time, please).

This happened to me too - as @shinyzen intuited, it could be a mislabeling of your plugins.

1. Go to FInder
2. Cmd+Shift+G
3. /Library/Audio/Plug-Ins/Components
4. RMB+Show Package Contents on your offending plugins
5. Open Subdirectory
6. RMB+Text Editor (I use TextMate) on the info.plist file
7. Check that the company and plugin names correspond to what you expect to see.
   (see screenshot below for illustration)
8. If they don't, or if you want to reorganize your plugins, you can edit the plist accordingly (make a backup first)
9. If they do, if all the fields match what you see or would expect to see, change them anyway, to make sure they follow.
10. It's all I got for now - until you send those screenshots (always send screenshots and/or video with support requests).

 

Patchwork is usually more forgiving because it just tries to host the plugin directly. Logic is stricter since every AU has to pass Apple’s AU validation tool first. So a plugin can technically still “work” inside Patchwork while failing AUVal over things like permissions, signing, sandboxing, bad metadata, or minor spec violations that Logic will not ignore.

I frequently use Patchwork to load something one time, first in standalone mode, and then in Logic if it still doesn't show up.

Check to make sure Logic does not consider the plugins "midi controlled effects".

Spoiler

The “MIDI Controlled Effects” menu only appears on channel strips that can actually receive MIDI input for plugins. In Logic, that is usually software instrument tracks or certain instrument channel strips — not regular audio tracks.

So if someone cannot find that menu, a common fix is:

• create a Software Instrument track
• click an Audio FX insert slot
• look for the “MIDI Controlled Effects” category inside the AU menu

A lot of people search on an audio track and assume the plugin is missing when Logic is just hiding incompatible plugin types for that channel strip.

There's a method of bypassing or forcing validation on newer MacOS versions, but it is pretty technical and i'm not going to post it here since I haven't ever had to try it.