Age | Commit message (Collapse) | Author | |
---|---|---|---|
2016-06-21 | tracker/pt: adjust auto threshold max area size | Stanislaw Halik | |
2016-06-21 | tracker/pt: move pi constant to headers | Stanislaw Halik | |
2016-05-13 | Revert "tracker/pt: experimental non-white color removal" | Stanislaw Halik | |
This reverts commit 546cfb5ad52dcfe1421d1af5e7baeada588ac735. @MathijsG points out that some users have red LEDs, not uniform white. Issue: #355 | |||
2016-04-27 | tracker/pt: experimental non-white color removal | Stanislaw Halik | |
It's enabled only for automatic thresholding. With it on, it's possible to keep tracking in normal light conditions without changing gain or exposure beforehand. It won't function on badly overexposed images, or with other bright white colors in the frame. It should function on somewhat overexposed images. CPU usage is somewhat high, even taking advantage of all OpenCV SIMD goodness as per the code. We can revert the change if user reception is bad. | |||
2016-03-07 | tracker/pt: less malloc/free each frame | Stanislaw Halik | |
2016-02-17 | tracker/pt: fix build | Stanislaw Halik | |
2016-02-17 | tracker/pt: retire get_points() in the extractor | Stanislaw Halik | |
2016-02-17 | tracker/pt: protect get_n_points() | Stanislaw Halik | |
There's a race here since further accesses to the points array aren't protected by a mutex in the extractor class. There's no race in "get_points()" in the extractor since it's only used in same thread where updates take place. | |||
2015-12-28 | tracker/pt: increase auto threshold bucket size againopentrack-2.3-rc21p7 | Stanislaw Halik | |
Slowdown was caused by something else. I can no longer reproduce it. | |||
2015-12-19 | tracker/pt: don't allocate temporary dynamic size arrays | Stanislaw Halik | |
2015-12-19 | tracker/pt: don't copy points array needlessly | Stanislaw Halik | |
2015-12-18 | tracker/pt: reduce mutex contention | Stanislaw Halik | |
2015-10-30 | move to subdirectory-based build system | Stanislaw Halik | |
Closes #224 |