In my work with TWO, I've come across the issue of sub-sections of the OSC address spaces of large applications, very often being identical, because they correspond to instances of the same type of object, in the model of the OSC server.
While I have implemented a way for dealing with this that I am satisfied with, there's no corresponding mechanism in OSC Query, for Discovery between OSC Servers and Clients, of such hierarchies. I should add that TWO now supports OSC Query through libossia.
I've given a solution some thought, and have written up an argument and proposed solution on my Discourse forum, I hope it is OK with you that I link to it from here to preserve formatting and images:
Hi!
In my work with TWO, I've come across the issue of sub-sections of the OSC address spaces of large applications, very often being identical, because they correspond to instances of the same type of object, in the model of the OSC server.
While I have implemented a way for dealing with this that I am satisfied with, there's no corresponding mechanism in OSC Query, for Discovery between OSC Servers and Clients, of such hierarchies. I should add that TWO now supports OSC Query through libossia.
I've given a solution some thought, and have written up an argument and proposed solution on my Discourse forum, I hope it is OK with you that I link to it from here to preserve formatting and images:
https://forum.controlmedia.art/t/osc-query-hierachy-of-namespaces-take-2/36
The above issue is to me the most important, but I have identified another 2, which I describe separately here: https://forum.controlmedia.art/t/duplicate-message-targets-overloads-and-choosing-between-them/34/2 and here: https://forum.controlmedia.art/t/osc-query-how-to-deal-with-selection-in-a-namespace/37 I guess I should post about them separately as new issues, maybe later so that I don't distract from the main point on the first link! :)
Let me know what you think!