openframeworks / openframeworks/openFrameworks
Threading issues with multiple Kinects (1414 model)
@ofTheo is already working on this.
Since Jul 29, 2016.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
This is happening with the latest version of openFrameworks. It is on Yosemite with the latest version of xCode on a mac mini.
I understand that, to keep the Kinect communication from dying, a constant 'pinging' of the led's is done to keep the kinect from freezing. I can see this happening in a separate thread when I use verbose messages in the log. ( The 'keep alive' code mentioned in https://github.com/OpenKinect/libfreenect/pull/361 )
I am using three Kinects, all model 1414. After about twenty seconds there seems to be a backlog of threads for the Kinects in trying to maintain the LED connection and the entire arrangement starts losing frames. I used to be able to run this installation for hours at a time without delays (late 2013) but now it becomes almost unusable within three minutes.
Is there a way to disable the LED, or have it occur a little less often? Being able to control it so that there is no more than one Kinect being 'kept alive' per frame might make the system I am developing more useful for more people. Right now, for the working code being distributed, I may have to step back a few generations in Xcode/openframeworks/libfreenect, but that forces people to use only a specific kinect model, which may not be practical.
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.
Assessment
This issue has not been assessed yet.