This happens with latest tip, under Linux, when compiling an audio plugin with the standalone wrapper: stdout is spammed with the message
“JUCE Assertion failure in /home/johannes/code/juce-git/src/audio/dsp/juce_AudioSampleBuffer.cpp, line 82”
Only happens with the Standalone wrapper, not with the VST wrapper.
In my JucePluginCharacteristics.h, JucePlugin_MaxNumInputChannels is #defined as 0, and JucePlugin_IsSynth as 1. When I #define JucePlugin_MaxNumInputChannels 2, problem goes away.
Is it illegal to have zero input channels? I thought it would be logical for a synth. I’m not processing any audio input, only generating output.
Another (unrelated) problem with latest tip is that Linux GUI programs use 100% CPU after a while. There seems to be some kind of short-circuit in message processing. I’ll post about this later when/if I find out more.
I know that Jules is on holiday so I’m not expecting the usual immediate fix
Am I missing something here? When I set the number of audio inputs to 0 in the Plugindemo, there is no output sound! I don’t want any audio inputs into a synth I’m creating.
Well I figured it out. These two lines of code should not be there.
// In case we have more outputs than inputs, we'll clear any output
// channels that didn't contain input data, (because these aren't
// guaranteed to be empty - they may contain garbage).
for (int i = getNumInputChannels(); i < getNumOutputChannels(); ++i)
buffer.clear (i, 0, buffer.getNumSamples());