Thanks! One feature that we developed, called "instances", is actually quite interesting, we ended up even publishing paper just on that topic [1]. It's a pro

Thanks! One feature that we developed, called "instances", is actually quite interesting, we ended up even publishing paper just on that topic [1]. It's a proposed way to design mappings that handles the idea of signals that "appear and disappear", or might have multiple instances, like in the context of a multitouch display. So instead of mapping a specific signal (eg. position of an active touch), you map a signal "class" which can be "instantiated", and the receiving side can automatically handle this, e.g. a synthesizer can allocate or deallocate voices in response. The protocol handles all events and corner cases such as the two sides having asymmetric resources, or the associated instances along the chain having asymmetric lifetimes, etc. This is one thing that we feel is quite unique to this solution and does something that MIDI, or other protocols that we know of, really cannot do (well). [1] https://www.researchgate.net/profile/Stephen-Sinclair-4/publication/320841558_Generalized_Multi-Instance_Control_Mapping_for_Interactive_Media_Systems/links/5e06006ea6fdcc2837429fac/Generalized-Multi-Instance-Control-Mapping-for-Interactive-Media-Systems.pdf https://www.researchgate.net/profile/Stephen-Sinclair-4/publ...