4 ms·
I hacked the Leap controller at the SF Music Hack day. My team and I built an app called leapJ: multiplayer DJ'ing with your body. (https://www.hackerleague.org
by bravura 12y ago
I hacked the Leap controller at the SF Music Hack day. My team and I built an app called leapJ: multiplayer DJ'ing with your body. (https://www.hackerleague.org/hackathons/music-hack-day-san-francisco-2014/hacks/leapj https://www.hackerleague.org/hackathons/music-hack-day-san-f...)
Leap is a great little device. My main complaint is that the API is too low-level. We would just fire events roughly every 20ms, in a markovian (stateless) way. For this reason, the instrument control was somewhat janky, because we didn't have the time to de-jitter hand paths / infer a tracking spline.
My wishlist for leap is:
* Higher level APIs, that apply the sort of sophisticated filtering and tracking that many people are liable to roll themselves.
* Multiple leap devices per computer. Needing a separate computer per leap is a big barrier to working with several leaps at once.
* ARM support. I'd love to have a RaspberryPI for each leap. Then they would be truly mobile. For right now, I think I'm going to have to get a mini ITX motherboard,
- sitkack 12y agoYou need a smoothing library. I welcome our low level access, you can always pile what you need on top, the converse is not possible. What would be nice is some intelligence pushed down into the Leap, like the ability to run Lua or JVM code directly so that realtime multidevice is possible.
- scott_karana 12y agoI think he meant augmenting your API with higher-level stuff, but not removing any of the low level access. :-)