Win7, SimpleOpenNI 0.24 win32 > Can't open the depthMap

[GoogleCodeExporter]

When I try to run an example program of the 
SimpleOpenNI-0.24-win32.zip library
I just get this console output: 

SimpleOpenNI Version 0.24
Can't open the depthMap, maybe the camera is not connected!

When I try to run an older Version - SimpleOpenNI 0.20 - I get this error:

SimpleOpenNI Version 0.20
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x73fc02b5, pid=7536, tid=7712
#
# JRE version: 6.0_30-b12
# Java VM: Java HotSpot(TM) Client VM (20.5-b03 mixed mode windows-x86 )
# Problematic frame:
# C  [OpenNI.dll+0x102b5]

I attached the whole crash report of the second test.

---------------  S Y S T E M  ---------------

OS: Windows 7 , 64 bit Build 7601 Service Pack 1

CPU:total 8 (4 cores per cpu, 2 threads per core) family 6 model 26 stepping 5, 
cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, ht

Memory: 4k page, physical 25164216k(17264944k free), swap 50326584k(42772584k 
free)

vm_info: Java HotSpot(TM) Client VM (20.5-b03) for windows-x86 JRE 
(1.6.0_30-b12), built on Nov 10 2011 01:51:00 by "java_re" with MS VC++ 7.1 
(VS2003)

I got two kinects plugged in 

and installed PrimeSense NITE 1.5.2.7 along with PrimeSense Sensor 5.1.0.25 and 
OpenNI 1.5.2.7

On the same machine I got a virtual machine running with osx 10.7.2 lion. On 
this VM SimpleOpenNI works.

Original issue reported on code.google.com by mwebin...@gmail.com on 4 Jan 2012 at 1:45

Attachments:

• hs_err_pid7536.log

[GoogleCodeExporter]

Sorry but I forgot to ask you a question. Which version of Java JDK and 
Processing you prefer for Win7 64? What configuration you use to develope 
SimpleOpenNI?

Thanks in advance for any help

Original comment by mwebin...@gmail.com on 4 Jan 2012 at 1:57

[GoogleCodeExporter]

Can you give me an example of your sourcecode, so i can simulate it ?

Original comment by m...@paus.ch on 4 Jan 2012 at 2:33

[GoogleCodeExporter]

Also, you said you installed:
> and installed PrimeSense NITE 1.5.2.7 along with PrimeSense Sensor 5.1.0.25 
and OpenNI 1.5.2.7

You use the kinect, so you should install the avin2 drivers:
SensorKinect091-Bin-Win32-v5.1.0.25
http://code.google.com/p/simple-openni/downloads/detail?name=OpenNI_NITE_Install
er-Win32-0.24.zip&can=2&q=#makechanges

Original comment by m...@paus.ch on 4 Jan 2012 at 2:43

[GoogleCodeExporter]

should I install the 32bit version of the avin2 drivers? For the already 
installed drivers and java I now switched completely to 64bit. I uninstalled 
everything and reinstalled only 64bit. But still I got "Can't open the 
depthMap, maybe the camera is not connected!"

Regarding the source code I just used the examples that came with the library. 
For example Nite > Hands

Original comment by mwebin...@gmail.com on 4 Jan 2012 at 4:39

[GoogleCodeExporter]

Thought you would like to run the 32bit version of SimpleOpenNI, even if your 
on a 64bit platform:
> When I try to run an example program of the 
> SimpleOpenNI-0.24-win32.zip library
So i assume you wanna go the 64bit way. Then install the 64bit version:
http://code.google.com/p/simple-openni/downloads/detail?name=SimpleOpenNI-0.24-w
in64.zip&can=2&q=#makechanges
http://code.google.com/p/simple-openni/downloads/detail?name=OpenNI_NITE_Install
er-Win64-0.24.zip&can=2&q=#makechanges

Also check that your Processing env. is setup right:
http://code.google.com/p/simple-openni/wiki/Installation

Install also the 64bit java sdk, like mentioned in the install instructions.

Original comment by m...@paus.ch on 4 Jan 2012 at 4:55

[GoogleCodeExporter]

After the version 0.20 did not work I completely switched to 64bits and 0.24. 
Funny thing is that the VMware OSX Lion works great.
Which JDK Version should I install? 5, 6 or 7?

Original comment by mwebin...@gmail.com on 4 Jan 2012 at 5:18

[GoogleCodeExporter]

Still getting "Can't open the depthMap, maybe the camera is not connected!"  
Tried everything 32bit and 64bit and every usb port combination. Kinect and 
Visual Studio samples work without any problems the Opensource MoCap software 
Brekel also works. 

Original comment by mwebin...@gmail.com on 5 Jan 2012 at 2:26

[GoogleCodeExporter]

Ok, so you installed now 64bit(SimpleOpenNI 64bit + SimpleOpenNI 64bit 
installers). 
If you can run the native OpenNI examples, then SimpleOpenNI should work as 
well. 
Did you tried to run it with only 1 camera connected ?

Original comment by m...@paus.ch on 5 Jan 2012 at 2:33

[GoogleCodeExporter]

yes of course. SimpleOpenNI only works on OSX running inside a VMWare machine 
on the same Computer. 
Funny thing is that the MultiCam Example does not work on OSX. It finds Cam1 
and Cam2 but then it also prints "Can't open the depthMap..."
Do you know if there is a Kinect Simulator/Emulator available? I could not find 
one till now. 
Thanks for your help the project is really cool.

Original comment by mwebin...@gmail.com on 5 Jan 2012 at 3:02

[GoogleCodeExporter]

