Thank you, Daniel. The reason why I think this is important is that being able to quickly assign a saved endpoint configuration to a VSTi would allow easy configuration when the playback template can’t solve ambiguity.
For example, I have Orchestral, Appassionata, Chamber, Dimension and Solo Strings in my template. When a playback template including separate endpoint configurations for the above libraries is recalled, it applies the right end.conf to the Solo Strings, but replicates the first end.conf for all the ensemble strings.
So, I can’t have at the same time, for example, Orchestral Strings for full section, and Chamber Strings for divisi. The only solution, in this case, is to manually reprogram all the routing for the end.conf. I also fear that all the playing and playback techniques included in the missing end.conf are missing.
Being able to assign an endpoint configuration to an existing VSTi would allow for immediate configuration of the missing library. Manual routing of some tracks would then be an easy task.
I hope that, since you can save an endpoint configuration from a VSTi, it is also easy to implement reloading it.