Hy,
I have a question about the multiball object.
Im working on an experimental project, and would like to control a few parameters in Live with multiballs.
Is it possible to set up the multiball object that still send values after releasing my finger from the screen?
Normally it stops...if I uncheck XYZ will move, and Im able to "poke" the balls, but no value sent...
Multiball question
Re: Multiball question
Im not sure but I think I know what you have stumbled on....
Lets say the physics of the ball are activated. This means the ball will continue moving even after you stop touching it, and of course it will continue sending midi messages.
BUT...even when physics are enabled for an object, any midi feedback message received back from the controlled software (this case, Live) has priority over the "physics" of the object. In other words, when feedback is received from Live back into Lemur's multiball, it will cause the multiball to "stop" at the value of the feedback and disregard ANY physics settings.
To counteract this, you just need to disable the feedback for that object. Unticking the xyz disables Lemur "sending" the values, not the actual feedback though.
So your solution is to create "custom midi messages" - these by default do not support midi feedback therefore it will work.
Here is an example to showcase the feature - map the following multiball to anything you want in Live - you will see that the multiball "listens" to its physics settings no matter what happens inside Live.
Notice how the custom midi messages are set: they are all set to "follow" the xyz parameters (by attaching x,y,z on the value field of Xn, Yn, Zn custom midi messages) - for the example I have used miditarget0, CC 21- 23, midi channel 1
Lets say the physics of the ball are activated. This means the ball will continue moving even after you stop touching it, and of course it will continue sending midi messages.
BUT...even when physics are enabled for an object, any midi feedback message received back from the controlled software (this case, Live) has priority over the "physics" of the object. In other words, when feedback is received from Live back into Lemur's multiball, it will cause the multiball to "stop" at the value of the feedback and disregard ANY physics settings.
To counteract this, you just need to disable the feedback for that object. Unticking the xyz disables Lemur "sending" the values, not the actual feedback though.
So your solution is to create "custom midi messages" - these by default do not support midi feedback therefore it will work.
Here is an example to showcase the feature - map the following multiball to anything you want in Live - you will see that the multiball "listens" to its physics settings no matter what happens inside Live.
Notice how the custom midi messages are set: they are all set to "follow" the xyz parameters (by attaching x,y,z on the value field of Xn, Yn, Zn custom midi messages) - for the example I have used miditarget0, CC 21- 23, midi channel 1
- Attachments
-
- MultiballCustomMidi.jzml
- (4.61 KiB) Downloaded 80 times
Last edited by Softcore on 01 Dec 2013 12:23, edited 1 time in total.
Re: Multiball question
A-ha!!!
Now I see
Thats what I was looking for, thank you very much!!!
Now I see
Thats what I was looking for, thank you very much!!!