hipox
New Member
Posts: 2
|
Post by hipox on Jul 29, 2019 6:28:43 GMT -5
Hello Stray and members of this great forum!
I downloaded the TouchOSC template, installed everything as in the tutorial and output to iPad really works! I just have a hard time figuring out how did you manage to get Bindings in your scripts work with banks etc. Is it like button "Bank 1" will trigger "xmode 1" etc? Would you mind sharing with me/us a more in depth steps how to exactly replicate your bindings, please?
Thank you very much, Peter
|
|
|
Post by Stray on Jul 29, 2019 8:15:07 GMT -5
Welcome to the forum. I just set up X-Controls to trigger a series of BIND actions to rebind the knobs. For example:
b3 = note, 9, 11, 21, 55, bind k1 sel/dev(sel) b5 p1; bind k2 sel/dev(sel) b5 p2; bind k3 sel/dev(sel) b5 p3; bind k4 sel/dev(sel) b5 p4; bind k5 sel/dev(sel) b5 p5; bind k6 sel/dev(sel) b5 p6; bind k7 sel/dev(sel) b5 p7; bind k8 sel/dev(sel) b5 p8; bind k9 sel/dev(sel) b6 p1; bind k10 sel/dev(sel) b6 p2; bind k11 sel/dev(sel) b6 p3; bind k12 sel/dev(sel) b6 p4; bind k13 sel/dev(sel) b6 p5; bind k14 sel/dev(sel) b6 p6; bind k15 sel/dev(sel) b6 p7; bind k16 sel/dev(sel) b6 p8; osc str /dsp "Bank 3";
I hope that helps.
|
|
|
Post by samverlen on Jul 29, 2019 12:25:57 GMT -5
You don't have the necessary files installed. Please follow the instructions in the first post of this thread. Oh sorry, I thought my copy of user-actions directory did not succeed. It well works now, thanks !!
|
|
|
Post by Stray on Jul 30, 2019 5:37:08 GMT -5
No worries.
|
|
hipox
New Member
Posts: 2
|
Post by hipox on Jul 30, 2019 5:42:50 GMT -5
Welcome to the forum. I just set up X-Controls to trigger a series of BIND actions to rebind the knobs. For example: b3 = note, 9, 11, 21, 55, bind k1 sel/dev(sel) b5 p1; bind k2 sel/dev(sel) b5 p2; bind k3 sel/dev(sel) b5 p3; bind k4 sel/dev(sel) b5 p4; bind k5 sel/dev(sel) b5 p5; bind k6 sel/dev(sel) b5 p6; bind k7 sel/dev(sel) b5 p7; bind k8 sel/dev(sel) b5 p8; bind k9 sel/dev(sel) b6 p1; bind k10 sel/dev(sel) b6 p2; bind k11 sel/dev(sel) b6 p3; bind k12 sel/dev(sel) b6 p4; bind k13 sel/dev(sel) b6 p5; bind k14 sel/dev(sel) b6 p6; bind k15 sel/dev(sel) b6 p7; bind k16 sel/dev(sel) b6 p8; osc str /dsp "Bank 3";
I hope that helps. After some examination I finally get the whole concept I thought the OSC template would be able to also modify values it shows, now I understand there's not this option. Are there any plans on implementing encoders control (in live) over OSC like MIDI does have over Encoders Bindings? Maybe it's not necessary while we can combine OSC output and midi encoders bindings, I'm just curious.
|
|
|
Post by Stray on Jul 31, 2019 9:58:24 GMT -5
There is no plan for that at the moment, but I'll add it to the wish list and take a look at implementing it.
|
|
|
Post by kirkwoodwest on Sept 24, 2019 13:23:06 GMT -5
Loving the new OSC stuff. I'm able to do so much more and create more connectivity between the lemur and ableton. That sounds about right as we constantly refresh the OSC data that is sent out to prevent dropped packets. This seems a little bit odd, i can understand this but it is also resending data from any OSC STR, OSC INT actions. it constantly sends this data. which means my lemur code has to constantly interpret it. in some form or another. I'm not sure what is the proper protocol is for OSC but resending packets this many times seems excessive to me. particularly if the value hasn't changed.
|
|
|
Post by Stray on Sept 29, 2019 3:56:51 GMT -5
It's certainly not a perfect solution. Currently, we have no way of knowing if a packet gets lost, so we just refresh everything always. I suppose I could add an option for the refresh rate, so that users could decide for themselves how often the refresh should occur. I'll look into that for the next update.
|
|
j7468
New Member
Posts: 3
|
Post by j7468 on Oct 3, 2019 15:52:48 GMT -5
Hi everybody,
OSC output is an absolutely amazing feature! I am using it at the moment to send messages to QLab, far beyond what would be possible with midi. ClyphX, already an great product, has become so much more powerful and useful for my use case.
But please, let the user decide what the refresh rate for resending packets should be and, even more importantly, let me turn the resending off completely. I'd like to send messages to other programs that trigger an action, not a continuous controller value. These messages must only be received once or else the action (e.g. triggering a cue in QLab or sending an command to lighting equipment) gets triggered over and over again. I looked at the Python source code and couldn't find an obvious way to change the behaviour. Maybe I am missing something?
Thanks and keep uptake good work, Jens
|
|
|
Post by Stray on Oct 11, 2019 3:44:24 GMT -5
Welcome to the forum and my apologies for the delay. I will add this to the internal wish list and try to get it implemented for the next update.
|
|
|
Post by xasancle on Oct 12, 2019 6:31:44 GMT -5
|
|
|
Post by Stray on Oct 12, 2019 23:44:21 GMT -5
Welcome to the forum xasancle and thank you for the heads up!
|
|
j7468
New Member
Posts: 3
|
Post by j7468 on Oct 17, 2019 12:33:02 GMT -5
It seems like OSC addresses are always sent with lowercase letters. This makes it impossible to send certain messages to some applications.
For example, in QLab's OSC Dictionary there are messages like: /cue/selected/customString or /cue/selected/messageType
When I try to send messages to these addresses with ClyphX, these are converted to /cue/selected/customstring and /cue/selected/messagetype
and are not recognized by QLab any more.
Jens
|
|
|
Post by samverlen on Oct 17, 2019 14:22:44 GMT -5
It's certainly not a perfect solution. Currently, we have no way of knowing if a packet gets lost, so we just refresh everything always. I suppose I could add an option for the refresh rate, so that users could decide for themselves how often the refresh should occur. I'll look into that for the next update. Hi Stray, Thank you very much for this fantastic OSC feature in Clyph X. I would be very interested also by the option to avoid refreshing rate as my usage is only with private managed network between two computers (one with Ableton and the other with resolume). Could you inform us when you plan to deliver this option ?
|
|
j7468
New Member
Posts: 3
|
Post by j7468 on Oct 20, 2019 2:36:18 GMT -5
Replacing address = args[1] with address = args[1] if '"' in address: address = address[1:-1] in "OSCActions.py" and putting the address in quotes if it has uppercase characters that need to be preserved solves the issue for me. Jens It seems like OSC addresses are always sent with lowercase letters. This makes it impossible to send certain messages to some applications. For example, in QLab's OSC Dictionary there are messages like: /cue/selected/customString or /cue/selected/messageType When I try to send messages to these addresses with ClyphX, these are converted to /cue/selected/customstring and /cue/selected/messagetype and are not recognized by QLab any more. Jens
|
|