Skip to content
This repository has been archived by the owner on Aug 22, 2024. It is now read-only.

Separate capture from depth calculation #1718

Open
ngeorgis opened this issue Dec 24, 2021 · 0 comments
Open

Separate capture from depth calculation #1718

ngeorgis opened this issue Dec 24, 2021 · 0 comments
Assignees
Labels
Enhancement New feature or request

Comments

@ngeorgis
Copy link

It would be nice to have the ability to capture raw data from sensors and do not run any processing during capture. This would enable lower resource CPU/GPU or no-GPU systems to be used as capture nodes.

In the current implementation my understanding is capture of raw depth is not possible. Instead there is a requirement for a fast-enough GPU to be used for depth engine calculations running on the capture system. In some workflows it is better to capture in real-time, and run depth engine calculation later, not in real-time. We could also choose to run own custom depth engine in real-time and we do not want the GPU to be busy as currently is the case. I could not find any way to implement this two-phase Capture/Process approach in the current SDK but I may have missed this feature.

@ngeorgis ngeorgis added Enhancement New feature or request Triage Needed The Issue still needs to be reviewed by Azure Kinect team members. labels Dec 24, 2021
@qm13 qm13 removed the Triage Needed The Issue still needs to be reviewed by Azure Kinect team members. label Dec 29, 2021
@qm13 qm13 self-assigned this Dec 29, 2021
@qm13 qm13 assigned dasparli and unassigned qm13 Apr 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants