Open claudiocabral opened 8 years ago
Good point. To implement it, create a dedicated branch so can to do some reviewing together before it is merged to master. Also we have to decide on a kind of naming scheme for the messages which do not relate to etude or element inputs. We could think e.g. about having reserved namespaces like /control for host-level control messages, like switching between etudes or setting other global parameters, and /
I think we should be able to create and destroy elements with OSC messages. This should be fairly easy to implement in the current state of the project, I'll look into it this week.