Jonathon Mooney

I recently found this patch posted by Jules Francoise at 

 that seems to be a lot more useful than the aka.leapmotion patch but I'm having trouble extracting data from the jit.cellblock, specifically the palm location data. I can easily extract the finger locations but I can't seem to get any data whatsoever from this cellblock. I've tried so many different methods found in tutorials, and it's just blank.

Has anyone else used this leap motion patch?

Any help would be amazing. Also, forgive me I'm very new to max

I recently found this patch posted by Jules Francoise at http://julesfrancoise.com/leapmotion/ that seems to be a lot more useful than the aka.leapmotion patch but I'm having trouble extracting data from the jit.cellblock, specifically the palm location data. I can easily extract the finger locations but I can't seem to get any data whatsoever from this cellblock. I've tried so many different methods found in tutorials, and it's just blank. 

Any help would be amazing. Also, forgive me I'm very new to max


leap-motion-extracting-data-leapmotion-max

I was simply looking for the rotation of the right palm. - If you dig into the subpatchers (p hands / p gestures / p fingers ) you will see what each particular outlet is streaming, and can bust up the whole big list using unpack.

Also, for those people using aka.leapmotion, it seems to work very well, (on Mac at least) BUT - the SDK that aka.leapmotion was built with was a early version compared to what is being used now. In my experience the ONLY problem was a nagging error message that kept coming up. ("software is asking for features not available in this version of Leap" ) but your mileage may vary. I went with it at first simply cause i had the same problem with the Jules patch you were having - how do i get at the info?

After talking with the guys at Leap I found the one patch you have and life is good, it works flawlessly.

Hey Jonathon!
This is how I managed it.
I was simply looking for the rotation of the right palm. -  If you dig into the subpatchers (p hands / p gestures / p fingers ) you will see what each particular outlet is streaming, and can bust up the whole big list using unpack.

Also, for those people using aka.leapmotion,  it seems to work very well,  (on Mac at least)  BUT - the SDK that aka.leapmotion was built with was a early version compared to what is being used now. In my experience the ONLY problem was a nagging error message that kept coming up. ("software is asking for features not available in this version of Leap" ) but your mileage may vary. I went with it at first simply cause i had the same problem with the Jules patch you were having - how do i get at the info?

Hi John, thank you so much for the reply! That patch is very helpful, although I was primarily having trouble getting the palm position which only seems to be in the cellblock, and for some reason I can't get any data out of that cellblock. Have you successfully gotten data from that chart?

Hi John, thank you so much for the reply! That patch is very helpful, although I was primarily having trouble getting the palm position which only seems to be in the cellblock, and for some reason I can't get any data out of that cellblock. Have you successfully gotten data from that chart?
Cheers
Jonathon


Right-click on the leapmotion patch > Open Leapmotion Help

Unlock the patch, and paste the bit below in and follow the instructions. This works for me to get the palm position.

Attaching a metro as described in the patch may NOT be the most efficient way to get a flow of this data, just is the only way I know.

Much Wiser Maxxer's (MWMs) here will probably have a MUCH better way to approach this...I somehow feel that this somehow could cause more latency than necessary when dealing w lots-o-data.

Hey Jonathan,
try this.
Right-click on the leapmotion patch > Open Leapmotion Help
Unlock the patch, and paste the bit below in and follow the instructions.   This works for me to get the palm position.

Attaching a metro as described in the patch may NOT be the most efficient way to get a flow of this data, just is the only way I know.
Much Wiser Maxxer's (MWMs) here will probably have a MUCH better way to approach this...I somehow feel that this somehow could cause more latency than necessary when dealing w lots-o-data.

It works! You are a god among men. Thanks John!

I attached a metro to the input with the smallest interval and it seems to respond well.

solution without fetching data from coll object - directly from leapmotion !

Hi, 
solution without fetching data from coll object - directly from leapmotion !
 

in case somebody need something similar

cheers

Leap Motion Extracting Data (Leapmotion.max)