Instrument plug-in does not appear in Logic v11.

[Gen-MIDI]

I'm on a M4 Macbook. The audio and MIDI effects all work but the instrument plug-in is not available. It shows validated in the plug-in manager. Appreciate any help.

[Grovesnor]

I get a similar problem - although nothing works. I can load the plugin but the GUI doesn't appear and occasionally I get the Audio Unit has become unstable message. Did you get yours to work?

[Gen-MIDI]

No, haven't been able to get it show up at all.

[HexRebuilt]

Same issue on an M4 mini and Logic V11.1.2

[Mat808]

YES same here. Under Ableton 11 and 12 the AU works fine. Logic PRO 11.1.2 shows validated plug-in but does not
show in the instrument drop down list. FX shows up and is also working under Logic. Any idea. Pleas HELP.

[MrCoolSpan]

Same issue on an Imac I7 Logic pro V11.2 running Sequoia 15.4.1
Logic pro v10.8.1 working fine. same mashine

[kcoul]

I noticed this as well, REAPER also works fine. I think it is due to a change in auval that will need a fix. I'll look into it.

[rdoearth]

Interested in knowing the status for this. I have same troubles.

[MrCoolSpan]

Sorry nothing is happening
I thing for me is time to move to Cuebase

[kcoul]

This is one of the things I'll try and get fixed in an Interim release, it's probably due to the flexibility in the I/O negotiation. Logic v11 probably requires explicit support for even higher channel widths for spatial audio, I'm guessing.

[MrCoolSpan]

okay
let me know if i can help

[virgil9306]

@kcoul I saw your PR from earlier this year, and realized I might have duplicated your work in the OS bump for some of the JUCE update stuff (but not all: since then it seems more stuff has been deprecated). #1469

[beshanoe]

Solution is found! Source https://www.logicprohelp.com/forums/topic/149693-plugin-is-not-visible-in-the-list/

Do this and restart the Logic:

[virgil9306]

That is a very reasonable conclusion, that clearly explains why the AU plugins work in Reaper but not Logic @apohl79

Is Sentry different than what was used in version 1.1? Because in that one, the plugin works fine.
Or is there a way to disable Sentry? E.g. in the config file? I noticed some logging-related flags there.

--

@beshanoe Do you mind sharing the AU plugin files you built?

--

Update

I tried to build myself, but encountered errors due to various API and path changes.

Nothing huge, but, I made a draft PR just to demonstrate this: #1469

It builds, but I have not tested it or demonstrated it works, but leaving it as a reference in case it might be helpful.

[beshanoe]

sure, here it is https://mega.nz/file/21p0yJKJ#jrjOnKnULHNeTk6HTB7_p4IC5oU53Wl_HDZTK6AxbCk

Here's the patch to JUCE module that solved my build
changes.patch

[lepape23]

Hi beshanoe,

Thank you very much for providing the test build. I have performed the installation and testing on my machine:

• My Machine: Intel Mac (x86_64)
• DAW: Logic Pro (Latest version)
• Test Version Installed: AudioGridderPlugin_1.2.0_1_macOS-universal (from your shared ZIP)

Result:

Unfortunately, the issue remains unresolved, even after a full system cleanup (deleting old .component and .vst3 files, running sudo killall coreaudiod, reinstalling the universal version, and rebooting).

• AudioGridderInst.component Status (in Plug-in Manager): Still shows "Successfully Validated".
• AudioGridder (FX) and AudioGridderMidi (MIDI FX): Both are Visible and Functional in Logic Pro inserts.
• AudioGridderInst (Instrument): Still INVISBILE in the Instrument slot selection menu.

This seems to confirm a deep, persistent Logic Pro UI bug related to the AU instrument type categorization of this specific component.

I will now use the FX plugin as a workaround to continue working. Please let me know if you release a new test build focusing on this Logic Pro categorization issue.

Thank you again for your efforts!

[transfer91-sketch]

That is a very reasonable conclusion, that clearly explains why the AU plugins work in Reaper but not Logic @apohl79

Is Sentry different than what was used in version 1.1? Because in that one, the plugin works fine. Or is there a way to disable Sentry? E.g. in the config file? I noticed some logging-related flags there.

--

@beshanoe Do you mind sharing the AU plugin files you built?

--

Update

I tried to build myself, but encountered errors due to various API and path changes.

Nothing huge, but, I made a draft PR just to demonstrate this: #1469

It builds, but I have not tested it or demonstrated it works, but leaving it as a reference in case it might be helpful.

Hi @virgil9306 is the 1.1 build works fine with you? I tried to install but it doesnt work for me... both versions dont work

[DiligentPoetry]

For anyone still unable to fix the issue, try this, it might work

[DiligentPoetry]

Guys, I have a new fix you all to try,

Env:
macOS Seqouia 15.7.3 (UTM VM, ARM)
AGPlugin 1.2.0 ARM
AGServer 1.2.0 Windows (Crossover in VM)

Install the custom plugin (Inst only) as provided by @beshanoe here

Then try to, reset and rescan it in plugin manager (it should fail due to gatekeeper),

Go to Settings > Privacy & Security (scroll down) > AGInst.component <-> allow anyway

Post "allow anyway", rescan plugin, and load it in an instrument track in a blank project, it should show "dev-build" in the bottom left corner. Close DAW.

Reinstall AGPlugin (full) 1.2.0 as provided by @apohl79, the OG Inst component should work as usual now.

Weird fix I know, but this worked for me for some reason.