I’m endeavoring to write a comprehensive expression map for a library with a lot of articulations and a complex control scheme. And when I’m done I’d like to share it via ‘export/import library’ on the emap dialog.
I’m struggling with how best to encode the many articulations and patches that have no analogue in the existing playback technique set, as it appears that additions you make to that set do not get exported/imported with the expression map. This kind of makes sense as the playback technique set is global and there is no enforced namespacing on additions.
Nevertheless, this is a real need. Am I missing a trick or something? I’ve seen on the videos the co-opting of existing unrelated techniques but while that is something one might do for oneself (and now seems unnecessary since you can add to your own playback technique set), it seems fragile and confusing to do in a published expression map. All the more so since the user still must then create playing techniques (also not exported/imported) mapped to those playback techniques. I’m imaging a README that documents:
Smear == Legato slow
Whale Call == Repetition Staccato
etc. I’m estimating this library might require up to two dozen of these co-optings.
Is there another way?