Asus and Leap Motion Bring Minority Report-Style Gestures to Life
wired.com
wired.com
I'm dying to get my hands on one of these awesome things and I have tons of use for it, but I'm seriously not interested in putting "apps" on Leap's "app store" and I don't like this trend at all. If, for example, Chrome adds APIs for extensions and apps to access Leap Motion, I want my cross-platform "app" to be discoverable on the Chrome store.
With the app store nonsense (imo), I feel Leap is distracting themselves from the real task of getting their device out on every damn machine out there and getting their SDK into every dev's hands.
Disagree? I'm all ears.
> There isn't any reason that they couldn't make your example feasible.
That can happen if they, for example, won't license their SDK to be bundled as APIs for "Chrome packaged apps". If they did, there may not be an incentive to have your app live on their app store. I don't at the moment know what's in their SDKs, but setting up an app store can introduce such (imho artificial) conflicts of interest.
OTOH, it's their product and they may very well say "it's exclusive, folks". The irony is that I'm a bit pissed because I want this bad .. and without those ropes! Hope I'm not required to put apps on their store. Furthermore, I hope Wacom doesn't catch on to this trend and start a "Wacom App Store" as well.
When I envisioned a future of digital downloads, this is not what I imagined.
Edit: I forgot Mozilla and Facebook.
The benefit of these "app stores" is lost when they are so splintered.
The current trend towards everyone having their own "app store" is almost as annoying as every app developer wanting to install their own update manager that starts on computer bootup. Screw that noise, just because I'm using your shit doesn't mean it is that important to me.
Agree.
I'd imagine waving my broken shower head over it for a while, then using some sort of 3D magic software I could get a half decent CAD file that I could 3D print and repair that bad boy.
Besides, what you ask already exists, in the form of 3D scanners.
Being bundled with Asus is nice, but I think it's difficult for a PC maker to differentiate themselves.
When you go to buy a computer does anyone decide feature wise between an Asus or a Samsung? One big decision is Mac or PC. When you decide PC, you look for some deals or good prices.
You're right.
2 feet x 2 feet x 2 feet = 8 cubic feet.
Edit: Oh and yes feature set is important, but I find that just about all mid range to high end laptops have everything I want (USB 3.0, Webcam for programming stuff, 1080p screen (I chose my ASUS over a Samsung because it has excellent speakers and a sub woofer bullet. [both of which blast out beautiful sound.])
By look-down I visualize it attached to the top of my display and looking down.
The advantage would be that your hands are supported by a table. This would lower the muscle strain when interacting with a device for a long period of time.
My unit doesn't have the final casing, so the basic components are in plain sight. There are two cameras and some infrared LEDs. The LEDs appear to emit a sequence of pulses which is seen by the cameras at a high frame rate -- somewhere in the Leap docs it's mentioned that the highest frame rate sent by the device over USB is around 300 fps.
The magic is in the processing, of course. I don't know how that is split between the device and the Leap driver running on the host computer.
The data obtained through the SDK is preprocessed into hands that are further divided into fingers or "tools" such as a pencil being held by the user. It doesn't seem to be possible to get raw depth data, but the hand data is high quality and the latency is impressive -- it feels very good in use.
The Leap doesn't have an infrared projector that could emit a precise pattern, but it has two infrared cameras that run at a much higher rate than the Kinect's. I think the Leap's depth detection is based primarily on stereo vision mapping with some kind of temporal component.
I'm picturing a future full (virtual) keyboard interface for google glass. Thoughts? concerns?
Leak in 3.. 2..