4.1. setPreferredBusArrangement() mono-stereo or same Ins/Outs

Audio Plugins
41

It should read and/or. I'll fix this...

any idea when we can expect the Host to support multi-bus ?

We are a bit behind with some other work but it's definitely in our backlog.  I think we'll wait until the multi-bus stuff is tried and tested on the client side before we start implementing the hosting.

 

42

I can confirm this fixed the mentioned issue I saw with my own plugin and with the Juce audio demo plugin.

Thank you Fabian!

43

I’m using JUCE 4.2.2 (hence the fix mentioned by @fabian above should be included)

My plug-in doesn’t have additional buses and uses the legacy channel configurations as specified below:

#define JucePlugin_MaxNumInputChannels      2
#define JucePlugin_MaxNumOutputChannels     2
#define JucePlugin_PreferredChannelConfigurations  {2, 2}, {1, 1}, {1, 2}

Despite that, I am still getting the “1 in 6 out” configuration listed in Plogue Bidule for the VST2 plug-in.

Could this be a regression in JUCE?

Is there something more I must do to get rid of that config?

44

Yes, I believe you’re right: this seems like a regression indeed.

I did this:

  • made sure no remaining JUCE audio plugin demo dlls were left in my VST2 paths
  • pulled latest JUCE (master branch) and built Projucer
  • opened JUCE audio plugin demo project
  • changed channel settings to {1, 1}, {1, 2}, {2, 2}
  • unchecked VST3
  • saved project
  • built in VS2015
  • moved built dll to VST2 plugin path on my system
  • opened plugin in PlogueBidule (32-bit)

–> Bidule again shows:
1 ins 1 outs
1 ins 2 outs
1 ins 6 outs <--------
2 ins 2 outs
default ins default outs

Note that if I keep the original channel settings {1, 1}, {2, 2} (and again uncheck VST3), the plugin does correctly show up in Bidule with:

1 ins 1 outs
2 ins 2 outs
default ins default outs

I didn’t have the time right now to find out where the regression happened.
Not sure how to flag regressions in the forum, but I assume someone from the JUCE team will pick this up.

45

Ah so it seems to be somehow linked to the presence of {1, 2} in the list of supported channels.

I guess @fabian is the one in the JUCE team that works on the multi-bus stuff. I’m tagging him here in the hope he’ll have a look at this (a bug-tracking system to reopen the issue would be very convenient in this case)

46

@fabian or @jules Could you have a look at this issue, please?
I just updated to JUCE 4.2.3, and I still get (1-in, 6-out) as one of the 4 (not 3) possible plugin configurations.
The problem still also exists with the JUCE audio plugin demo, if you add {1,2} as explained above.
This problem had been fixed on Febr. 4th, but is back now.

By the way: are there other hosts where it is easy to see which configurations are supported by the plugin?

47

OK this is fixed on the develop branch now. For some reason, Bidule sends invalid VstSpeakerArrangement requests: it sends a VstSpeakerArrangement with type stereo but sets the number of channels to 6. I’ve now added a sanity check to the setSpeakerArrangement method.

48

I can confirm this fixed the issue also for my plugin.
Thanks Fabian!