Sony Ps3 Eye Cl-eye-driver-4.0.2.1017.exe - fasrwb. At the 'Intel Chipset Driver' ver. 9.4.0.1017' screen, click 'Next'. At the 'License Agreement' dialog, read the agreement, then, if you agree, click 'I Agree'. Sony Ps3 Eye Cl-eye-driver-4.0.2.1017.exe - fasrwb. The PS3 Eye camera has a USB vendor id of 1415 and a USB product id of 2000. To allow direct libusb access without root permissions on a Debian linux variant (e.g. Ubuntu, Raspbian, etc) add a new udev rule for your cameras by creating a new file.
| Active 10 Meter USB Extension CableThe ideal USB extension cable with active USB capability for excellent camera attenuation. |
| Air Mouse-Air KeyBoard Combo2.4GHz wireless with nano-USB receiver. Air mouse with Vibration technology built-in. QWERTY keyboard to speed through set up and chats. Support multiple platforms. Remote control especially designed for Android based devices like TV Box and other Android systems that have an USB port. Includes rechargeable Li-Ion Battery. |
| Calibration MaglightSony PS3 Eye cameras require calibration using a Maglight Mini with Candle function. These items have the appropriate lumens and intensity to effectively allow for system calibration when using Sony PS3 Eye cameras. |
| Extended Warranty / Technical Support |
| Removable Sony PS3 Eye Mounting Base AdhesiveSemi-Permanent attachment for the Sony PS3 Eye camera - has bottom side adhesive which allows secure attachment to almost any flat surface. Easy removable with no damage to the surface or the camera base. Attaches to the base of the camera with semi-permanent , but removable adhesive. |
| Sony PS3 Eye CameraSony PS3 Eye web cam - ideal for iPiSoft MoCap |
| Sony PS3 Eye Camera Set of 1010 Sony PS3 Eye web cams - ideal for iPiSoft MoCap |
| Sony PS3 Eye Camera Set of 22 Sony PS3 Eye web cams - ideal for iPiSoft MoCap |
| Sony PS3 Eye Camera Set of 44 Sony PS3 Eye web cams - ideal for iPiSoft MoCap |
| Sony PS3 Eye Camera Set of 64 Sony PS3 Eye web cams - ideal for iPiSoft MoCap |
| Sony PS3 Eye Camera Set of 88 Sony PS3 Eye web cams - ideal for iPiSoft MoCap |
| Universal Sony Eye or Kinect Wall MountCustom wall mount adapter for both the Sony PS3 Eye Cameras and / or the Microsoft Kinect sensor. Can be combined with the optional tripod and tripod adapter to make a complete universal solution. |
| Universal Sony PS3 Eye and/or Kinect Mounting Base AdapterSony PS3 Eye camera bottom side base matching adapter with universal camera threads to allow for secure attachment to standard tripods. Attaches with semi-permanent adhesive, included. |
Thanks for answer. I was aware of 4-channel image. My testing
implementation now works with following conclusions:
a) Idea of
int[] img_data; // PS3 camera frame, RGB, 4-channel
reorder_channels(img_data);
IplImage img = IplImage.create(imageWidth, imageHeight, IPL_DEPTH_8U,
4);
frame_buffer = new java.jni.ByteBuffer().wrap(.......);
frame_buffer.asIntBuffer().put(img_data);
img.imageData(new BytePointer(frame_buffer));
is not feasible because RGB --> BRG conversion is needed. I did not
find RGB channels reordering to show “normal color” image. Image was
shown but colors were always corrupted.
Ps3 Eye Driver Windows 7
b) Current solution/performance issues (based on my current
knowledge):
- I have to go through “int[] img_data; // PS3 camera frame, 4-
channel” pixel by pixel and create another array “byte[] ipl_data” in
3-channel BRG format
- every such ipl_data frame have to be set to image by calling
img.imageData(new BytePointer(ByteBuffer.wrap(ipl_data)));
as a side effect content of ipl_data is copied into internally
allocated buffer of the image
- javacpp.BytePointer/java.jni.ByteBuffer implementation (see
constructor of BytePointer) does not allow “wrapping” of IplImage
around user accessible image data buffer because of side effect
mentioned above
- BytePointer/ByteBuffer implementation does not allow getting of
address of the existing IplImage internal data buffer. (Eg.
ByteBuffer.hasArray() returns null.)
Ps Eye Driver
To put thinks another way: image data needs to be copied twice before
the IplImage is created. There is no bulk copy and 'for' cycle element-
by-element needs to by used. That is not very efficient for low level
image grabber.
My knowledge of all these subtle details of low level implementation
is rather limited and I can see couple of pros in separating
structure data. But from the performance perspective it is limiting.
Any suggestions, thoughts, ideas?
Regards,
Playstation Eye Driver
Jiri