|
Post by Stray on Jun 20, 2019 13:15:22 GMT -5
Right, what you're doing looks fine. I haven't had a chance to try to reproduce this, but it's on my to do list.
|
|
|
Post by Stray on Jun 22, 2019 7:09:23 GMT -5
could you tell me what i`m doing wrong? no osc is coming out of live. tested with OSC data monitopr and resolume. as output OSC adress i tried it with 127.0.0.1, localhost and 192.168.1.100... nothing worked..... i`ve got the feeling that i`m missing something essentially btw. i tried it with the official 10.1 release and the new beta. no difference Okay, I've just tried this using the M4L device named OSC Monitor included with Live Suite and it's working as expected when OSC_DEVICE_IP_ADDRESS is set to 127.0.0.1 and OUTGOING_OSC_PORT is set to 8000 (the default for the OSC Monitor device). Does that work for you?
|
|
|
Post by stoersignal on Jun 22, 2019 13:28:33 GMT -5
|
|
|
Post by Stray on Jun 22, 2019 18:42:59 GMT -5
Please follow the debug procedure covered in the Troubleshooting section of the manual as that may help shed some light on what's going on here.
|
|
|
Post by stoersignal on Jun 25, 2019 2:40:37 GMT -5
Please follow the debug procedure covered in the Troubleshooting section of the manual as that may help shed some light on what's going on here. hope that helps Attachments:Debug Log.txt (18.5 KB)
|
|
|
Post by Stray on Jun 28, 2019 8:57:12 GMT -5
Apologies for the delay. Everything looks good in the log. Are you able to use X-OSCs to trigger action lists? In either case, have you tried this in a stable version of Live?
|
|
|
Post by stoersignal on Jun 28, 2019 10:34:42 GMT -5
Apologies for the delay. Everything looks good in the log. Are you able to use X-OSCs to trigger action lists? In either case, have you tried this in a stable version of Live? X-OSC = yes stable version = yes
|
|
|
Post by Stray on Jun 30, 2019 6:38:05 GMT -5
Okay, that is quite odd and I can't think of what could possibly cause that. I'll give it some more thought and post back here if I have any other suggestions.
|
|
|
Post by moha2009 on Jul 2, 2019 23:16:28 GMT -5
Hi Stray, i dont really know what i did to get it working. For me seems the same as before but now its working.
The other questions regarding clyphx pro are 1) can i hot swap a sample in a nested simpler? (for example in a drum rack pad) 2) can i control parameters of a device in a chain return track? (drum rack also)
Im relatively comfortable with user actions if you have something in mind. Thank you so much!
|
|
|
Post by Stray on Jul 3, 2019 17:31:16 GMT -5
Those could both be done with user actions. If you have further questions about that, please create a new thread on the topic, so we don't create confusion in here.
|
|
|
Post by samverlen on Jul 6, 2019 16:27:31 GMT -5
Hi, I tried to send action OSC OUT message from Ableton to Resolume software (on the same mac or another) but I don't know what to put in the x parameter With /msg or the IP adress ([] OSC STR /msg "TheResolumeCmd"), it does not work. Do you have any other suggestion ? Thanks for your help ! Debug Log.txt (7.61 KB)
|
|
|
Post by Stray on Jul 7, 2019 9:25:13 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"
|
|
|
Post by kirkwoodwest on Jul 14, 2019 15:14:16 GMT -5
Finally getting around to implementing this part of my rig... I've made a couple attempts to get this to work. starting with my lemur and then eventually using the OSC_monitor to monitor all the OSC Data. Using the node.js tool oscurl I was able to send data just fine... but not with using Clyphx. I'm really curious what happened to those who just found it working all of the sudden... Debug Log.txt (6.09 KB) Just to add... I reinstalled clyphx pro, bindings then copied the user actions. Still no go... any help would be super appreciate. Its totally strange that it just works for one user and not the others. :
|
|
|
Post by kirkwoodwest on Jul 14, 2019 15:52:03 GMT -5
Not sure if it would help but you could remote into my machine and do some tests. I'm running OSX Mojave 10.14.5.
This seems so strange. almost like a possible port blocking thing or something from the App itself. But then when I use the OSC Send in the connection kit with the same things 127.0.0.1 port 8000 it works fine.
|
|
|
Post by kirkwoodwest on Jul 14, 2019 16:20:58 GMT -5
Ok.. sorry for the excessive posts but I did some thinking about why our systems would be different. So I tried some other stuff including putting a line in the OSC-X.txt file which seems to have enabled the OSC Beta feature.
I just added this to my osc-x thing and now the messages seems to work fine.
/1/button3 = arm
Now what is also happening... is it spams A12 and B12 of my bindings with 0. I have nothing bound to these. if I modify the bindings it just selects another binding to spam. If I take out the bindings all together it just spams the currently selected track and device. (I should clarify its not full spam its just like every 1/4 second or so).
|
|