Map plugin parameters through GUI

[rbuskov]

I’m building a host in JUCE and need to map plugin parameters. I would like to do this by letting the user click controls in the plugin’s AudioProcessorEditor (Ableton Live style).

Is there a way to do this in JUCE?

I have noticed the getControlParameterIndex (Component &) method in the AudioProcessorEditor class which looks promising, but I can’t figure out how to use it.

I have tried handling mouse up events for the plugin’s AudioProcessorEditor to see if that might give me a component reference I could use, but I can’t seem to intercept mouse events for this particular component.

[daniel]

Unfortunately the method getControlParameterIndex() says:

Currently only AAX plugins will call this, and implementing it is optional.

I think the best way is, if you are in learn mode, to intercept all beginGestureChange() messages and link to the first one arriving, switching the learn mode off.

[rbuskov]

@daniel OK, that should do the trick I wasn’t aware of the AudioProcessorListener at all.

[daniel]

Be careful with AudioProcessorListener, it seems not to do what it suggests. I got bitten, see this thread:

AudioProcessorListener is not notified when host changes parameter

The AudioProcessorListener is only notified, when a parameter is changed via AudioProcessorParameter::setValueNotifyingHost(). But if the host performes the automatization it calls setValue rather than setValueNotifyingHost (which makes perfect sense). But the listener doesn't get this changes notified. Wouldn't it make sense to move the notification to setValue so that the listener gets every change?

On the other hand, the AudioProcessorValueTreeState::Listener unfortunately only sends valueChanged(), it would be great if they could send beginGestureChange() and endGestureChange() as well for exactly that purpose.