.oni files are read 2 times slower. about jit.openni

[diablodale]

From what I can determine, this is a fault in OpenNI itself. I can reproduce the same behavior using only the OpenNI samples binaries. Try this yourself:

1. install a working Kinect
2. Use the NiViewer application to record a 20 second clip. Do something very obvious that can be timed like waving your finger in 1 second intervals. I did this watching a stopwatch.
3. close NiViewer
4. run NiViewer and on the commandline, give it the filename of the recording you just made
5. watch the results
   The playback is too slow. My estimation is that it is 1.5x too slow.

Do you reproduce this problem give my steps above? If so, then this is a bug in the OpenNI code and not one that I can fix. You can, however, workaround the issue in your own patch. When you have a recording loaded, bang jit.openni approximately 1.5x faster. In the demo patch I provide, I banged it at 22ms (which is about 45fps)

[totoetlititi]

Exactly, same problem with NiViewer.
But what I see is more complex, speed seems variable : some parts of the video is very slower, and some part just a bit slower...
In this case, changing bang speed is not a valid trick !

[diablodale]

Unfortunately, this is a bug in OpenNI itself. I am not able to fix this. I don't control the code, they do.
If you would like, you can get the source code for OpenNI, debug this issue, fix it, and compile it yourself. However, I don't recommend it.

If you are on Windows, I recommend you use dp.kinect instead. The Microsoft Kinect SDK is far more reliable and therefore the external benefits from it.

I may be able to give you advice or a recommendation if I better understand your need for accurate time playback of ONI files. Would you share that?

[diablodale]

I am closing this issue as the bug is external (PrimeSense's bug) and they are not going to fix it.

If you feel I have not addressed your concern, please reopen this issue