I’m trying to build a modular architecture for Dsp signal processing blocks that i will use in my own graph and integrate in a plugin, in this matter I have some requirements about parameters handling.
I want all my parameters to be hiden to the DAW by default, but usable in an editing interface, and when my graph is done i want to be able to choose which parameters will be exposed to the daw.
I have some elements of answer taking into account this comment :
I cannot use AudioProcessorParameters or AudioProcessorValueTreeState for all my dsp signal processing blocks because depending on the DAW all my parameters would be exposed…
But I can use the ValueTree contained in the AudioProcessorValueTreeState. If i have a ValueTree in each of my blocks the i just need to add them to the ValueTree contained in AudioProcessorValueTreeState. This allows me to solve many parameters architecture issues (save/restore, undo/redo, coherence between all the objects, …).
What i don’t know is :
How to make some of my ValueTrees properties controled by an AudioProcessorParameters when i decided that i want this property as an exposed automatable parameter.
Can you see a solution to this? I have read the documentations but i don’t find a way to do it ! If i’m unclear feel free to ask anything !