I’m using an XML specifications file that allows my plug-ins to dynamically infer an
AudioProcessorValueTreeState::ParameterLayout for the processor, plus create a GUI in the editor, and also automatically make any attachments between Components and parameters. This works like a charm for plug-in parameters (exposed to the host).
But I’d like this flexible mechanism to also support “realtime properties”. They would be properties that belong to the processor. The processor could read/write them (from
processBlock()). But the editor could only read them. And would not be visible to the host (they also don’t need to be stored/recalled).
Of course, I can achieve this manually (like using atomic variables in my processor and read them by polling in my editor), but my wish is to have something with the same benefits of an APVTS: named parameters, lambdas for string<>value conversion, etc.
Frankly, I though about using another APVTS but they have to be tied to a processor, and I’m less than sure about thread safety concerns…
Any suggestion or advice?
Thanks a lot.