#Leap motion blender windows#

The rate these failures occur, combined with stereo triangulation requiring double the reliability, prevents Kros’s MediaPipe implementation from being usable. the back of a right hand can get mislabeled as the palm of a left hand). Correctly locating the joints of a hand, but identifying the hand as the wrong hand facing the wrong way (e.g.Unfortunately, this means that if there is a tracking failure in either camera, the product of the stereo calculation is ruined. This is how Kros currently uses MediaPipe. However, by calculating the hand tracking image points for each eye of the stereo camera, it is possible to triangulate the absolute positions in space if the camera’s optical properties are known.

In fact, without knowing the size of the hand, it is impossible. So, by itself, MediaPipe can’t give an absolute position in space. The X and Y values together make a point on the image on a scale from 0 to 1, but the Z value is the depth relative to the wrist of that hand with a poorly documented relative scale. The MediaPipe hand tracking solution takes a single image and outputs a nominally 3D point per joint including fingertips.

Can an open source solution like MediaPipe be made to work in the future?.

#Leap motion blender windows#

How am I going to continue using Leap Motion without tethering to a Windows machine?.Why doesn’t MediaPipe work as well as Leap Motion?.

This blog post will answer the following questions: So, having experienced MediaPipe’s hand tracking as a method of input, I have decided to continue using Leap Motion for the current proof of concept.