AlexP,
Sometime ago someone in the Processing community has written a Processing/Java library or wrapper for your driver to use the camera to Java. It is a great way to attract visual artists and multitouch folks. Now I can’t find links to the Dec 09 version of your driver before someone told me the CL-driver is the current version. Unfortunately the person that wrote the wrapper is too busy to follow your recent updates so his library only works with your PS3Eye Camera Setup v3.0.0.0901.exe or older.
So could you still provide a link to this file? Thank you!
Don’t seem to work. The link gets back to this website, which contains only the latest driver. I mean the link that says version 3.0.0.0825. Anywhere else that is still hosting the file?
Don’t seem to work. The link gets back to this website, which contains only the latest driver. I mean the link that says version 3.0.0.0825. Anywhere else that is still hosting the file?
We are currently working on making a Java Processing wrapper for our new CLEyeMulticam component. This will be included in the next version of the CL-Eye Platform SDK.
As far as the older depreciated versions of the driver, of course we are hosting them all.
Take a look at our downloads archive section here (the Archive link is on the downloads page all the way to the right).
Wow! Thank you AlexP. I have donated (only a little though) to the right cause! I’ll make some attempt to test your driver with some popular motion analysis programs for physics labs and start encouraging other professors to try the PS3 Eye and, donate to your cause of course!
Wow! Thank you AlexP. I have donated (only a little though) to the right cause! I’ll make some attempt to test your driver with some popular motion analysis programs for physics labs and start encouraging other professors to try the PS3 Eye and, donate to your cause of course!
Hey liudr try out the latest SDK build... in it there is a processing library and example application on getting the cameras working with latest Multiple Camera API.
KrisM,
I unstalled the pre-CL version driver, which is able to do 640*480@60 or 320*240@125. I installed the new driver and sdk. Now I only get 640*480@30 or 320*240@60 and a few slower FPS modes. I don’t know what’s happening. I tried virtualdub also and got the same thing.
Now for the sdk: I installed it and tried to run the java/processing example. First the library could not be find. Silly me, I didn’t copy it to the libraries directory. I did that and still nothing. I realized I need to rename the folder to get rid of “library” word and only leave “CLEyeMulticam” as the folder name since the .jar file is CLEyeMulticam.jar not CLEyeMulticamLibrary.jar.
That worked and I started getting unsatisfied link error from not finding CLEyeMulticam.dll so I copy and paste it everywhere I can think of, with processing.exe, inside the library folder, with the sketch, and in windows/system32. Still nothing happens. So I’m stuck. Have you had success running this java/processing lib? Thanks.
I also tried an older CL driver from 12/23. Same thing. Only 640*480@30 or 320*240@60 and a few slower FPS modes. I’m using a windows xp 32-bit tablet version. I’ll try my other system in a moment but it’s not supporting the original AlexP driver with freeze and black screen so I don’t have much hope. Wife has punched in so I’ll grab her laptop for a try too.
Thanks for the feedback, please try this attached update it allows for more precise targeting of the DLL since this will continue to be an issue. For this I added a new public method to the jar which allows user to pass DLL location if not provided it uses SDK default settings.
As for the resolution/framerate there shouldn’t be any issues… I’ll confirm with Alex though.
Thanks and g’luck
Update: Check out our latest SDK. We addressed all of the issues you’re having.
KrisM,
I unstalled the pre-CL version driver, which is able to do 640*480@60 or 320*240@125. I installed the new driver and sdk. Now I only get 640*480@30 or 320*240@60 and a few slower FPS modes. I don’t know what’s happening. I tried virtualdub also and got the same thing.
Now for the sdk: I installed it and tried to run the java/processing example. First the library could not be find. Silly me, I didn’t copy it to the libraries directory. I did that and still nothing. I realized I need to rename the folder to get rid of “library” word and only leave “CLEyeMulticam” as the folder name since the .jar file is CLEyeMulticam.jar not CLEyeMulticamLibrary.jar.
That worked and I started getting unsatisfied link error from not finding CLEyeMulticam.dll so I copy and paste it everywhere I can think of, with processing.exe, inside the library folder, with the sketch, and in windows/system32. Still nothing happens. So I’m stuck. Have you had success running this java/processing lib? Thanks.
I also tried an older CL driver from 12/23. Same thing. Only 640*480@30 or 320*240@60 and a few slower FPS modes. I’m using a windows xp 32-bit tablet version. I’ll try my other system in a moment but it’s not supporting the original AlexP driver with freeze and black screen so I don’t have much hope. Wife has punched in so I’ll grab her laptop for a try too.
Just out of curiosity, is your main system drive not ‘C’? From the CLEyeMulticamLibrary code you can see that first we handle both x86 and x64 system SDK installs, but only under assumption that the system is located on the drive C.
Yes it is on the C drive. I followed your direction “Found XP, plug in cam before continue”. I always get an error saying driver is not properly installed. But the camera works in your test program. On my wife’s vista x86 machine the driver and sdk works just fine but also your program only lists the 640*480@30 or 320*240@60 and a few slower FPS modes. Maybe this is XP-specific? Plus, I’m not used to the double slash as divider between folder names. I tried both \\ and // and didn’t work.
Yes it is on the C drive. I followed your direction “Found XP, plug in cam before continue”. I always get an error saying driver is not properly installed. But the camera works in your test program. On my wife’s vista x86 machine the driver and sdk works just fine but also your program only lists the 640*480@30 or 320*240@60 and a few slower FPS modes. Maybe this is XP-specific? Plus, I’m not used to the double slash as divider between folder names. I tried both \\ and // and didn’t work.
liudr, it looks like you have an older driver that you didn’t remove prior to installing the new CLEye driver. In that case there is a conflict and the new one cannot be installed over the old one. I suspect that this might be way too old driver. What does it show in device manager when you plug in the cam? Could you find ps3eye and take a screenshot and post it here?
As far as ‘//’ double slashes go, with the latest SDK v1.0.1.0101 you don’t have to call ‘loadlibrary’ yourself anymore. It will try to autodetect the apropritate location of the dll, but before this, the CLEye driver must be properly installed and sample multicam apps included in the SDK should properly run. Regarding the slower FPS modes, you are talking about DirectShow camera component and not about new CLEye multicam. The CLEye multicam support all the camera modes and this is the one we wrapped in Java class.
Here is the image. The driver seems to say it’s 12/12/2009 instead of 12/30/2009. I ran the cl eye test program that your driver installs and finds the low fps. The camera driver definitely works in processing. I tried a different camera lib called JMyron and it works. But the lib has no programatical control over FPS or exposure or gain etc.
Here is the image. The driver seems to say it’s 12/12/2009 instead of 12/30/2009. I ran the cl eye test program that your driver installs and finds the low fps. The camera driver definitely works in processing. I tried a different camera lib called JMyron and it works. But the lib has no programatical control over FPS or exposure or gain etc.
Ok good, so the driver works on your XP machine. Now, can you run any precompiled samples from the latest SDK?
The CLEyeMulticamTest.exe runs in 320*240 mode and is fine. The CLEyeMulticamWPFTest crashes every time I run it.
EventType : clr20r3 P1 : cleyemulticamwpftest.exe P2 : 1.0.0.0
P3 : 4b3a2ba1 P4 : cleyemulticamwpftest P5 : 1.0.0.0 P6 : 4b3a2ba1
P7 : 1b P8 : 0 P9 : system.dllnotfoundexception
I’ve tried to put the sdk library dll in a simple folder like c:\downolads and specify its location with the loadLibrary still no go. Will you add a line like System.loadLibrary(“CLEyeLibrary”); in your wrapper? This way at least if the dll is with the code it may get loaded fine. Thanks.
The CLEyeMulticamTest.exe runs in 320*240 mode and is fine. The CLEyeMulticamWPFTest crashes every time I run it.
EventType : clr20r3 P1 : cleyemulticamwpftest.exe P2 : 1.0.0.0
P3 : 4b3a2ba1 P4 : cleyemulticamwpftest P5 : 1.0.0.0 P6 : 4b3a2ba1
P7 : 1b P8 : 0 P9 : system.dllnotfoundexception
I’ve tried to put the sdk library dll in a simple folder like c:\downolads and specify its location with the loadLibrary still no go. Will you add a line like System.loadLibrary(“CLEyeLibrary”); in your wrapper? This way at least if the dll is with the code it may get loaded fine. Thanks.
liudr, the CLEyeMulticamTest.exe should run in both camera modes (640x480 and 320x240, depending on the rng value). If it doesn’t show at 640x480 just exit and run it again.
It seems that you don’t have .NET 3.5 SP1 installed in order to run the WPF test app. That’s ok.
As for Java, you can actually call ‘System.loadLibrary’ from your Processing code and it should load. BTW, the library you are trying to load is not ‘CLEyeLibrary’. It is the ‘CLEyeMulticam.dll’. Just to clarify are you talking about loading CLEyeMulticam.dll or cleyemulticam.jar? What is exactly your error in Processing?
In any case, once you have installed the SDK, there is no need for any of this since the location of the ‘CLEyeMulticam.dll’ will be auto detected and loaded by default for both x86 and x64 Windows systems by the cleyemulticam.jar. Just leave CLEyeMulticam.dll where it is and it should work.
Remember to copy the whole ‘cleyemulticam’ directory (under Java in the SDK) into your Processing ‘libraries’ directory.
I will experiment further with System.loadLibrary and will add that to the next SDK release.
