Breaking change: Added an option to declare plug-in parameters as either continuous or discrete, irrespective of their number of steps

I haven’t updated yet, but it seems to me that your commit breaks much more things than just this continuous/discrete thing.

you have replaced many calls like those:

audioProcessor.getParameterDefaultValue (parameterIndex)
processorParam->getDefaultValue()
 juceFilter->isParameterAutomatable (index))

by the (not so) new AudioProcessorParameter class ‘equivalents’:

processorParam->getDefaultValue()
param->isAutomatable()

Isn’t it going to break all the plugins for people that are still using those AudioProcessors methods?
I know those that are commented with :

 NOTE! This method will eventually be deprecated! It's recommended that you use
        AudioProcessorParameter::isAutomatable() instead.

but they haven’t been deprecated yet, and many people are not using AudioProcessorParameter yet:

1 Like