openframeworks / openframeworks/openFrameworks
strange issue with latest ofxKinect and multiple Kinects
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
I recently updated my Xcode, and in doing so ended up with a number of code breaks, which prompted me to update to the latest openFrameworks (0.8.4) which included new ofxKinect files.
Since then, when running my rebuilt software that uses multiple Kinects, I have noticed a series of pauses that seem to be centered around threads which are getting opened, closed, etc. They don't happen right away, but tend to occur after a minute or two.
The Kinects have not changed, but I recall for the Kinect4Windows and newer models, there was some top-secret-mumbo-jumbo being done using LED's to maintain a connection to a Kinect and prevent it from timing out.
Mine are all, currently the original 1414 models, so this shouldn't be an issue, but I am unsure how to avoid the LED check thingie which is giving me so much grief. I will eventually have to have this code work with all models of Kinect once it is available for others to use.
Is there a way to opt-out for the led check if it is not needed?
This is OS X yosemite, on Xcode 6.0, on an i7 mac mini.
(sorry, I don't seem to be able to label this post properly)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No specific file or test is named. Start by tracing the updated ofxKinect code that opens and closes threads and performs the LED check, then reproduce the pauses with multiple original 1414 Kinects on OS X Yosemite; done means identifying whether the LED check causes the pauses and establishing whether it can be opted out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100