Leap Motion SDK 十大題問

Hello,

Last week, we asked you to share your questions about the SDK through our Google Moderator. Thanks to everyone who participated, we had lots of great questions, so here are the top 10 answers voted by our community.

The effective range and field of view of the Leap Motion Controller are expected to improve as the software matures. However, at this time it begins 2 centimeters above the device, and extends to roughly half a meter. The field of view is about 130° side-to-side and 100° front-to-back. You can think of the interaction area as an upside-down clipped pyramid, or frustum. This range is largely determined by the lenses we use, as well as ambient lighting and environmental conditions.

The SDK has a proprietary license. Our SDK agreement allows you to use our tools to develop and distribute Leap Motion-enabled applications. We do have some restrictions around high-value applications, as well as applications that can control commercial and/or industrial or similar equipment. However, we think the license terms should cover 99% of typical applications.

The hardware and software operate at 60 frames per second in our highest-precision mode, and 240 frames per second in our highest-speed mode. When more hands or fingers are visible, the CPU usage and latency will increase; however, it will always remain below the limits of what is perceivable by the human eye.

Once tracking has begun on a hand or object, the Leap can keep up with any humanly possible speed. Even if a person moves at velocities greater than 5 meters per second, this is easily detectable by the Leap.

We’re working on an ARM implementation of our processing pipeline, but at this point we have no ETA for when this will be available.

Our software automatically adapts to the environment in order to improve robustness – so that shelves, faces, and other background objects don’t interfere with tracking. We don’t plan to provide this as a controllable feature in the API, but we are open to suggestions. In the event that the device falls out of calibration, you’ll be able to use our re-calibration tool. In our experience, however, it’s rarely necessary to use this tool.

Resolution does vary and depends on the exact location within the field of view. However, even at the worst location within the field of view, the accuracy is still very high. For this reason, we do not currently report any error through the API.

No. The Leap Motion API includes attributes that describe the physical characteristics of a hand, finger, or tool – such as position, length, and width – as well as functions for calculating the distances in 3D space. It’s up to the application to decide what constitutes a collision.

Using our software’s Robust Mode, the device and tracking will function just fine. However, if the sun is shining directly into the device, small areas with degraded tracking can occur.

Currently, the API reports coordinates relative to the device itself. This means that if the device moves, the coordinate system moves along with it. We’ve also designed our software so that the z-axis – which is always perpendicular to the long dimension of the device – automatically orients its positive axis to point toward the user. As a result, if you put your hand into the field of view from the opposite side, the software will flip the z-axis. You can turn off this auto-orientation option from the Leap Motion Control Panel.

As always, we love to hear your thoughts as we get ready to open the Developer Portal. We’re continuing to put new tools into place that will allow you to build incredible apps for the Leap Motion Controller. We're on the threshold of something amazing. Thanks again for being a part of this journey with us.

Warm regards,
The Leap Motion Team

時間關係，只翻譯了我對問題大約的中文解讀。多多指教!