Yes the outages occur when using the V4 API. I have the feeling that when using low performance CPU / GPU machines, the problem is more common. Still need to test to find out the pattern!
meanwhile, might roll back to V3.2 for stability sake…
Hum, ok It’s maybe not the same issue I encountered then, because my problem was only with ORION API and V4 was ok for me. Rolling back to 3.2 would be a solution, but I think the tracking is less accurate, and you won’t have access to Orion API.
Leapmotion is still “touchy” to use, but maybe indeed, the solution will come from testing (different leap, different USB load, Different Computer, Light situation…)
And if it’s very short and rare outages, It’s always a good solution to mitigate them inside Touchdesigner with subtle CHOP lag or other solutions (Very good video series about this by Ian Shelanskey : TouchDesigner Tutorial - Denoising Sensor Data - Part 1 - YouTube)
@ruigato sorry I missed your previous message. We don’t have any immediate plans to update our leap support, but the new drivers definitely look interesting and it sounds like they’ve addressed some of the major issues I’ve heard from users.
I will keep an eye on things and bring it up during our next planning session.
thats great @robmc, thank you for the update on the status
right now I’m facing a crash when using a intel NUC with the version 2 API drivers, probably because of the absence of dedicated graphics card. This issue does not occur when using version 2 with a full PC with NVIDIA.
I can send you the crash .dmp file if you are interested, but might be more productive to move over to version 5 if the issues found on version 4 get solved with that!
edit:
the major issue with version 4 is the onset of the tracking state, and the intermittent disconnection listed above