I’ve been using a simple parameterManager class in my VSTs. It’s basically an array of floats and get/set methods. I make one in the main filter constructor and pass the pointer out to all the classes it uses.
I’m thinking of making it into a more generic/reusable thing and theres a couple of things that could go into it.
Mapping of bools and ints to 0-1 floats for use with automation for one. It could be thread safe and simplify the connection of gui to parmeters, presuming it wraps the notifying-host bit.
And, and here’s where I’m out of my depth so to speak, it could have an option to generate the gui based on parameter meta data. Kind of like the VST standard gui but much nicer looking.
The point being that a new parameter only results in one or two new lines of code rather than 15 or so, and it could probably work well togther with VST2.4 where you can define the parameters more freely.
And then I thought, hey, if Jules did it, it might even work!
…I could probably do it myself, but I’m thinking it might make a nice addition to the framework.