falahati / NiWrapper.Net

OpenNI 2 and NiTE 2 .Net Wrapper
http://www.falahati.net
GNU Lesser General Public License v2.1
52 stars 30 forks source link

Video stream freezes when both rgb and depth streams are used at the same time in 640x320 (or higher) mode. #16

Open sumittada opened 10 years ago

sumittada commented 10 years ago

How to reproduce: update the NiViewer with give files and run it by selecting the new "Color & Depth" option. Choose 640x480@30 Rgb888 for Video mode and 640x480@30 Depth 1Mm. Click the Update button and let the stream run for a few minutes. One or both the streams freeze after a few minutes of running.

Extra details of the test run:

sumittada commented 10 years ago

Here are the sample code files to reproduce the problem. They are taken from the sample NiViewer.Net and the problem can be reproduced when the "Color & Depth" option is chosen with both streams in 640x480 mode.

https://gist.github.com/sumittada/9829236 https://gist.github.com/sumittada/9829242

falahati commented 10 years ago

Thanks sumitta, let me take a look at this, I will get back to you asap.

falahati commented 10 years ago

Unfortunately I couldn't reproduce the issue. Tried compiling as both 32 and 64bit and tested with two devices. (Kinect, Asus Xtion)

I am going to try it on an other machine and see if I can see the problem. Yet I am little busy now.

sumittada commented 10 years ago

Thanks for checking it out! I hope it can be reproduced on other machine. If that doesn't succeed, what do you think is the best way to debug it? Maybe we could try a remote-debug session?

vidstige commented 9 years ago

I'm still seeing this alot. Perhaps we can keep it open for now? I'm suspecting its actually a bug in the OpenNI C-layer.

falahati commented 9 years ago

Unfortunately as I cant reproduce the bug, I cant debug it either. I ask you guys to try to debug it if you had the time and encountered this bug. Even though I am not really sure if this problem is in the wrapper layer, I can guess that it is a multitasking or a buffering problem.

falahati commented 6 years ago

I checked this issue again using the latest release of the library and it wasn't there. But then again I never had this error. So it might be a Kinect thing and I don't have a Kinect anymore.