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.