Thanks for the information, that really helps to narrow down where the real issue might be.
It sounds like the slowdown is very specifically in the function that generates the player index rather than with the USB bandwidth or the body tracking library in general.
On my end it is just a single call to retrieve the image and I don’t really know what is going on behind the scenes and how that interacts with Orbbec’s kinect emulation code. I will pass this info along to Orbbec and let you know if I hear anything else.
I’ve tried different cables and ports with different chipsets, this issue is not related to that. Femto bolt is detected as USB 3.1 and works ok in other apps. Also the original Kinect Azure works ok in same ports with same cables and TouchDesigner Kinect Azure Top with Player Index and Color at the same time. The problem is only with the Orbbec K4A Wrapper in TouchDesigner when using the Player Index image. I hope you can find a solution soon. Thanks
Everyone at FemtoBolt and Mega, if you encounter any issues, could you please share your screen with me? I will arrange for support. Everything is currently testing fine on my end
Hi Jack - I tried updating the Orbbec SDK as outlined in your video on TouchDesigner 11760 with the camera running 1.1.2. I’m still seeing pronounced freezing of the point cloud and color images when using player index. I’d be happy to screen share if it helps resolve this faster.
unfortunately, I’m still having issues with my Femto mega lagging behind in one of the views even with the “sync to bodytracking” enabled. Is there anything im maybe missing?
Body Tracking SDK version is 1.1.2 and
Sensor SDK Version is 1.4.0_6433845a3
