Hunterits309

The Leap Motion system stores many options in configuration files. These include most of the user-settable options in the Leap Motion Control Panel, service control settings, and feature control settings. These options can be set at runtime using the LeapSaveConfigValue() function, when starting the Leap Motion service/daemon as a command line option, or in a JSON-formatted configuration file.

See Getting and Setting Configuration Values for more information about reading and writing configuration settings.

The Leap Motion controller lets you interact directly with digital content on Windows PCs using your bare hands. (Legacy support for Mac OS X is also available.) quick setup: download the Leap Motion software, plug the device into your USB port, and you're ready to go. Download free apps for desktop and virtual reality on the Leap Motion gallery. Mudra Mouse is available for Leap Motion ™ Controller (Leap Motion SDK 2.x / 3.x / 4.x).

Mac users should download our V2 software which is available here.This is the last version that is compatible with OSX devices. Additionally, starting with macOS Catalina, 32-bit apps are not longer compatible with macOS. Your hands are intricate and nuanced. Our software is too. World-leading hand tracking that captures all the subtlety and complexity of natural hand movements. Leap Motion is now part of Ultraleap.

Important These settings affect all running Leap-enabled applications, not just your own. Use caution when changing settings on computers that you don't personally control. Changes could interfere with the operation of the user's other applications.

The tracking settings control the tracking data available to an application.

• images_mode : integer

  Enables or disables tool tracking. Set to a value of 0 to disable images; set to a value of 2 to enable images.

  Since this setting is controlled by the user, you should ask for permission before changing its value.

  Note that applications must still invoke the image policy API at runtime to receive images. Simply enabling images on the service is not sufficient.

• image_processing_auto_flip : boolean

  When enabled, the Leap Motion device can be used with either the long side of the device with the green LED facing toward or away from the user. The service detects the orientation and flips the images from the device before analyzing them. When disabled, the images are never flipped and tracking recognizes hands much better when the green LED side of the device is facing the user (or downward in a HMD mount).

  Since this setting is controlled by the user, you should ask for permission before changing its value.

The service control settings change how the Leap Motion service (Windows) or daemon (OS X and Linux) operate.

• robust_mode_enabled : boolean

  Robust mode improves tracking when excessive ambient IR light is present. However, it also lowers the framerate significantly. If the resulting framerate is too low, turning on robust mode might cause worse tracking performance than not enabling it in the first place.

  Robust mode can be enabled in the control panel and by setting the robust_mode_enabled configuration parameter. When enabled, the system enters robust mode when excessive ambient IR light is detected.

  Set this parameter to true to enable; false to disable.

  Since this setting is controlled by the user, you should ask for permission before changing its value.

• avoid_poor_performance : boolean

  Since this setting is controlled by the user, you should ask for permission before changing its value.

• background_app_mode arg : integer

  Determines whether applications should receive tracking data when not the focused, foreground application.

  Since this setting is controlled by the user, you should ask for permission before changing its value.

• cpu_affinity_mask arg : integer

  Processor affinity controls which CPU cores that a process will run on in a multi-core system. You can control the processor affinity of the Leap Motion service using the cpu_affinity_mask configuration parameter. This parameter takes an integer value that is converted into a bitmask that specifies which CPU cores the threads of the service will run on (i.e. 3, which is 0011 in binary, would specify that the threads will run on cores 1 and 2). A value of 0 means that the default OS-defined behavior is unchanged.

  The mask is passed to the Windows SetProcessorAffinityMask() API. This configuration parameter is not supported on other operating systems.

  Changes to this value only take affect when the service is restarted. Generally, it makes sense to set this value in the config.json file or on the command line to LeapSvc:

• process_niceness arg : integer

  Thread priority controls the priority of threads spawned by the Leap Motion service. Thread priority is controlled by the process_niceness configuration parameter. Specifying 0 means that the OS default priority is assigined; a value of 1-9 assigns a specific priority (1 = lowest, 9 = highest).

  Changes to this value only take affect when the service is restarted. Generally, it makes sense to set this value in the config.json file or on the command line to LeapSvc. This setting is used on Windows only.

• no_cp_startup : boolean

  Detemines whether the Leap Motion Control panel application launches when the computer boots up. Set to true to suppress automatically launching the control panel; false (the default) to allow.

• auto_check_updates : boolean

  Determines whether the Leap Motion service will automatically check for software updates.

  Since this setting is controlled by the user, you should ask for permission before changing its value.

• auto_install_updates : boolean

  Determines whether the Leap Motion service will automatically install software updates. the auto_check_updates setting must be true for the srvice to discover updates in the first place.

• show_tray_messages : boolean

  Allow notification area messages to be displayed by the service/daemon icon. Set true (the default) to allow; false to supress messages.

  This setting should only be used on computers you control.

• metrics_enabled : boolean

  Allows metric collection.

  This setting should only be used on computers you control.

Power Saving Options

Power saving options include the Control Panel Power Saving and Low Resource Mode settings. Power savings for computers running on battery power is on by default, but can be turned off using a configuration parameter.

The power-saving-related configuration parameters are:

• power_saving_adapter : boolean

  Limits the frame rate to save power, even when the computer is plugged into AC power.

• power_saving_battery : boolean

  Limits the frame rate to save power when the computer is running on battery power.

• low_resource_mode_enabled : boolean

  Limits the frame rate to reduce USB bandwidth.

Setting a value of false for one of these options disables it; a value of true enables it.

The effects of these options are not additive. If you enable both power saving and low resource modes, the resulting framerate will be the minimum value set by either option alone.

The power saving configuration parameters are ignored when images are enabled. (Low resource mode is still effective.)

WebSocket Options

The WebSocket options control how programs can connect to the WebSocket server provided by the Leap Motion service.

Important If you change these values, other programs on the client computer that expect the default WebSocket settings will fail to connect.

Note that changes to the port numbers do not take effect until the Leap Motion service or daemon restarts. Thus, it only makes sense to set these values on the command line or in the config.json file rather than using the LeapSaveConfigValue() function:

Configuration prameters can be set on the command line when invoking the Leap Motion service/daemon executable, (LeapSvc on Windows and leapd on OS X and Linux), in a configuration file, and in application code using the LeapC API.

On the Command Line

To set configration parameters on the command line, run LeapSvc in a console window, specifying the desired options:

• Windows::
• Mac and Linux::

Normally LeapSvc or leapd are installed as a service or daemon and run automatically. Before running LeapSvc manually, you must stop the service if it is already running. You can do this using the standard Windows net command (using an admin account):

• Windows::
• Mac::
• Linux::

As an example, the following command runs the service with auto-orientation and images turned on:

• Windows::
• Mac and Linux

Important: Command line configuration settings can be ignored when the Leap Motion Control Panel is already running.

Osculator Leap Motion

In a Configuration file

You can add options to a JSON-formatted configuration file. The options file can be specified on the LeapSvc command line using the --config parameter or you can add your options to the standard config file.

A configuration file must be valid JSON. A configuration file specifying the options discussed in this document looks like:

On the command line, you can specify the config file as follows:

The Leap Motion system also maintains two standard JSON-formatted configuration files. One is used by the service/daemon, the other is used by the Leap Motion Control Panel application. When both the service and the control panel are running, shared settings are kept in sync. Otherwise, the control panel settings take precedence. In other words, if the service/daemon is already running when the control panel launches, settings are updated to match those found in the control panel configuration file. If the control panel is running when the service/daemon starts, the control panel settings still take precedence over any found in the service configuration file – or set on the command line.

Leap Motion As Webcam

Editing these configuration files while the service/daemon or control panel is running does not change the current runtime setting. We recommend quitting the control panel and shutting down the service/daemon before making changes.

The configuration files are named config.json and can be found in the following locations:

Note that some of these folders are located within hidden directories.

