I'm not able to monitor incoming osc arguments.
Any help?
incoming osc arguments
Re: incoming osc arguments
sure man.
1. create an expression that will store your last received data. Place underneath the project or directly in a Monitor object.
2. create a script, let's call it "onOscReceive". In the script choose onOSC as execution type and maybe hit the "Custom Address" checkbox ...
3. access the parameters via:
param1 = OSC_ARGS[1];
param2 = OSC_ARGS[0];
Hope that helped.
Alex
1. create an expression that will store your last received data. Place underneath the project or directly in a Monitor object.
2. create a script, let's call it "onOscReceive". In the script choose onOSC as execution type and maybe hit the "Custom Address" checkbox ...
3. access the parameters via:
param1 = OSC_ARGS[1];
param2 = OSC_ARGS[0];
Hope that helped.
Alex
Re: incoming osc arguments
Yeah!
I'm a bit late on this answer...
Great thanks!
I'm a bit late on this answer...
Great thanks!
Re: incoming osc arguments
well ... I haven't had my Lemur back in August.
Hope answering my question doesn't take almost a year
Hope answering my question doesn't take almost a year
Re: incoming osc arguments
Bonsoir,
So I'm able to monitor in Lemur,the values coming from another program (SuperCollider).These values are coming from four pads and in the monitor I receive under this form:
0,0,0,0.
What must I do to get this form:
{0,0,0,0}
?
In advance,thank you.
So I'm able to monitor in Lemur,the values coming from another program (SuperCollider).These values are coming from four pads and in the monitor I receive under this form:
0,0,0,0.
What must I do to get this form:
{0,0,0,0}
?
In advance,thank you.
Re: incoming osc arguments
if you get the hang of this, you'll have a much better time dealing with many things in Lemur:
say, your monitor
Pads.x
and so the Monitor object displays {0, 0, 0, 1}
which maybe means that it has 2x2 rows/cols. then you just change that to:
Pads.x[0]
and you have the state of the first pad. the second would be Pads.x[1], the third Pads.x[2] and so on.
enable numbers on pads to see the IDs of the single pads on your Pads-object. Same applies to other objects in Lemur such as MultiBall and Switches
say, your monitor
Pads.x
and so the Monitor object displays {0, 0, 0, 1}
which maybe means that it has 2x2 rows/cols. then you just change that to:
Pads.x[0]
and you have the state of the first pad. the second would be Pads.x[1], the third Pads.x[2] and so on.
enable numbers on pads to see the IDs of the single pads on your Pads-object. Same applies to other objects in Lemur such as MultiBall and Switches