The input and feedback port can be changed in the MadMapper preferences. One is just for sending data from the client to MadMapper and the other one is for the opposite direction.įor example if processing should talk with MadMapper you have to create a new OSC client which maps to the input port of MadMapper and a new OSC server which listenes on the feedback port of MadMapper.
To combine multiple messages together it is also possible to create so called bundles.
#Syphoner processing madmapper update#
As an addition it is also possible to send data within the message, for example, to update a parameter. This address will be recognized by a client and will cause it to do something. Over OSC you can send messages which contain a specific address.
#Syphoner processing madmapper software#
The drawback of this is that if you want to create a bidirectional channel between your software and and antoher, you have to open a server and a client on both sides. The benefit of this is that it is really fast and simple. UDP gives you the ability to just send data and don't care about, if the client is listening or how many client's are listening to your message. OSC is a simple UDP based network protocol between a server and multiple clients. So it is useful to understand OSC and it's possibilities. The MadMapper OSC API uses OSC to send and receive messages. To simply start communicating with MadMapper you have to Surfaces) from MadMapper and their values.
QuickstartĪt the moment the API does just provide to read controls (e.g. The goal of this repository is to gather examples and documentations for the api to give other developers a quick start and and overview over the possibilities. This is just a documentation and example respsitory for the MadMapper OSC API which was released with the version 2.2 in December 2015.
0 kommentar(er)