The Leap Motion SDK contains two basic libraries that define the API to the Leap Motion tracking data. One library is written in C++, the second is written in C. Wrapper classes for these libraries define language bindings for C# and Objective-C. Language bindings for Java and Python use SWIG, an open source tool. The SWIG-generated bindings translate calls written in the bound programming language to calls into the base C++ Leap Motion library. Each SWIG binding uses two additional libraries. For JavaScript and web application development, Leap Motion provides a WebSocket server and a client-side JavaScript library.

All the library, code, and header files required to develop Leap-enabled applications and plugins are included in the Leap Motion SDK, except the leap.js client JavaScript library. You can download the Leap Motion SDK from the Leap Motion Developer Portal. An SDK package is available for each supported operating system. The JavaScript client library is distributed separately and can be downloaded from the LeapJS GitHub repository.

Plugins for Unity 5 and Unreal Engine 4 are provided separately from the main SDK. The Unreal plugin is included with Unreal Engine 4. The Unity plugin is available at https://developer.leapmotion.com/downloads/unity.

Supported Compilers and IDEs¶

• C++ on Windows: Visual Studio 2008, 2010, 2012, and 2013
• C++ on Mac: Xcode 3.0+, clang 3.0+, and gcc
• Objective-C: Mac OS 10.7+, Xcode 4.2+ and clang 3.0+
• C# for .NET framework versions 3.5+
• Mono version 2.10
• Unity Pro and Personal versions 5.3+
• Java versions 6 and 7
• Python version 2.7.3
• UnrealEngine 4.9+

Leap Motion Os Versions

C#¶

The C# class definitions are provided in the src directory. To build a Leap-enabled C# application, include the wrapper cs files in your appplication. Your application code should reference the Leap namespace. Also include libLeapC.dylib (Mac), LeapC.dll (Windows), or libLeapC.so (Linux) as a runtime library.

C++¶

To develop for the Leap Motion Controller in C++, include the API header files in your program and link with the Leap Motion library, either libLeap.dylib, Leap.dll, or libLeap.so, depending on platform.

On Windows, separate libraries are provided for 32-bit versus 64-bit architectures as well as debug builds versus release builds (for a total of 4 versions for each component).

On Mac OS X, both architectures and release modes are supported in a single library file.

Objective-C¶

Objective-C applications are supported by hand-written wrapper code. To build a Leap-enabled Objective-C application, include the wrapper header and Objective-C++ code file in your application along with the Leap Motion C++ headers. You can then use the classes defined in the wrapper in (otherwise) pure Objective-C applications. Link your application with libLeap.dylib and include the library in your application package.

Unity¶

As of Unity 5, both the Pro and Personal versions support plugins. The Unity plugin uses the C# class definitions in LeapC folder of the core assets. This library loads the native LeapC.dll (Windows) library.

Java¶

Leap.jar contains the Leap Motion Java classes. This code loads libLeapJava.dylib (Mac), LeapJava.dll (Windows), or libLeapJava.so (Linux). These libraries contain the native code that translates the Java calls to the base Leap Motion API in libLeap.dylib, Leap.dll, or libLeap.so (depending on platform). The base Leap Motion dynamic library is loaded by the intermediate library. For Windows 64-bit architectures, the Microsoft Visual C runtime libraries are also required.

Python¶

Leap.py contains the Python module that you reference in your Python application. This module loads LeapPython.so (Mac and Linux) or LeapPython.dll (Windows). These libraries load libLeap.dylib, Leap.dll, or libLeap.so (depending on platform).

JavaScript¶

Leap Motion JavaScript support has two main components. The first component is the WebSocket server provided by the Leap Motion service. This server allows web applications (or any application that can connect to a WebSocket) to access Leap Motion tracking data as JSON-formatted messages. The second component is the JavaScript client library, Leap.js. Leap.js is an open-source JavaScript API that consumes the WebSocket JSON output and presents it in a form that is consistent in philosophy and structure to the native Leap Motion API.

Other Languages¶

Leap Motion Sdk Mac Os

Many community-created language bindings are available, for a partial list, visit: Community Libraries.

Operating System Support¶

Leap Motion Ros

The Leap Motion software currently supports Linux (Ubuntu 12), OS X 10.7+, Windows 7+.