invalid memory access

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Yesterday Mappinect opened at run. Today it doesn't, neither in the compiled 
version, nor by processing.

2.
3.

What is the expected output? What do you see instead?

Processing gives: 

OscP5 0.9.6 infos, comments, questions at http://www.sojamo.de/oscP5

### [2011/11/10 9:21:51] PROCESS @ OscP5 stopped.
### [2011/11/10 9:21:51] PROCESS @ UdpClient.openSocket udp socket initialized.
### [2011/11/10 9:21:52] PROCESS @ UdpServer.start() new Unicast DatagramSocket 
created @ port 4000
### [2011/11/10 9:21:52] PROCESS @ UdpServer.run() UdpServer is running @ 4000
### [2011/11/10 9:21:52] INFO @ OscP5 is running. you (10.0.1.2) are listening 
@ port 4000
Settings loaded :
 -> midiOutputDeviceID :2
 -> oscDefaultInPort :4000
 -> oscDefaultOutPort :4444
 -> oscDefaultHost :127.0.0.1
 -> oscAddressPrefix :/mappInect
SimpleOpenNI Version 0.20
Invalid memory access of location 0x8 eip=0x32f58fda

What version of the product are you using? On what operating system?

macosx 10.6.8, mappinect 1

Please provide any additional information below.

Please help!

Original issue reported on code.google.com by michele....@gmail.com on 10 Nov 2011 at 8:24

[GoogleCodeExporter]

I tried also to set in config.xml "live_jazz.xml" as mapping, but the error 
remain.

Original comment by michele....@gmail.com on 10 Nov 2011 at 8:26

[GoogleCodeExporter]

Assuming you didn't change anything before and after the problem, i think it's 
more an OpenNI matter.
Have you tested simpleOpenNI examples to see if the library works ?
And if it doesn't work, you can try the samples from OpenNI (not the processing 
library).

If the examples work, well i frankly don't know where this comes from but i'll 
have a closer look if you confirm it comes from my code.

Original comment by bkuperb...@gmail.com on 10 Nov 2011 at 8:31

[GoogleCodeExporter]

Right, neither SimpleOpenni examples seems to run, and gives the same error.
I tried also to reinstall Simpleopenni without luck.
So the problem isn't in your code.
If i can solve it i'll post here the solution.

Original comment by michele....@gmail.com on 10 Nov 2011 at 8:49

[GoogleCodeExporter]

Solved.
Was quite a stupid mistake. Kinect was plugged in my mac, and its led on. BUT: 
its power source was plugged to a off-swithced plug. So, simply turing on the 
power source solved the problem. Stupid me, two hours working time wasted.

Original comment by michele....@gmail.com on 10 Nov 2011 at 9:09

[GoogleCodeExporter]

Original comment by bkuperb...@gmail.com on 10 Nov 2011 at 12:01

• Changed state: WorkAsDesigned