The Sony PS3 Eye Camera functions as a video chatting interface, with a 120 frames-per-second camera that delivers sharp images and video. The zoom lens of the camera. Join our community just now to flow with the file CL-Eye-Driver-5.1.0520 and make our shared file collection even more complete and exciting Sony Ps3 Eye.

Hi Samuel,

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

IplImage img = IplImage.create(imageWidth, imageHeight, IPL_DEPTH_8U,
4);

reorder_channels(img_data);

Playstation Eye Driver

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.

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.)

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.

Ps Eye Driver

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,

Ps3 Eye Driver Windows 7

Jiri