As above, vsts these days have a ton of parameters, so I’d never try to map them all manually.
Also it’s not just the preset generation , unless you use automation you also have to assign a ton of cc… and that means potentially midi learning every param in your daw.
Really unless you use the vst everyday it’s sounds like too much effort.
I think the better solution is a programmatic one
Basically take the same approach as push2
You wrute control scripts for your daw, that interrogate the plugin via automation… and then dynamically create that in the e1
But that’s quite a lot of work, and is also dependent on the daw.
there’s another approach which I’ve done in the past which is host vsts within a wrapper vst … that is more daw independent but has a few limitations.
Another simple / halfway house. approach would be to write a vst host,
That simple interrogates the vst, and the produces an e1 preset file , with cc mapping.
Then you could load that up to move things around , and then midi learn to params in your daw.
——
But for now , I went entirely the other/simpler way.
I think of the E1 as a performance interface , so presets are created just for what I’m using , where I need.
So I’ll combine things like level controls all on one page, even though they are for different hardware and software synths ,