|
Post by Stray on Jul 15, 2019 7:30:37 GMT -5
That sounds about right as we constantly refresh the OSC data that is sent out to prevent dropped packets.
|
|
|
Post by rickywander on Jul 16, 2019 13:16:47 GMT -5
Hi all. a simple but basic question . Do I need to activate "Touch OSC Bridge" in "Touch OSC" in order to transmit osc bindings?
|
|
|
Post by Stray on Jul 17, 2019 4:11:37 GMT -5
No, the bridge is only needed if you want to use TouchOSC to send/receive MIDI data.
|
|
|
Post by rickywander on Jul 17, 2019 8:21:57 GMT -5
I was quite shure. Anyway It's not working.... I have a project on Ableton with working bindings and and a BCR2000 nicely responding. I am using touch OSC with the preset You kindly provided and already set all files in USER_ACTION folder . Also if I use Touch OSC Bridge then Touch OSC can comunicate with Ableton via Midi so the network is ok, I suppose. I created a log which I hope can help. I send some file in order to let You check what's goin on Attachments:Debug Log.txt (6.6 KB)
Preferences.txt (3.76 KB)
|
|
|
Post by stoersignal on Jul 17, 2019 12:43:36 GMT -5
same problem here. hopefully stray finds the problem @stray: if you need any further information, or if i could help anyhow, please let me know!
|
|
|
Post by Stray on Jul 18, 2019 6:06:24 GMT -5
rickywander,everything looks good in terms of your settings, so I'm not sure what the problem could be. stoersignal, I appreciate the offer, but I'm honestly not sure what information could help here. I'm in the midst of a large project at the moment and so I don't have time to look deeper into this, but it's on my prioritized to do list. Sorry for not having an immediate solution for you guys.
|
|
|
Post by kirkwoodwest on Jul 18, 2019 18:26:31 GMT -5
That sounds about right as we constantly refresh the OSC data that is sent out to prevent dropped packets. Cool. Well what I know for a fact is the Output started working when I added a working line to the X-OSC file. Maybe that helps others...
|
|
|
Post by Stray on Jul 19, 2019 5:32:25 GMT -5
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
Let me know if that helps.
|
|
|
Post by rickywander on Jul 19, 2019 7:50:00 GMT -5
It works. Bindings and osc viewer perfectly synchronized on my two euros mobile on Android. Now I can go more indeep of this futuristic future. Tnx kirkwoodwest 4 the BIG input :-)
|
|
|
Post by rickywander on Jul 19, 2019 8:37:56 GMT -5
That sounds about right as we constantly refresh the OSC data that is sent out to prevent dropped packets. Cool. Well what I know for a fact is the Output started working when I added a working line to the X-OSC file. Maybe that helps others... It actually did! Tnx
|
|
|
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. :-)
|
|
|
Post by Stray on Jul 22, 2019 7:24:57 GMT -5
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!"
|
|
|
Post by Urbi Et Orbi on Jul 22, 2019 17:33:43 GMT -5
...please try adding an entry to X-OSC.txt. For example: /some/address = d Let me know if that helps. Oh yeah! Works like a charm!
|
|
|
Post by samverlen on Jul 26, 2019 11:51:37 GMT -5
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" Unfortunatly, it does not work better. Here is the debug file Debug Log.txt (13.3 KB)
|
|
|
Post by Stray on Jul 27, 2019 4:43:18 GMT -5
You don't have the necessary files installed. Please follow the instructions in the first post of this thread.
|
|