[ANSWERED] URGENT: Leap Motion not detected :(

mark

I am sorry that you are facing issues with the Leap Motion Watcher.

For a long time, the only SDK that worked for macOS was v2.3.1, which you should be able to download from Ultraleap's website. Unfortunately, when I click the link, I get an error and the SDK is not downloaded.

It is only recently that they introduced a new SDK (v5?) that works for macOS. But to make use of this, I must change the Leap Motion Watcher plugin to work with this new SDK and recompile it, because the new SDK is totally incompatible with the old one. Unfortunately doing so has not been at the top of the priority list because this plugin is for a specific piece of hardware that is not frequently used by most Isadora users.

So, for now, to work with the Leap Motion Watcher you must install the v2.3.1 SDK, which is compiled for Intel computers only. If your need is urgent, you may want to see if you can borrow or rent an Intel-based Apple computer.

I may have a copy of the v2.3.1 SDK on a backup, but I will not be able to access those backups until Friday Dec 15th, 2023. If I can find that SDK, you should be able to follow these steps to run the existing Leap Motion Watcher.

Install the LeapMotion v2.3.1 SDK
If you are running on an M1 computer, ensure Isadora is set to run in Rosetta (intel compatibility) mode.
Connect your Leap Motion hardware
Open Isadora
Use the Leap Motion Watcher plugin.

I will let you know if I can find the v2.3.1 SDK for macOS, and I will also test this setup on my M1 to prove that it works.

Thanks for your patience.

Sincerely,
Mark

Armando

@anajcperfeito

Did you try the GECO solution ?

anajcperfeito

Hey @juriaan

Thanks for your help.

I downloaded the “Leap Motion Orion Beta v3.2.1 SDK” as suggested in that article, but I couldn’t find the installer for Mac in there, only for Windows... I have a Mac Intel.

Thanks you.

anajcperfeito

@armando

I was having a look at GEGO, looks great! Have you try to send the signals to Isadora already? If yes, please let mw know how… Thanks a lot :)

anajcperfeito

Hi @mark

Thanks for the reply.

I have an intel Mac.

I haven't been able to download the 2.3.1 version either. So if you find it, please send it to me, I want to try it.

Meanwhile, we will wait patiently for an updated Leap Motion Watcher on Isadora, that would be fabulous!

All the best,

Ana

Armando

@anajcperfeito GECO sends out midi or OSC. For the Midi, Geco sends Control change messages (CC) so in Isadora you choose Communication/midi setup and, in the midi input 1 you choose Isadora virtual in. Lauinch Geco software and set in the preferences of midi signals to Isadora virtual in. Then back in Osadora you go into the midi group and chose the control watcher. Interact with the leapmotion and you should see data moving in the control watcher.

mark

@anajcperfeito

The good news: I found a copy of the Leap Motion v2.3.1 SDK for Mac in a backup (Leap_Motion_SDK_Mac_2.3.1.tgz). I have sent you a private message here with instructions on how to get it. This should allow you to use Leap Motion.

The other good news: I ran the installer inside Leap_Motion_SDK_Mac_2.3.1 on an ARM/M1 macMini running the macOS Sonoma (v14.0) and macOS Big Sur (v11.0). When running Isadora in Rosetta mode as instructed below, the Leap Motion plugin works just fine.

The bad news: Leap Motion didn't always work on an M1. I installed it on my MacBook Pro running macOS Monterey or Ventura, and I could not get it to work. I am not sure why this is; maybe the hardware itself has additional security?

Please be aware that if you have already installed Ultraleap's latest version of the Leap Motion driver ("Gemini") you may not be able to get the old driver working. If you have already installed the latest version from Ultraleap, I suggest you compress "Ultraleap Hand Tracking.app" into a .zip file, delete this application, run the Leap_Motion_SDK_Mac_2.3.1.tgz installer again and reboot. Maybe that will solve the problem. For sure, if you do not do this, the latest driver will "win" and the old driver won't see the ultraleap.

Instructions:

If Isadora is running, quit it.
If you haven't already, download and install the Leap Motion Watcher plugin
Decompress the file Leap_Motion_SDK_Mac_2.3.1.tgz (If you need to get this from us, please open a support ticket; because this is UltraLeap's software, we can't upload it to our site.)
Run the installer Leap_Motion_Installer_release_public_mac_x64_2.3.1+31549_ah1886.dmg
Attach Leap Motion controller
Reboot your computer (just to be on the safe side)
Go to Applications and open "Leap Motion.app"
In the Window that appears, choose Troubleshooting and then click "Diagnostic Visualizer"
If you put your hands ovder the Leap Motion, you should be able to see a 3D rendering of your hands as it track them. If this is working, should work with Isadora
Quite Leap Motion.app
If you are running on an M1 computer, ensure Isadora is set to run in Rosetta compatibility mode. (Click here to learn how.)
Open Isadora
Add Leap Motion Watcher
If everything is OK, the 'available' output will say 'on' and moving your hands above the Leap Motion controller will generate values.

Best Wishes,
Mark

mark

Dear All,

So because of this thread, I looked into the latest Leap Motion SDK and, after several hours of work, I am happy to say that I got it working natively on the M1. The bad news with the new SDK is that they removed all the gesture recognition functions from the SDK; the updated version of the plugin will not be able to recognize circles, swipes, and taps. The hand tracking part works fine though.

But now the issue is that, apparently, Ultraleap wants me to pay a fee to release a commercial product that uses their SDK. I am waiting for them to give me more information, but if the fee is too high, I'm afraid I won't be able release an update. Fingers crossed the amount they are asking is something reasonable.

Best Wishes,
Mark

Armando

Thanks @mark for (again) putting some work on an old (but supercool) device. And, although I have one, I think it is unfair to ask you for money because you make them sell more devices. They should be paying Troikatronix, not the other way around in my opinion....

nexxa

Hi @mark, any updates on this issue? We at the Polytechnic are also encountering the same problem. It would be helpful to solve it because in previous years we purchased about 10 Leap Motion 1 devices for educational purposes and to use with Isadora. Please let me know. Personally, I can use it on my Mac with the old Leap Motion SDK, but with students, having very different computers, it becomes difficult. Before your plugin/actor Leap Motion I used OSC applications directly, like OSC Motion, but I can't find the application anymore and I don't know if there are others. If anyone of you have any suggestions, they are very welcome given the situation. Thank you very much.

tomthebom

@armando said:

<p>@anajcperfeito GECO sends out midi or OSC. For the Midi, Geco sends Control change messages (CC) so in Isadora you choose Communication/midi setup and, in the midi input 1 you choose Isadora virtual in. Lauinch Geco software and set in the preferences of midi signals to Isadora virtual in. Then back in Osadora you go into the midi group and chose the control watcher. Interact with the leapmotion and you should see data moving in the control watcher.</p>

I just tried my Leap Motion 1. gen with the Geminidriver and GECO trough MIDI with Unify and it worked right away for me.
As Armando pointed out this should be a possible workaround... Just needs a nice user actor that syncs with a config file for GECO.

mark

@tomthebom @Armando @nexxa

Hello all. As I said above, I have used the recently released SDK to get the Leap Motion watcher to work properly on M1/M2/M3 machines. I cannot deliver the plugin to you before March 27th. So, if you need this plugin, please open a ticket, say you need the new Leap Motion plugin, and our team will notify you when they can give you a copy.

Best Wishes,
Mark

nexxa

@mark ok. I'll open a ticket to get the new Leap Motion plugin. Thanks! and thanks to @tomthebom @Armando