Yep, started with the birth of what is now Media Bay. Not crazy to just you either. It is crazy. Fortunately many 3rd party vendors are just hand jamming the capability into their plugs.
This is quite true.
The mechanism to input Program changes that VSTi’s can follow does exist. It is up to the VSTi designers to make it work or not. Why Steinberg chose to completely dismiss the ability to recognize MIDI Program changing with every one of their synths is beyond me. It is a basic MIDI spec just thrown out the window…and for what? The sake of MediaBay? There’s a great idea…design a behemoth database for Preset storage and retrieval and leave out the ability to change Program selections on the fly….either with MIDI or Automation. What really burns me about this is the inability to change presets from my master MIDI keyboard…regardless of whether I wish to record the changes or not.
I have quite a few 3rd party VST2 and VST3 synths and even some effects plugins that are all capable of responding to MIDI Program changes. Some will only change the patch without any preset list updating while some will change the patch and update the listing in the synth as well as the Inspector’s preset list. If 3rd party programmers can do this, why not Steinberg with all its programming talent?
So, unless Steinberg decides to restore this basic MIDI functionality to its VSTi line, your only recourse is to do what Ernst suggests: multiple tracks of the same plug-in. The Prologue (along with most others) won’t eat CPU cycles for each instance while they’re waiting to play. As an addition to that suggestion, I’d stick 'em in a FolderTrack to cut down mixer clutter.
…my 2 cents