Now, to recap (And again: please fill in any gaps or mis-assumptions I would love to see this made into documentation): Once that's saved and uploaded to the TouchOSC device, that slider will always change the transparency of the selected layer. So, a good example for the slider I've been talking about would be: /md8key/ctrl_layer_alpha/0 Where "md8key" refers to the application Modul8, "" is a placeholder for the keyword you want to affect (Example: "ctrl_layer_alpha" (self-explanitory)), and "" refers to the layer number: 0 means the selected layer, 1-10 for each layer and -1 for all the layers.
*NOW: Here's the fundamental difference: Remember the "Labels" from before? Now those are no longer generic: you need to edit the TouchOSC templates or create your own, and when you do that each control is basically locked into a function: /1/fader6 can now become /md8key//
Configure TouchOSC to the correct port as listed in the module This is newer, less tested, and different in fundamental ways, but it has more potential. In Modul8, you go into the MIDI Mappings, choose a control, and touch the TouchOSC control in order to have it send the data as follows: TouchOSC > network > Computer > OSC In to OSCulator > MIDI Out from OSCulator > Modul8: Modul8 is now controlled. You then choose MIDI CC (MIDI Control Change) as the event type, and a channel/device so that Modul8 can see the MIDI message When you touch a control on TouchOSC: OSCulator picks up it's label and catalogs it TouchOSC points at the computer OSCulator is running on, on port 8000 OSCulater is loaded on the computer it is set to receive messages by default on port 8000, and it loads blank *Note: these labels can be anything, but I'll get back to that A template is loaded into TouchOSC (Let's say Mix 2 iPad) each control is assigned a "Label" already, and sends messages with that label (for example: /1/fader6 as the fader art the bottom of page 1) The process for this, as I understand it, is as follows (Using TouchOSC): In terms of the flow of information, I know that there are 2 (or more?) ways to get OSC from a device to Modul8:ġ) Using OSCulator to receive OSC messages and translate them to MIDI, then to use MIDI Mapping in Modul8 (And there may be some way to get feedback back through the channel?) Since this thread has very nice clear information (And came up while I was searching, as did this one which I will reference: ), I think it would be well served to outline the processes a little (if the contributors are willing - I'm just learning myself, so have a lot of gaps just want to set the stage so to speak): A solution to this problem will be addressed in the next release. This will require that at least know the host name of your iPad.īut this solution is not very convenient because if you want to use another device, then you will have to change the host name or address in every routing.
Now, if you need to make some sort of correspondence or mapping between modul8's addresses and you the control in your layout, you will need to manually enter OSC Routes in the Parameters Window. This will have the effect of routing the same OSC message to your iPad, even if your iPad changes it's network configuration (IP address for example). For every OSC message that modul8 sends to OSCulator, that you want to forward to the iPad, select "OSC Routing" as Event Type, and "Default: Your iPad name here" as Value.Having you iPad connected and displaying the layout, make sure that it is set as the Default Host (in Parameters Window, OSC Routes tab).Set modul8 to send OSC to the localhost on OSCulator's port (8000 by default).In other words, it will be easy to configure if there is no address rewriting involved (more on that later). There is an easy way to do this if the layout on your iPad uses the same OSC addresses as modul8's.
0 kommentar(er)
