I was hoping that the midi program change node was going to work generically for this… but apparently steinberg and vst3 and some of the plugin developers are not willing to play the game.
But I think this is sort of better…
Could we have the ability to save the state of the hosted plugin as one of a list of named presets within the plugin host node but not specific to that instance, so that the list can be accessed in future instances of the plugin host node for that specific vst plugin. Those individual presets in that list of presets should then be accessible via a pin in so that we can change presets on the fly.
It could be done like state morph/state, but there would have to be some way of saving presets to a list that does not go away so that they can be used over and over again… sort of like what unify does.
Hope that all makes sense.
Sorry… adding things as I think of them while doing other things:
The preset version of the state node could have a header dropdown that lists vsts that have had preset states saved for them and then there would be a child dropdown that lists the saved presets for that vst to choose from, which then sets up the host plugin node.
That’s it.