Can we get a little explanation as to why the JUCE folks chose what they chose for these very important methods?
virtual void AudioDeviceManager::audioDeviceIOCallback (const float **inputChannelData,
int numInputChannels,
float **outputChannelData,
int numOutputChannels,
int numSamples)=0
virtual void AudioProcessor::processBlock( AudioBuffer<float>& buffer,
MidiBuffer& midiMessages)
static void AudioBlock::process (const AudioBlock< SampleType > &inBlock,
AudioBlock< SampleType > &outBlock,
const FunctionType &function)
template<typename SampleType >
template<typename ProcessContext >
void FIR::Filter< SampleType >::process ( const ProcessContext & context )
void AudioSource::getNextAudioBlock(const AudioSourceChannelInfo & bufferToFill)
seems like every class has their own name and signature for processing a block of audio samples… Why not be consistent and provide the same name and method signature since they’re all doing the same thing: processing a block of audio samples