4 ms·
I wonder how accurate it really is. The demo video didn't match up with the movements at all and the on-screen drawings looked like prerecorded video that they
by jstapels 11y ago
I wonder how accurate it really is. The demo video didn't match up with the movements at all and the on-screen drawings looked like prerecorded video that they were trying to sync to.
It's a neat idea, but without a dedicated component or an extremely high-speed RTOS, you're not going to come close to the level accuracy that's really needed to do the math and still allow interaction.
I don't mean to rain on the parade, but I just don't think they really have anything usable.
- noir-york 11y agoIf the tech is great then wonderful, but I still remember LeapMotion...
- bossx 11y agoHave you tried the Orion SDK? It's an order of magnitude improvement in tracking accuracy, even with the older hardware. https://developer.leapmotion.com/orion https://developer.leapmotion.com/orion
- alexwebb2 11y agoI tried the "massive improvement" they released before Orion and it was still terrible. Only so many times a company can say they've got their issues ironed out before I stop believing them.
- LesZedCB 11y agoOrion really is quite impressive. I tried the improvement as well. Orion actually works.
- ajacksified 11y agoHmm, I'll have to try it out tonight. I have some 4-year-old v0.6 and v0.8 hardware in a drawer somewhere.
- MasterScrat 11y agoLeapMotion is not precise?
- CarVac 11y agoTo me it looked like a ton (two seconds or so) of latency, not pre-recorded video. And I would expect latency for such heavy DSP work on a phone.
- Mithaldu 11y agoThis is correct. The movements match up just fine, but the reaction time there is something above 2 seconds.
- foobarqux 11y agoThey need to buffer to get a Fourier transform and to do the autocorrelation.
- tobr 11y agoThey say they use an "inaudible high frequency soundwave", so that should be > 20kHz. Shouldn't a buffer of a few milliseconds be more than enough then?
- foobarqux 11y agoPresumably the buffer is longer to make the system more robust by avoiding spurious detections, not because of some fundamental limit like the Nyquist rate. You would need to set the buffer size experimentally.
- aiabgold 11y ago> I just don't think they really have anything usable. I'm not sure that's the purpose. I wouldn't think of this as being intended to be a fully usable product right now. They could be intending it merely as an interesting experiment to explore new possibilities for interaction with mobile and wearable tech. Another CS student came up with a virtual keyboard using the iPhone's accelerometer[1]. It only had ~80% accuracy[2], so was it all that useful or practical? Probably not. But could it lead to another person or company refining the technique for production in the future? Certainly. [1] Video: https://vimeo.com/49780741 https://vimeo.com/49780741 [2] http://www.gottabemobile.com/2012/11/13/cs-student-turns-iphone-accelerometer-into-virtual-keyboard/ http://www.gottabemobile.com/2012/11/13/cs-student-turns-iph...
- melling 11y agoI bet you have RSI within a week banging on a desk like that. If it comes down to using something other than your fingers, someone has the nose working as a user input device: http://www.looknohands.me http://www.looknohands.me
- pbreit 11y agoI would totally disagree. I don't think it would have to have much fidelity or low latency be insanely useful. The huge advantage is no extra hardware necessary. And maybe it might be hard for you to believe it could do what you want it to do but I'm guessing your vision is pretty narrow.
- jcoffland 11y agoThis reads like a personal attack.