General
Please Help "Multiball controls Faders"
Started by Balog on .
Sign in or create an account to join the conversation.
Hi,
how is it possible to control Lemur faders via the multiball object.
Thanks Balog
Lemurized FL GRANULIZER
how is it possible to control Lemur faders via the multiball object.
Thanks Balog
Lemurized FL GRANULIZER
Hi, no one has a tip?
I want to control lemurs fader with a multiball.
How is this possible.
Thanks balog
I want to control lemurs fader with a multiball.
How is this possible.
Thanks balog
Thank you !
bxsj wrote:See attachment. Not sure if this is what you are looking for.
Hope that helps,
B.
Hey ~ I'm looking at this and I can't figure out how you tied one to read the other :\
I've set up the same rig, the monitors are reading fine, but the ball does not affect the fader - what am I missing??
I guess you didn't include the script that tells one object to influence the other. Compare it to the working template in the Lemur editor.Z3B wrote:what am I missing??
The fader x value is updated in the "onchange" script in the multiball object. This script is triggered whenever the x value of the multiball object is changed (on expression x).
BxSj
Edit: Hey Phill you've beat me by one second
BxSj
Edit: Hey Phill you've beat me by one second
maybe but your response was more precise. 
Nice, thanks for the answers (so fast) - this was my first crack into the scripting for Lemur... I didn't realize I was looking for the 'onchange()' in the project menu... I was just clicking objects and finding no script
Us noobs need to be tolerated, hahaha
Us noobs need to be tolerated, hahaha
So here's another question that comes to mind...
I have Kapture making changes to ableton device values... and I want these changes to be updated/reflected on my Lemur device as they happen. It seems like this would be the same principle, only having a midi value triggering an attribute in Lemur. You tell me...
I have Kapture making changes to ableton device values... and I want these changes to be updated/reflected on my Lemur device as they happen. It seems like this would be the same principle, only having a midi value triggering an attribute in Lemur. You tell me...