Page 2 of 2
Re: Pads value
Posted: 25 Apr 2013 13:50
by Softcore
Try this one if you got a chance - still works only for one pad pressed at a time, but that will be an easy thing to change....does it send osc messages in a format you could use though?
Re: Pads value
Posted: 25 Apr 2013 17:35
by nitefish
Bonsoir,
I have tried with the x yesterday. SuperCollider prints the whole array of xs.
The message I need for a link "out of the box" between the lemur's pads and the GUI in SuperCollider is exactly this one:
/Pads/r/c,boolean value(just one,not the whole array)
I need the slashes for r and c.Is there a way to construct such messages with Lemur ?
I'm revisionning things around "getnext","nonnull",etc on the forum to be able to add the boolean with a script.
Re: Pads value
Posted: 25 Apr 2013 19:09
by Softcore
Silly me! Had forgotten about the x.....As I said this will be easy to do...not sure how to construct the slashes though...
BRB...
Re: Pads value
Posted: 25 Apr 2013 19:56
by Softcore
Ok I am really not sure if we can use custom variables inside custom adresses so Im stuck......
This should work as you want by the way but I really really reeeeeaaaally find it ugly and inelegant
Re: Pads value
Posted: 26 Apr 2013 08:56
by nitefish
Bonjour.
Softcore,a great thank for the interest and the replies.
Now I'm sure that the way Lemur sends the message [/address,(all of the 16 values with 0 and 1)] is the best way
.
It just will be more simple to manage multipads or multiswitches.
It's more logical (more elegant) to have the same array on the SuperCollider's GUI side.
So,back to the SC Help...