Ethan Wise

Im a fairly amatuer MaxMSP user, i am currently working on a project connecting a leap motion controller to parameters of a VST in this case Native instruments Massive.

I am able to connect the specific control from leap to massive, however the problem i am having is that the control in massive seems to only go on or off it doesnt allow smooth movement of the control it is either on or off.

I believe it to be down to the scale used to scale the number coming in from the leap motion to the number for massive which works with midi, so i believe it should be 0. 127. but everything i have tried doesn't seem to work.

Im a fairly amatuer MaxMSP user, i am currently working on a project connecting a leap motion controller to parameters of a VST in this case Native instruments Massive. 

vst-object-trouble-with-native-instruments-massive

Did you try to send values between 0. and 1. to your 

Did you try to send values between 0. and 1. to your vst~?


No the values being sent are the lowest value that my leap controller sends for the gesture/movement used to control and the highest so it is 20. and 260. scaled to 0. and 127. but i still get just on or off from the control on the VST

What I mean is that you should try to map your datas to the 0.-1. range rather than 0-127.

leapdatas -> [scale 20. 260. 0. 1.] -> FILTER1-CUT $1 -> [vst~ Massive.vst]

What I mean is that you should try to map your datas to the 0.-1. range rather than 0-127.
Something like:
leapdatas -> [scale 20. 260. 0. 1.] -> FILTER1-CUT $1 -> [vst~ Massive.vst]


Ah i see, sorry for the misunderstanding. I will give this a go thank you very much!

VST object trouble with native instruments massive