Skip to content
This repository was archived by the owner on Jul 26, 2024. It is now read-only.

Body tracking latency #109

Closed
pengy8 opened this issue Jan 17, 2020 · 3 comments · Fixed by #161
Closed

Body tracking latency #109

pengy8 opened this issue Jan 17, 2020 · 3 comments · Fixed by #161
Assignees
Labels
enhancement New feature or request investigate Used when investigation needed ROS1 SDK_Issue This is an issue in the Azure Kinect SDK, not the ROS Node triage approved The Issue has been reviewed and approved for development by the Azure Kinect ROS Driver Team

Comments

@pengy8
Copy link

pengy8 commented Jan 17, 2020

Is your feature request related to a problem? Please describe.
The body tracking data in the ROS driver is very useful to my application, but somehow there's about 1-second latency in the reported data. However, the data seen in the body tracking SDK is faster (about 0.25 second).

Describe the solution you'd like
Is there any way to improve the body tracking data latency in the ROS driver to be close to the SDK's speed?

Describe alternatives you've considered
NA

Additional context
NA

@pengy8 pengy8 added enhancement New feature or request triage needed The Issue still needs to be reviewed by the Azure Kinect ROS Driver Team labels Jan 17, 2020
@ooeygui ooeygui self-assigned this Jan 20, 2020
@ooeygui ooeygui added investigate Used when investigation needed ROS1 triage approved The Issue has been reviewed and approved for development by the Azure Kinect ROS Driver Team and removed triage needed The Issue still needs to be reviewed by the Azure Kinect ROS Driver Team labels Jun 28, 2020
@ooeygui
Copy link
Member

ooeygui commented Jun 28, 2020

It may be due to the double hop though pub/sub.

@RoseFlunder
Copy link
Contributor

RoseFlunder commented Jun 29, 2020

There is also a huge discussion when it comes to the latency about the body tracking sdk in the sdk repository:
microsoft/Azure-Kinect-Sensor-SDK#514

I am on mobile at the moment but I remember that one person wrote that there is like 1 buffered frame in the body tracker after creation. He got less latency when he pulled that from the body tracker instance before queing new frames. Maybe you can test this.

@ooeygui
Copy link
Member

ooeygui commented Jun 29, 2020

@RoseFlunder Thank you for linking this in.

@ooeygui ooeygui added the SDK_Issue This is an issue in the Azure Kinect SDK, not the ROS Node label Jun 29, 2020
zchenpds added a commit to zchenpds/Azure_Kinect_ROS_Driver that referenced this issue Nov 16, 2020
zchenpds added a commit to zchenpds/Azure_Kinect_ROS_Driver that referenced this issue Nov 16, 2020
zchenpds added a commit to zchenpds/Azure_Kinect_ROS_Driver that referenced this issue Nov 17, 2020
zchenpds added a commit to zchenpds/Azure_Kinect_ROS_Driver that referenced this issue Nov 17, 2020
zchenpds added a commit to zchenpds/Azure_Kinect_ROS_Driver that referenced this issue Nov 17, 2020
zchenpds added a commit to zchenpds/Azure_Kinect_ROS_Driver that referenced this issue Nov 18, 2020
zchenpds added a commit to zchenpds/Azure_Kinect_ROS_Driver that referenced this issue Nov 29, 2020
amelhassan pushed a commit to zchenpds/Azure_Kinect_ROS_Driver that referenced this issue Oct 29, 2021
amelhassan added a commit that referenced this issue Oct 30, 2021
Use a separate thread to pop k4abt_tracker result. Fix #109.
amelhassan added a commit that referenced this issue Oct 30, 2021
Use a separate thread to pop k4abt_tracker result. Fix #109.
ooeygui pushed a commit to ooeygui/Azure_Kinect_ROS_Driver that referenced this issue Apr 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request investigate Used when investigation needed ROS1 SDK_Issue This is an issue in the Azure Kinect SDK, not the ROS Node triage approved The Issue has been reviewed and approved for development by the Azure Kinect ROS Driver Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants