Which VSTi's are you using? CW does a pretty good job for this already and of course it gets complicated.
Almost all VSTis rely on their own internal patch selectors (like IL, etc). I think what you want is a quick way to use a text file to define some patch maps, like a drum map but using the bank select/PC msgs with text for the VST. An .ins file system might work but I'm not aware that it can be done. I don't think that there are any linkages to particular VSTis and their states other than SyProperty page presets.
If handled kind of like drum maps it would be handy. If VSTs publish names/patches, CW uses them but only pretty old VSTs do these days. Of course, we'd need to be making/naming our own Patch maps and the folks at CW will never be able to help with unpublished mystery VSTi patch maps. For instance, I load up my Rapture and there isn't any patch map. I understand why and it isn't a problem.
Some of the internal CW VSTis do this. The GrooveSynth publishes a pretty detailed patch map available from the inspector, but it doesn't appear to be editable. It isn't particularly easy to use either. I just select patches directly from the VST and save the project. This does make some multi-timbral stuff awkward for those who like to use patch changes mid track rather than in a separate track. GM/S vstis do this pretty well usually, but those probably aren't one's you are asking about.
VSTis generally don't follow the midi patch/bank selection model, but creating new copies of a VST isn't a big CPU load to mix, match, edit patches. Auditioning patches is still a PITA, but I save synth presets when I'm getting close to something I like, and then CW is happy and selections are pretty easy.
My solution: Start with VST manual patch selection (can't do it by name from sonar directly), tweak, finish with a Synth preset save (and if needed a VST preset save or even a synth track template). Save-as new Project. Move on.
post edited by m.letcher@q.com - 2015/03/19 18:48:12