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.
–
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
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
Thank you, but unfortunately this did not help… But Logic did not rescan the plugins again after running your command on Terminal. But Logic should do this or?
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.
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)
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