Bonjour,
I'm french,and real newbie with Lemur( and with SuperCollider too...)
I am using the lemur class found here: http://www.jazzmutant.com/workshop_tuto ... ercollider.
I can understand almost every infos in this tutorial and map simple sc synths on basic lemur controllers.
But I really don't know how to "name" a second multiball(ball 1) or the second slider of a multislider in my SuperCollider code.
/MultiBall1/x don't work,/MultiBall/x[1] don't work...
Any help?
I had understood all those things (x[0],x[1],etc...).
My problem is to have access to those specifics variables in SuperCollider.
I can map "x" on an argument with the SC lemur class,but this don't work with x[0].
Hi
Sorry about that I thought you meant the Lemur side . .
Also be aware that SC has changed a bit since those examples where made - OSC is dealt with slightly differently these days I think.
Anyway I see two solutions:
1. Access the values from the MultiBall.x array in SC using 'array.at(n)' as detailed in the MultiSlider example the tutorial.
2. Create Custom OSC addresses for each index in Lemur and capture those singularly in SC
Approach 1 is probably recommended.
Once your Responder has captured the array of MultiBall.x data you can access and use it how you like.
thank you,
I will look at this in the evening.
(And,it's true,the info IS in the tutorial,so the real universal tip is just"opening the eyes"...
once again )
have a nice day!
Bonjour,
I'm back with this,because I'm not able to find the right syntax to achieve solution one(from the Macciza's post above).
I don't know how to put this array "notion" in this SC message:
~lemur.mapXScaled(~synth, "level", "/MultiBall/x", 0, 0.9);
solution two works fine,but if the first is "probably recommended"...
Any help?
Hi
It's been a while since I did any SCing so I'm unsure of the SC side . . .
But it comes down to pulling the values out of the array and the ~lemur.map functions being able to deal with that data.
I'm not sure if they would as they probably expect the address reference - you would need to use your own scaling, I think.
But you can always format your stuff on the Lemur side of things. ie Solution 2.
Try this:
Make 2 new variables in the MultiBall - x1 = x[0] & x2 = x[1] these are the first 2 ball values.
Set these to send to your SC OSC Target - x does not send anywhere now.
In SC your example line now uses "/MultiBall/x1" for the first ball "/MultiBall/x2" for the second etc
Make as many additional variables as needed.
)