-
Notifications
You must be signed in to change notification settings - Fork 622
When can we expect body tracking on ARM64? #1342
Comments
Just wondering if there has been any update since this last comment on the issue (that I can find), which was back in April. Completely appreciate that these things take time, but just wondering if there is an ETA? I have depth/RGB camera input working perfectly on Nvidia Jetson Xavier NX, but of course body tracking is still officially not supported yet for this platform. |
This is still under development. |
Yes, understood that it is still in development, but was curious if there was any rough timeline? I don't want to put pressure on developers, but since the last update was 5 months ago, I was wondering if it was something coming soon (in the next month) or still half a year away? |
@qm13 Hi ! |
As far as I know, Body Tracking works just fine on Linux! See https://docs.microsoft.com/en-us/azure/kinect-dk/body-sdk-download#linux-installation-instructions But currently it only works for x64 architecture. Whereas I would like to try running this on a Jetson Xavier, which uses ARM64. |
@qm13 https://developer.nvidia.com/blog/announcing-onnx-runtime-for-jetson/ |
Any news on ARM64 support for Body Tracking? I have read somewhere an estimation that Xavier NX will be capable, is there any information about this regard? |
+1 for status update. Is this something perhaps the community could help contribute? If so do you have any pointers on how to go about doing this for folks staring out? Hoping to get body tracking working on nvidia xavier |
Any news on ARM64 support for Body Tracking? |
Unfortunately we have encountered some sever issues getting body tracking running performantly on ARM64. |
@qm13 does that mean you are pausing it, or just working through the issues, and will release soon? |
Still hopefully waiting for the support.. |
Duplicate of #871. |
Body Tracking team is also adding ARM support. A new version of BT is coming that will work with 1.4.0.
Originally posted by @wes-b in #1093 (comment)
The text was updated successfully, but these errors were encountered: