isBusesLayoutSupported(), AUVAL and mono/mono configuration (SOLVED)

[zabukowski]

My code:

bool MyAudioProcessor::isBusesLayoutSupported (const BusesLayout& layouts) const
{
    if (layouts.getMainInputChannelSet().size() != 1 && layouts.getMainInputChannelSet().size() != 2 && layouts.getMainInputChannelSet().size() != 4)
        return false;
    
    if (layouts.getMainOutputChannelSet().size() > 2)
        return false;

    return true;
}

Trying to support 1,2 or 4 inputs and max. 2 outputs.

Now the AUVAL result is following:

Reported Channel Capabilities (explicit):
      [1, 2]  [2, 1]  [2, 2]  [4, 2]  

Input/Output Channel Handling:
1-1   1-2   1-4   1-5   1-6   1-7   1-8   2-2   2-4   2-5   2-6   2-7   2-8   4-4   4-5   5-5   6-6   7-7   8-8
      X                                   X                                                                       
WARNING: Can Initialize Unit to un-supported num channels:InputChan:1, OutputChan:1

I don’t understand what am i doing wrong? Why 1in/1out is not supported? Also in Logic X, mono - mono version of plugin is not available.

JUCE 4.3.1

Edit: further debugging reveals that i am not even being asked if 1/1 is supported - any idea why ?? Also tried with JUCE Plugin Host - the same story.

[zabukowski]

My default layout is:

	static BusesProperties getDefaultLayout()
	{
		BusesProperties buses;
		buses.addBus (true, "input", AudioChannelSet::stereo());
		buses.addBus (false, "Output", AudioChannelSet::stereo());
		buses.addBus (true, "Sidechain", AudioChannelSet::mono());
		return buses;
	}

[daniel]

And presumably you have nothing specified in the Projucer field “Plugin Channel Configurations”…

The AudioPluginHost is not suited for that test afaik, since it does no channel negotiation, but plays the default from the constructor.

Another thought, some hosts might play as multiple mono instances without telling you, for the user’s convenience?

The code looks correct to me, but for readability I would write:

bool MyAudioProcessor::isBusesLayoutSupported (const BusesLayout& layouts) const
{
    const auto numInput = layouts.getMainInputChannelSet().size();
    const auto numOutput = layouts.getMainInputChannelSet().size();

    if (numOutput > 2)
        return false;

    if (numInput == 1 || numInput == 2 || numInput == 4)
        return true;

    return false;
}

[zabukowski]

No “Plugin Channel Configurations” here.

Code is a quick example, full code is actually a bit more complex, but i did some experimenting so it is not really an example of effective & pretty programming, hehe.

Not sure what is going on here - why AUVAL is not asking me for 1/1 layout? The consequence is that mono-mono plugin is not available in Logic.

I found something else: if i change output bus of my default layout to AudioChannelSet::mono(), then i am being asked about 1/1 config. But then same problem occured with 1/2 config !?!

Could it be something wrong in 4.3.1 which has been fixed later Have to try it with version 5.

[zabukowski]

Another observation: if i don’t limit outputs in any way, am i being asked properly about 1/1 layout every time.

Any idea would be greatly appreciated!

[zabukowski]

OK here is the latest test - macOS 10.13.6, Xcode 9, the latest JUCE5 commit from development branch.

Using JUCE AudioPluginDemo project and your code:

bool isBusesLayoutSupported (const BusesLayout& layouts) const override
{
    const auto numInput = layouts.getMainInputChannelSet().size();
    const auto numOutput = layouts.getMainInputChannelSet().size();
    
    if (numOutput > 2)
        return false;
    
    if (numInput == 1 || numInput == 2 || numInput == 4)
        return true;

    return false;
}

AUVAL result:

Reported Channel Capabilities (explicit):
      [1, -1]  [2, -1]  

Input/Output Channel Handling:
1-1   1-2   1-4   1-5   1-6   1-7   1-8   2-2   2-4   2-5   2-6   2-7   2-8   4-4   4-5   5-5   6-6   7-7   8-8
X     X     X     X     X     X     X     X     X     X     X     X     X                                         

WARNING: Source AU supports multi-channel output but does not provide a channel layout

Obviously something is not right here ?!? Can you please look at it …

[daniel]

@zabukowski

Obviously something is not right here ?!? Can you please look at it …

I have to deflect to the JUCE team, I left Roli a while ago

I hope they find something, good luck!

[zabukowski]

Ah, sorry … thank you, Daniel !!!

[HowardAntares]

@zabukowski

const auto numOutput = layouts.getMainInputChannelSet().size(); if (numOutput > 2) return false;

In this code you are setting numOutput using getMainInputChannelSize(), instead of getMainOutputChannelSize(). Is that the problem?

[zabukowski]

Big thank you for spotting this!!! Obviously a “BAD” typo

Anyway, things are now working as expected with JUCE 5, but not with JUCE4.3.1 !!!

Looks like there must be a post 4.3.1 patch which fixes this behaviour - i will check it again, to be 100% sure. If anyone have a slightest idea, which commit this could be, please let me know. Looks like i will have to dig into this deeper - maybe somebody from Roli could chime in …

[apple412]

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 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?

[daniel]

Ouch, sorry, seems I introduced that typo… your original didn’t have that…
Thanks @HowardAntares for spotting that

[zabukowski]

I’ve checked things again to be 100% sure.

The same code from above works with the latest JUCE5 commit. It doesn’t work with JUCE 4.3.1 (mono/mono layout is missing with AU).

Now i just have to find when and how this was fixed.

[zabukowski]

Found it - this is the commit, which fixes 1/1 layout with AU plugins.

AudioUnit PlugIns: Tidy up some AU wrapper code and fixed a bug which could lead the AU to report an incorrect AUChannelInfo

[zabukowski]

Worth looking into this one as well …

AU: Fixed a typo in the AU wrapper shared code

[matkatmusic]

Does the AudioPluginHost still not let us choose Mono versions of our plugins for testing?

[daniel]

It does, right click on your plugin and select “Configure AudioIO”:

It might have been there all the way, I just found it recently.