Why/when to use AudioProcessorParameterGroup?

[HowardAntares]

I’m porting an old (pre-JUCE) plug-in to JUCE 5.4.7, and am just wondering, why and when would I want to use AudioProcessorParameterGroup, instead of just RangedAudioParameter(s)? My plug-in has a lot of parameters, which seems like might be the reasoning for this kind of thing. Is that what they are for… just to gather related parameters into a collapsible display (for hosts that support that)? Or is there another reason? Do they help, for example, with meta-parameters (parameters that cause other parameters to change)? Thanks!

[reuk]

Yes, groups are designed for organising related parameters. Groups don’t affect the functioning of individual parameters.

[t0m]

Unfortunately there’s a fair bit to think about:

Plug-in parameter groups

Hello everybody. We’ve just added support for parameter groups to the develop branch. https://github.com/WeAreROLI/JUCE/commit/7e1db1aa4f2e29776f31fa39df4fdfff5e13ca19 Hopefully the new functionality is relatively straightforward. Now, in addition to calling AudioProcessor::addParameter, you can also call AudioProcessor::addParameterGroup, which adds a nested tree of parameters and subgroups. Parameters added in this way will be ordered by a depth-first group traversal. However, there are s…