AudioProcessorValueTreeState with branched ValueTree

[mashu]

It seems that using AudioProcessorValueTreeState with createAndAddParameter(…),it is only really possible to add parameters directly to the main value tree.

What about in more complex situations, where it would be appropriate to have a ValueTree with several children, and those children having more children…etc?

Is there already a way to createAndAddParameter(…) to children of the ValueTree? Or would i have to figure out a way to do that for myself?

[daniel]

To repeat myself, the parameters aren’t stored in the ValueTree at all:

Alternative to accessing ValueTree in processBlock?

I always guessed, but now I looked it up: The parameters are not stored in the valuetree! The AudioProcessorValueTreeState combines a ValueTree and the list of parameters to make it easy to serialise the state of a plugin/processor. The parameter ends up in an OwnedArray in the processor. Here is the code: This makes perfect sense, if you remember, that the actual value of a parameter is not part of the plugin state, because it is depending on the host’s automation. So there is no need t…

As hosts have no interface for hierarchical parameters, it makes no sense to add parameters (that are available to the host) into the tree.