Logic does not find my Audio Plugin

Hey there!

I am new to JUCE. For this I just did the tutorial “Tutorial: Create a basic Audio/MIDI plugin”.

Everything works, my plugin is placed here:

In this folder, it is the only one.
The other plugins I commonly use within Logic are placed here:

Now, I did a restart of my Mac, went to Logic and wanted to try out my plugin. But, I can’t find it within the Plugin Manager at all.

Can you help me with this issue? Thank you in advance!

Best regards from Germany

should be “/Users/YourUserName/Library/Audio/Plug-Ins/Components”.

Cannot handle Logic both folders at once?

Yes, it can but “/Users//Library/Audio/Plug-Ins/Components” is not a valid path, the user name is missing. Are you sure the plugin is well installed? If your plugin is well installed, I recommend you use auval Tool and/or pluginval to test the plugin.

Yeah, you’re totally right, sorry for that.

All the third party plugins (FabFilter and so on) are installed here:


My own audio-plugin, written with the help of the JUCE Tutorial is saved here:


But anyway, Logic does not recognize my plugin, even if I copy it from




If I try to test it with auval, I get the following result:

username@My-MBP Components % auval -f FirstBasicPlugin.component

    AU Validation Tool
    Version: 1.10.0 
    Copyright 2003-2019, Apple Inc. All Rights Reserved.
    Specify -h (-help) for command options


Thank you for your help!!!

auval -f FirstBasicPlugin.component

is not valid, -f should specify a text.

First, you should list your components:
auval -a
Then find you component in the list and test it by using the 4 digits specifying the TYPE SUBT MANU, for example:
auval -v aufx Stpc Ircm

Ok, did it:

auval -v aufx Gnfy Manu

outputs a lot, but in the end


So, it seems that everything is working correctly?

So, I am still asking myself, why Logic does not find my plugin?!

Sometimes Logic’s cache gets stuck for some reason. In that case, running

killall -9 AudioComponentRegistrar

can help.

Thank you, but unfortunately this did not help… :confused: But Logic did not rescan the plugins again after running your command on Terminal. But Logic should do this or?

Did you try Full Audio Unit Reset in the Plugin Manager?

Yeah, just did it, but nothing new… :confused:

Is there maybe a mis-configuration or something like that?

Sometimes it can get stuck.

First I would see in Logic → Settings → Plugin Manager.
Check the list if your plugin appears. You can click the plugin and run auval directly inside logic “Reset & Rescan Selection”.

Next thing, did you look in the right place? FX and Instruments are shown at different places.

And your plugin needs to support that channel layout. auval will show the channel layouts that it should support.

The sledge hammer method is to rm the ~/Library/Preferences/com.apple.logic.pro.cs. It will forget everything else though.

EDIT: just see PierreGuillot beat me to it, sorry

Also, you can check if this is unique. If you duplicated Juce project, change the name of the plugin but didn’t change the plugin code, perhaps Logic is scanning the previous one and ignore the current one?

Are you building on a computer with Apple Silicon chip?
If so, the problem could be that in Xcode you are building for one architecture (for example, ARM), while the DAW you are running expects a different one (for example, Intel if you have instructed your DAW to run in Rosetta2 mode)

Yeah, I was just typing… and wanted to write, that nothing helped…

My last guess was maybe the OS version, or using Rosetta when starting Logic.

Your guess is totally right, I have a MacBook Pro with the M1 chip, and starting Logic using Rosetta.

So, this seams to be the problem…?! But, how to fix the issue? Does JUCE have any opportunities for this issue?

At the top of the Xcode window, there should be an area that says “My Mac”. Click that and choose “My Mac (Rosetta)”, that will build using the Intel architecture.
Leaving it on “My Mac” will build (as you probably guessed) only for the native architecture of your computer (hence ARM), while “Any Mac” will build a Universal Binary that will contain support for both architectures, if I recall correctly

This is it!! You fixed my problem… And saved my day!! :slight_smile:

Thank you all for your help!! Really appreciate it!

Take care

1 Like