Creating new plugin - standalone plugin host throws assertion on launch


#1

Sorry, this is probably an easy one but I can’t figure it out…
I just created a new plugin using the Projucer and I wanted to start fresh using the “Standalone Plugin” target.

I’m getting an assertion in AudioProcessor::getPlayConfigDetails.

// the processor may not support this arrangement at all
jassert (success && newNumIns == getTotalNumInputChannels() && newNumOuts == getTotalNumOutputChannels());

newNumIns is set to 1. This seems to come directly from the audio device (using a new 2018 MBP). getTotalNumInputChannels() returns 2.

My audio processor’s constructor looks like this:

TestAudioProcessor::TestAudioProcessor() :
AudioProcessor({{1,1}, {2,2}, {1,2}})
{}

Can anyone tell me what I’m doing wrong?
The plugin builds fine and loads in Reaper as VST 3.


#2

Looks like this is a bug from a recent change that I made. I’ll push a fix shortly.


#3

Thanks ed, much appreciated!