AlexP from the nuigroup forums has got the Sony PS3 Eye working under windows. If you are looking for a cheaper alternative to 1394 Cams like FireflyMVs or Unibrain, you can try this one out. However, it still does not work with any OF apps but it does work in Windows Apps like MSN and Skype and even Amcap.
I tried changing the code as you suggested but still no luck.
Btw, I am running VS2005.
Here is the error in Debug mode:
A protection error dialog pops up with the following:
Debugger detected - please close it down and restart!
Windows NT users: Please note that having the WinIce/SoftIce service installed means that you are running a debugger!
Here is the error in Release mode:
***** VIDEOINPUT LIBRARY - 0.1991 - TFW07 *****
SETUP: Setting up device 0
SETUP: PS3Eye Camera
SETUP: Checking crossbar
SETUP: You are a webcam or snazzy firewire cam! No Crossbar needed
SETUP: Setting capture size to 320 by 240
SETUP: Media Type is RGB24 no conversion needed
SETUP: Capture callback set
ERROR: Could not connect pins - RenderStream()
SETUP: Disconnecting device 0
SETUP: freeing Grabber Callback
SETUP: freeing Renderer
SETUP: freeing Capture Source
SETUP: freeing Grabber Filter
SETUP: freeing Grabber
SETUP: freeing Control
SETUP: freeing Media Type
SETUP: removing filter NullRenderer...
SETUP: filter removed NullRenderer
SETUP: removing filter PS3Eye Camera...
SETUP: filter removed PS3Eye Camera
SETUP: freeing Capture Graph
SETUP: freeing Main Graph
SETUP: Device 0 disconnected and freed
error allocating a video device
please check your camera with AMCAP or other software
When i deleted VI_COMPOSITE and recompiled, it still works. Now all my other apps work without me having to recompile.[/quote]
Ahh yeah I think the driver remembers what the last setting was so once you set it to Composite once it will remember the next time you use it.
Would be curious to see what the settings panel of the PS3 EYE looks like.
If you call the ofVideoGrabber videoSettings(); command it should pop up a box of options to control the camera params.
Progen is this working now? Let me know what I would need to do so I can recompile tbeta so it works with the ps3 eye. Also, did you get it working at the high fps?
I think he added a property sheet dialog box, although the videoInput library doesn’t seem to integrate these property sheets for setting res, fps, colorspace like dsvideolib does. I’m hoping in the next version of OF we have ability to set camera resolution AND fps or have access to something like a property sheet so we can access all camera settings. With Alex’s driver, the ps3 eye on windows is really the best camera for the money.
I’m also wondering, since OF doesn’t let you set fps of the camera directly, if the PS3 eye will default to the last used FPS (n amcap or other) or if it’ll go to highest fps (320 x 240 = 150fps or 640 x 480 = 75fps).
Yes, the PS3 now works with all my OF apps. You just need to recompile the ofVideoGrabber with the necessary changes. However, you need to note that it does not work in debug mode. Theo mentioned that it could be something with the Directshow filters for the PS3 Eye. So might have to ask AlexP about this.
Setting FPS - well it has been requested a lot now for videoInput!!
I think it is time to bite the bullet - next videoInput release will let you specify framerate. Not sure about adjusting it on the fly but you will be able to specify a desired framerate in the setup command. Not sure how that will integrate with ofVideoGrabber though as that would be windows only functionality for now - though a quicktime and possibly a v4l/unicap solution might exist also.
unicap can set things like brightness, fps, gamma, automode… by code (indeed any property you can set from ucview). So if you decide to integrate that with the videoGrabber, the linux version can be done too.
Theo, I don’t think there’s a need to adjust FPS on the fly, only to be able to set it on init. Many cameras don’t allow you to set their fps once they initialize. So although we have access to videoSetting, most of these just adjust image quality (brightness, contrast, etc) but don’t let you set resolution, frame rate, colorspace. The philips SPC900nc is an exception to this, it lets you change fps after it starts in the videoSettings. But, generally we have to set that before the camera starts which is why it’s so important. I could say more why we need this feature, but I don’t want to hijack this thread heh. Hopefully eventually we can get a FPS setting for all platforms.
@ Progen, that’s not good news I’ll PM Alex and point him to this thread. I wonder what he changed between the version you had working and the current one.
Should we look into using his PS3lib and SDK instead or should the directshow one work the same you think?
[quote author=“cerupcat”]@ Theo and arturo, that is great news!
Theo, I don’t think there’s a need to adjust FPS on the fly, only to be able to set it on init. Many cameras don’t allow you to set their fps once they initialize. So although we have access to videoSetting, most of these just adjust image quality (brightness, contrast, etc) but don’t let you set resolution, frame rate, colorspace. The philips SPC900nc is an exception to this, it lets you change fps after it starts in the videoSettings. But, generally we have to set that before the camera starts which is why it’s so important. I could say more why we need this feature, but I don’t want to hijack this thread heh. Hopefully eventually we can get a FPS setting for all platforms.
@ Progen, that’s not good news I’ll PM Alex and point him to this thread. I wonder what he changed between the version you had working and the current one.
Should we look into using his PS3lib and SDK instead or should the directshow one work the same you think?[/quote]
cerupcat, it is the best if you can use the PS3Eye SDK since it provides minimal latency and the best performance. You will see much improvements in both performance and stability if you run it under Vista as opposed to XP. This especially applies when running at high frame rates.
I will look into DirectShow filter issue. It is a major pain to write DS video source filter since there is not much info about this process out there…
I’ll PM Alex and point him to this thread. I wonder what he changed between the version you had working and the current one.