Projucer Audio Plugin standalone

[apple412]

Hi @fabian

So actually had kind of a similar thing happen to me the other day, as outlined in this post:

Mono/Mono AU fails to load in Live, "This Audio Unit plug-in is not compatible. Failed to initialize."

Hi All, I am building a plugin using the AudioProcessorGraph model and running into a bit of an issue. The plugin for now should only support mono input and output. For the VST3, everything is working well, you can add it to a track in Live and it is added to the track without complaint. The plugin only outputs the left channel of the input, but that is as expected until we get around to fixing that. If you attempt to add the AU version of the plugin, however, you get the error message: "Fai…

Although in looking into it further, it seems that this may not be the correct fix, as described in your answer here:

Projucer Audio Plugin standalone

Sorry I should be more clear. In JUCE you either choose to use the JucePlugin_PreferredChannelConfigurations define or override isBusesLayoutSupported. In any case, if you are using the standalone target, then you need to alter your plug-in so that it supports zero channels as an input. This means that you would have to alter the Projucer’s audio plugin default template code to also support zero input channels, when adding the standalone target to the project. If you are using JucePlugin_Prefe…

I’m not sure which one is the correct answer. In my experience over the last few days you have to do BOTH JucePlugin_PreferredChannelConfigurations AND isBusesLayoutSupported for VST/AU to work correctly in all cases, but this post seems to indicate otherwise?