I am getting exactly the same “UnsatisfiedLink” error when using Processing and Windows 7 x64.
It does work, however, if you export the application.
I have tried different Processing versions, different SDK versions, several path strings variations and dll locations… with no success.
No problem at all using Windows XP with the very same software versions.
Any thoughts/updates on this?

Javier G. - 02 November 2010 10:46 AM

I am getting exactly the same “UnsatisfiedLink” error when using Processing and Windows 7 x64.
It does work, however, if you export the application.
I have tried different Processing versions, different SDK versions, several path strings variations and dll locations… with no success.
No problem at all using Windows XP with the very same software versions.
Any thoughts/updates on this?

While Code Laboratories is fixing the newest build, I found that I could extract a dll from the older version of the SDK (attached to my message in this thread), point my processing sketch to it, and it started to work (Win 7 64 bit).

eight - 02 November 2010 11:15 AM

Javier G. - 02 November 2010 10:46 AM

I am getting exactly the same “UnsatisfiedLink” error when using Processing and Windows 7 x64.
It does work, however, if you export the application.
I have tried different Processing versions, different SDK versions, several path strings variations and dll locations… with no success.
No problem at all using Windows XP with the very same software versions.
Any thoughts/updates on this?

While Code Laboratories is fixing the newest build, I found that I could extract a dll from the older version of the SDK (attached to my message in this thread), point my processing sketch to it, and it started to work (Win 7 64 bit).

@eight: Thanks, but no luck either…
I might be doing something wrong or misunderstood the procedure. I have tried installing the older version of the SDK you attached, and also reinstalling the newest SDK and replacing the dll with the older one.
Could you please provide more info about the actual procedure?

Javier G. - 02 November 2010 10:46 AM

Could you please provide more info about the actual procedure?

I haven’t tried to install old sdk.

Using 7-zip.exe archiver:

Right Click on downloaded sdk -> 7-Zip -> Extract files… to a directory -> navigate to this extraction directory/$_OUTDIR/Bin/—> copy CLEyeMulticam.dll into any /directory/of/your/choice/.

Open CLEyeMulticamTest.pde in Processing. Locate the following line in the setup() method:

and replace the path with the “/directory/of/your/choice/CLEyeMulticam.dll” above.

That’s it!

Thanks eight!
It’s working now!
The key was extracting the dll from the old executable.

I agree, it does sound a bit like a ‘quick fix’ solution.Surely you can never be 100% absolutely certain that something won’t go wrong.

eight - 02 November 2010 11:58 AM

Open CLEyeMulticamTest.pde in Processing. Locate the following line in the setup() method:

CLCamera.loadLibrary("C://PATH//TO//CL-EYE SDK FOLDER//Bin//CLEyeMulticam.dll"); 

and replace the path with the “/directory/of/your/choice/CLEyeMulticam.dll” above.

Here I am in september 2011 struggling with the same errors. I had to uninstall the current version of CLEye SDK and use the dll provided by eight. And now it works, after more than 3 hours banging my head.

windows 7 64.

thanks.

Hi Guys,

I’m also experiencing the “Invalid access to memory location” when trying to use the latest dll in my java application (it uses awt and threads).  I believe the problem has something to do with running a 32bit JVM on a 64bit system.  Trying to debug it, I found that forcing the application to load shell32.dll from /windows/syswow64 explicitly helped (seems that the CLEyeMulticam.dll clashes with a WOW64 redirected system32 import), but it is now crashing due to a thread starting.  Any help you could provide would be appreciated as I’m locked into a 32bit JVM and need to support both 32 and 64bit Windows boxes with my application.

Cheers,

mlk