[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, bug report, or anything other than a feature request directly related to this project.
Proposal
First of all, amazing work! Love using this driver.
Not a big expert on the SDK, but it appears to me that in this driver e.g. image / depth frequencies are tightly coupled.
Slow depth estimates may thus lead to slow image publishing?
Would it be possible to have these somehow run asynchronously?
Use-Case
Image processing / recording irrespective of depth estimate. Might cause a whole lot of synchronicity issues.. Hence looking forward to the feedback / some insights!
Preliminary Checks
Proposal
First of all, amazing work! Love using this driver.
Not a big expert on the SDK, but it appears to me that in this driver e.g. image / depth frequencies are tightly coupled.
Slow depth estimates may thus lead to slow image publishing?
Would it be possible to have these somehow run asynchronously?
Use-Case
Image processing / recording irrespective of depth estimate. Might cause a whole lot of synchronicity issues.. Hence looking forward to the feedback / some insights!
Anything else?
No response