I’m not quite sure what you are expecting here?
generally DAWs/VSTs are not like hardware … they don’t allocate fixed CC to parameters. (this is not viable)
so we use midi learn, and these are usually stored in the daw project (or sometimes vst preset), since the mapping is often different for different projects.
this is not something E1 can do anything about, thats the way DAWs/VSTs work.
as for bi-directional control - this is down to the DAW/VST, some daws support bi-directional control using midi learn, others do not. the E1 will respond to it if the daws supports it.
so indeed for the most part for VSTs you’d have to download the E1 preset, then map it to vsts.
how this works depends on your daw, but in Ableton this also requires you to mark your midi connection in preferences as ‘Remote’ (again common to every midi controller)
… Im pretty sure there are posts on the E1 forum talking about this.
I also disagree this is a a lot of work/preset are of no use…
simply because:
all you have to do is activate midi learn in ableton, then touch control on vst, touch encoder on e1… repeat … even with many parameters, this is pretty quick to do.
the presets save you a lot of work, like laying out parameters, naming them, setting ranging and doing things like naming ‘enums’
really this is the best that can be done…
sure, there could be ‘control surface scripts’ written for every daw, but this was never promised or part of the scope of E1… so would need some with the time/inclination to do.
I think someone is doing something with Bitwig, not sure about Ableton.
its actually quite tricky to do this ‘generically’, this you have to do things like track the ‘active’ track and such like.