Has anyone successfully used the processing simpleOPENNI library and exported a processing application that runs ? (on a mac)
I have a mac osx 10.8 and I am using SimpleOpenNI library that is giving trouble when compiling an application. When just running the processing sketch, it runs no problem. But it won't work with a compiled app. How can I run a compiled application for a Mac using the SimpleOpenNI library???
This is similar to this forum but the solution presented here is not working for my problem on a mac :https://code.google.com/p/simple-openni/issues/detail?id=73
This happens when I Compile application with proccessing then run the application. The processing sketch works fine.
The Application fails to load openni libs with error:
Exception in thread "Animation Thread" java.lang.UnsatisfiedLinkError:
SimpleOpenNI.SimpleOp at SimpleOpenNI.SimpleOpenNiJNI.swig_module_init(Native Method)
at SimpleOpenNI.SimpleOpenNIJNI.(SimpleOpenNIJNI.java:290) at
SimpleOpenNI.ContextWrapper.(ContextWrapper.java:54) at SimpleOpenNI.SimpleOpenNI.
(SimpleOpenNi.java:256) at LanScapesLerp.setup(LanScapesLerp.java:126) at
processing.core.PApplet.run(PApplet.java:1530) at
processing.core.PApplet.handleDraw(PApplet.java:1608) at
java.lang.Thread.run(Thread.java:680)
Have you tried installing the library a different way, such as downloading it from a website (https://code.google.com/p/simple-openni/) this has seemed to work for most people with java.lang.UnsatasfiedLinkError
Related
I am trying to execute the following basic psychopy (version 2021.2.3) code through the Python 3.6.13 console:
import psychopy.visual as pv
pv.Window()
Which gives the following error.
*** stack smashing detected ***: <unknown> terminated
Aborted (core dumped)
The only related topic I can find is on the psychopy forum with no answers
I'm running this on an Ubuntu 18.04.05 machine. The machine is initialized as a headless server, but I am trying to run this through RDP.
I installed psychopy using pip inside a conda environment. Initially I was getting errors related to wxPython. When I manually installed wxPython from a whl file that error was resolved and error in this question appeared.
My guess is that this is to do with the version of one of the libraries but very hard to tell from this limited info.
What version of PsychoPy are you trying to install and by what means are you installing it? Are you running from the app or is this a script you're trying to launch from the terminal? ie. trying to work out what parts of PsychoPy this is affecting (the app, the visual lib, the gui libs...?)
I had a very similar problem on ubuntu 18.04.5, psychopy 3.2.4, no headless server. I suspect that the problem is general but ubuntu/drivers related.
My solution was to update the system and to install&switch to a proprietary NVIDIA driver.
I'm writing software via NetBeans to interface with a Ocean View spectrometer and I'm running into an issue with deploying my jar file to a Raspberry Pi 3 without running into a n RunTimeException. I correctly followed the steps to deploy remote java jar files on the NetBeans IDE, but can't get past this error "Caused by: java.lang.RuntimeException: Failed to load any native library for USB. Tried base filenames: NatUSB_32, NatUSB_64"
Screenshot of the error in console here
My code runs successfully when compiled on the IDE, but not on the Raspberry Pi. I'm using JDK 8, and have the class path set to include OmniDriver.jar. Any help on troubleshooting this issue would be appreciated!
I am having difficulty with Titanium cross mobile development platform, i am getting error "failed to load JNI shared library c:\programfiles\java\jdk 1.6.0 _45\bin\server\jvm.dll.
could any one help.Thanks in advance.
Did you read System Requirements?
From Documentation:
For Windows, the 32-bit version of Java JDK is required regardless of
whether Titanium is running on a 32-bit or 64-bit system.
Try to install additional 32bit version of Java (without removing the 64bit) and set the system variable.
You can refer the following links for it
Failed to load the jni shared library jvmdll Titanium
Failed to load the jni shared library jdk - Eclipse
Hope it helped you
I have been using SimpleOpenNI, a wrapper for Processing, all summer now. I use it for the Kinect to make games and demos. Last week, I have been getting a fatal error in my processing window and none of the SimpleOpenNI projects will work. Here is the error:
SimpleOpenNI Version 0.20
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x72e8f955, pid=4596, tid=4624
JRE version: 6.0_24-b07
Java VM: Java HotSpot(TM) Client VM (19.1-b02 mixed mode windows-x86 )
Problematic frame:
C [OpenNI.dll+0xf955]
An error report file with more information is saved as:
C:\Users\mss042\Desktop\processing-1.5.1\hs_err_pid4596.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.
It appears as if the new OpenNI/NITE/SensorKinect drivers do not work with the SimpleOpenNI wrapper. I have tried it with people using the old drivers and everything still works. Problem is, you cannot download the old drivers off of the websites so I cannot test if it's that or not. You can see everything I've downloaded from the simpleopenni site: http://code.google.com/p/simple-openni/
Any help with this error would be appreciated. Thanks.
Mike
It looks like there's a problem with OpenNI.dll. Make sure that:
You have the dll (It should be in Program Files where you've installed OpenNI)
Make sure you've got the Environment Variables for the Open NI paths and that the paths are correct, otherwise, you might have the .dll file, but the .jnilib wouldn't know where it is.
Had a Kinect Workshop in Uni, and my colleagues using Windows all had issues with the drivers,
so I'm just passing on what they did:
Even though they had 64-bit versions of Windows they used the 32-bit version, and used Brekel OpenNI Kinect Auto Installer - Developer Edition v1.3.2.3.exe(direct link via developkinect.com) after reading this message:
Comment 4 by tijmenva...#gmail.com, Oct 21, 2011 Hey all I have Solved
the unsatisfied link dll error on windows 7 64 bits by installing java
runtime (jre-7u1-windows-i586.exe)and (Brekel OpenNI Kinect Auto
Installer - Developer Edition v1.3.2.3.exe) I uninstalled everything
and than it worked :)
hope this helpes
in Issue#17 on the SimpleOpenNI project issues page.
Another colleague used Synapse and OSC in Processing instead of SimpleOpenNI, but she had loads of errors with the drivers (basically spent a few good hours uninstalling/installing different versions). In her case, uninstalling any previous partial or complete drivers from the machine and deleting any registry entries related to PrimeSense(Sensor, Nite) and OpenNI, then using the installers from the links on the Synapse page, worked for her.
HTH
This is a long shot, but that exact error is also given if the Kinect USB and/or power supply simply becomes unplugged. Thought it was worth mentioning as it is not obvious from the error message itself and it may help someone out if they kicked their power supply and started searching for the above exception :)
I'm developing a solution for Windows CE 6.0 using GuD_AtomKit X86 Device emulator.
I'm not able to run any unit tests, because I get following error message:
The test adapter ('Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestAdapter, Microsoft.VisualStudio.QualityTools.Tips.UnitTest.Adapter, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a') required to execute this test could not be loaded. Check that the test adapter is installed properly. Exception of type 'Microsoft.VisualStudio.SmartDevice.TestHostAdapter.DeviceAgent.TestAlreadyRunningException' was thrown.
But there's no unit test running on the device.
I would really appreciate your help.
Did you change the target device in your testrunconfig file? Running against the target device is definitely supported.
You also might have to manually deploy the CF to the device as the Unit Test framework doesn't auto-deploy it.
That was probably caused by a hardware issue. After I updated the flash with the board I was running the test against, it started to work again. So probably a bug in the firmware of the board... :(