I should've looked at the code when you mentioned this. Indeed, this OSC stuff will not work at all unless there is at least one valid entry in X-OSC.txt. So, for those having trouble with this, please try adding an entry to X-OSC.txt. For example: /some/address = d
Post by rickywander on Jul 20, 2019 12:43:19 GMT -5
Very stable and fast!!
I suppose that is possible to send OSC messages to box names on Touch-OSC, launching them from X-OSC clips in Session view. Since my bindings are always divided in group of four, I need to visualize on the external screen some more informations, apart the track's name + first device selected which are sent continuosely.
What I understood is that I need to write a string on OSC.txt for each object I may need and give it a unique name.
Is not so clear to me also the syntax I have to use in order to create X-OSC Clips.
Does anybody have some working strings and procedure to show? I think it will be useful for others too...
Stray, TNX again for the opportunity you give to us. :-)
X-OSCs are a trigger type that lets you trigger actions via OSC. That doesn't sound like what you're looking to do. It sounds like you want to send OSC messages out from ClyphX Pro. To do that, you'd use the OSC Actions covered earlier in this thread. Something like: OSC STR /msg "Hello world!"
Welcome to the forum. Assuming that you're trying to send OSC to an app running on the same system and the app is receiving on port 7000, what you've got in Preferences.txt is correct. The format of the action is wrong though. You have:  OSC STR "/composition/connectnextcolumn"
You need to specify the address to send the string to as well as the string to send. For example:  OSC STR /the/address "The String"