Steps causing the bug to occur
- Launch the example composition ‘DisplayLeapHand.vuo’
- Connect Leap Motion Controller
- Run Composition
- Visually observe delay in hand motions
- Confirm delay by inspecting the output of the ‘hands’ value from the Get Frame Values node while moving hand above leap and removing it.
How did the result differ from what you expected?
There is a delay, ranging from about 1/2 second to several seconds from when my hand moves over the leap controller and when the value of ‘hands’ coming from the Get Frame Values node is updated.
I also tested my leap motion with the ‘Visualizer’ app from leap - it seems to be working fine, no delay.
I tested a composition with less going on - the hand and pointer count - CountLeapObjects.vuo - after I increased the fire periodically rate to .02 there was no noticeable delay from when I moved my hand over the leap and when the console logged it’s presence.
It seems like the delay is happening with compositions that have more complex rendering.
My machine specs:
Mac Book Pro mid 2012 2.6ghz Intel Core i7 with 8gb Ram. NVIDIA GeForce GT 650M 1024 MB graphics card
OS 10.8.5
When did you first notice this bug?
Experimenting with Vuo .0.5.2 today
Have you found a workaround?
not yet
Other notes
- Vuo version: 0.5.2
- macOS version: OS X 10.8
DisplayLeapHand.vuo (12.5 KB)
CountLeapObjects_mod.vuo (2.85 KB)