Fixing the depthMap issue:
Unplug Kinect, uninstall the Kinect SDK. Plug Kinect again and let Windows do 
an automatic install of the driver. It works in my case (win7 64bit, processing 
1.5.1, openni 32bit).

Original comment by erand...@gmail.com on 27 Feb 2012 at 3:52

[GoogleCodeExporter]

hi 

I am new to kinect, i installed openni,nite and kinectsensor drivers and i run 
the samples given in primesense folder. Examples are executed and my kinect is 
working. 

I was copied SimpleOpenNI folder into C:\Users\username\Documents\Processing 
this path. And i am trying to use this(import SimpleOpenNI.;) in the program in 
VC++ 2010 but there, it gives errors. 

Errors: 
IntelliSense?: identifier "import" is undefined 
IntelliSense?: variable "SimpleOpenNI" is not a type name 

please Can any one solve my problem 

Original comment by ign...@gmail.com on 29 Feb 2012 at 1:00

[GoogleCodeExporter]

I have encountered the same problem. For windows, the solution is to install 
SensorKinect091-Bin-Win32-v5.1.0.25.msi instead of the higher versions. I guess 
for other platforms you can also try similar solutions.

Original comment by irene.we...@gmail.com on 21 May 2012 at 7:24

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

http://www.youtube.com/watch?v=Bn7Mt4XcVSo see it

Original comment by lepotter...@gmail.com on 17 Aug 2012 at 5:30

[GoogleCodeExporter]

Hi,

I run Win7 32bit fresh install, downloaded the Simple OpenNI 0.27 Win32 
binaries, here what I have:

- Windows 7 32bit Service Pack 1
- KinectSDK 1.6 (USB driver)
- OpenNI Win32 1.5.4.0
- NITE Win32 1.5.2.21
- Sensor Win32 5.1.2.1
- SensorKinect 5.1.0.25 or 5.1.2.1 (I tried both)
- Simple OpenNI 0.27 (installed in 
/Users/username/Documents/Processing/libraries/, once Processing is running I 
see the Examples)
- Kinect attached (Kinect SDK & Toolkit recognizes kinect and demos work)

but Processing 1.5.1 or 2.0b7 won't work and fails with 
   Can't open the depthMap, maybe the camera is not connected!

The issue is, OpenNI NiViewer and NiSimpleRead shows nothing (yes, cmd windows 
appears quickly and disappears), once I called 'cmd' and went into 
OpenNi/Samples/Bin/Releases/ and start NiViewer (can't even select/copy text 
there):
    PrimeSense/SensorKinect/5.1.2.1: The device is not connected.
    PrimeSense/SensorV2/5.1.2.1: The device is not connected.
    PrimeSense/SensorKinect/5.1.2.1: The device is not connected.
    PrimeSense/SensorV2/5.1.2.1: The device is not connected.

I can't believe it is THAT HARD to get OpenNI working on a Win7. Even worse, 
the current libfreenect fails as well - essentially none of the Open Source 
approaches of Kinect & Processing handling on Win7 works . . . both approaches 
are BROKEN.

I'm currently reviewing frameworks to program a video booth (not just 
photobooth) with gesture control, the idea is Processing + OpenCV + GSVideo + 
Simple OpenNI.

:-|

Rene

Original comment by spiritD...@gmail.com on 2 Feb 2013 at 4:45

[GoogleCodeExporter]

The problem seems XBox Kinect and Kinect for Windows behave differently to 
OpenNI, XBox Kinect works with OpenNI, but not Kinect for Windows, but I found 
a solution thanks to Emil Polyak's info:

- Installed KinectSDK 1.6 along with Simple OpenNI 0.27 
- Install additionally http://code.google.com/p/kinect-mssdk-openni-bridge/ 
(read the README_en, start it with 'cmd' as Administrator, and cd into the 
directory of the unpacked package, and call install.bat)
- Test installation with 'nireg -l', last entry should show the new module

"Kinect for Windows" & Processing 1.5.1 & 2.0b7 & Simple OpenNI 0.27 works 
finally

Rene

Original comment by spiritD...@gmail.com on 3 Feb 2013 at 8:28

[GoogleCodeExporter]

I've tried every configuration of 32bit, 64bit, the OpenNI bridge, different 
versions of the PrimeSense Kinect driver, reinstalled the Kinect SDK, all to no 
avail.

A potential jumping off point though is whenever I try and run the 32bit 
version of OpenNI the .dll in the processing library always tries to run 
64bit... is there any way to force processing to run the 32bit version?

Original comment by sevo...@gmail.com on 2 May 2013 at 10:48

[GoogleCodeExporter]

what i should i do with this error? 
SimpleOpenNI Version 0.20
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7359ef95, pid=5396, tid=5012
#
# JRE version: 6.0_37-b06
# Java VM: Java HotSpot(TM) Client VM (20.12-b01 mixed mode windows-x86 )
# Problematic frame:
# C  [OpenNI.dll+0xef95]
#
# An error report file with more information is saved as:
# G:\processing-2.0\hs_err_pid5396.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Could not run the sketch (Target VM failed to initialize).
For more information, read revisions.txt and Help ? Troubleshooting.

i try to following the instruction in this conversation but i can't find the 
solution. help please.

Original comment by amii.na...@gmail.com on 1 Jul 2013 at 3:00

[GoogleCodeExporter]

i tried a fix mentioned above, unplug the kinect and remove all associated 
drivers/software from the Microsoft's Kinect SDK and reconnect and let windows 
instal the drivers(not my fix). cheers to the dude !!!

Original comment by d.kamthe...@my.westminster.ac.uk on 15 Jul 2013 at 1:39