# Why/when to use AudioProcessorParameterGroup?

**URL:** <https://forum.juce.com/t/why-when-to-use-audioprocessorparametergroup/38562>\
**Category:** Audio Plugins\
**Created:** [April 8, 2020, 3:56pm UTC](https://forum.juce.com/t/why-when-to-use-audioprocessorparametergroup/38562 "2020-04-08T15:56:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [April 8, 2020, 6:23pm UTC](https://forum.juce.com/t/why-when-to-use-audioprocessorparametergroup/38562/3 "2020-04-08T18:23:05Z")

</div>

Unfortunately there’s a fair bit to think about:

> [@Plug-in parameter groups](https://forum.juce.com/t/plug-in-parameter-groups/29409):
>
> Hello everybody. We’ve just added support for parameter groups to the develop branch. [https://github.com/WeAreROLI/JUCE/commit/7e1db1aa4f2e29776f31fa39df4fdfff5e13ca19](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…

---

_[View the full topic](https://forum.juce.com/t/why-when-to-use-audioprocessorparametergroup/38562)._
