Hey peeps, just wanted to say, ABSOLUTELY in love with the software...cant put it down, can't stop talking about it.
So i'm getting down and dirty with Leap and have a workflow, where I am working with a fader, that fader switches its function, becomes something else for a while and then goes back to being a fader for the original function. The thing is, every time I put my hand back in the sensing field, the fader automatically goes to the point I am currently on. I would like for this fader to be inert until it hits the threshold that I last left it at. I am currently using data dispatch to switch between functions, if that helps.
Thanks!
Leap: fader - resume fader data upon triggering last input.
hehe welcome to the club ! 
so the algorithmic translation looks someting similar to 'if the leap went out of sensing field, it won't remote the control anymore, until it reached back the value it left last time'
what i would do pers is a mutivar math module that control a pass or stop event flow from the leap to the controller. so first, when the leaps gets out of scope a pulse make multivar affect 0 for exemple to the pass module. then a A-B scan the difference bettween the fader and the current leap value (so prior to the pass that stopped). if the (abs)olute difference is below a defined threshold (ie A<B module), then a pulse goes to multivar that tis time affects back a 1 to the pass module so leaps controls back as it reached back.
so the algorithmic translation looks someting similar to 'if the leap went out of sensing field, it won't remote the control anymore, until it reached back the value it left last time'
what i would do pers is a mutivar math module that control a pass or stop event flow from the leap to the controller. so first, when the leaps gets out of scope a pulse make multivar affect 0 for exemple to the pass module. then a A-B scan the difference bettween the fader and the current leap value (so prior to the pass that stopped). if the (abs)olute difference is below a defined threshold (ie A<B module), then a pulse goes to multivar that tis time affects back a 1 to the pass module so leaps controls back as it reached back.
-
fractalist
- Member
- Posts: 84
- Contact:
another, yet different tip but that could give you ideas for the future :
I had similar issues but different goals so when the hands are back in the field, I use a smooth object, so that that values smoothly glide from the state it was before I entered the field again, and the current state, and the duration of the smoothing process is proportional to the distance between the two. If the last value was .9 and I entered the field at .1 in the X dimension, it will take some time to reach the current value. But if I get closer to the last value before I got out of field, I'll be quickly controling the position in real time (current value will be reache wuickly).
it gives a nice sense of interaction with the field of control.
I had similar issues but different goals so when the hands are back in the field, I use a smooth object, so that that values smoothly glide from the state it was before I entered the field again, and the current state, and the duration of the smoothing process is proportional to the distance between the two. If the last value was .9 and I entered the field at .1 in the X dimension, it will take some time to reach the current value. But if I get closer to the last value before I got out of field, I'll be quickly controling the position in real time (current value will be reache wuickly).
it gives a nice sense of interaction with the field of control.
Who is online
Users browsing this forum: No registered users and 91 guests