Modified PS3EyeDriver (from Eugene Zatepyakin) compiled with 圆4 profile (I created a separate static lib from his work that we can use in our OpenCV projects). WinUSB kernel driver (installed with Zadig utility, the WinUSB kernel driver is provided by Microsoft) You must connect the PS3Eye to your machine and then install one of the generic kernel drivers. Here is the link for the installer: If you don't trust it, you can try this one. The real generic driver can be installed separately. No worry about the libusb thingy because there is a open source installer that will do it for you. Considering that I don’t think this will even provide direct OBS support due to lack of DirectShow drivers (not sure about this though), I don’t want to take that risk unless someone already did this successfully. However, they seem to require Libusb for Windows for which I’ve read many threads saying that it disabled the user’s USB ports. I’ve read reports from Linux users who use different (and free) drivers: There are SDK and “professional” packages available, but their multi-cam support is only theoretical and by no means out-of-the-box. However, they only support one camera at a time. Unfortunately, so far using two or more PS3 Eyes is only possible in Linux. However, nowadays multiple cams are the standard, with one or even two for the players and an additional one for the commentators. Then right click on the PS3EyeInstaller project in the solution explorer and click build.The Sony Playstation Eye camera is only 10$ and by far the cheapest camera that does 480p60 with decent / good quality, so it’s very attractive to streamers. To build the installer, first build the 32 and 64 bit release configurations of the solution. If the DLL was built with a debug configuration it's possible to use WinDBG to set a breakpoint in the filter code which will be hit when using the camera with any DirectShow application. Use c:\windows\system32\regsvr32.exe /u to unregister the filter. If you have run the installer make sure to uninstall the package before doing this. If you would like to make the compiled DirectShow filters available to other applications, run c:\windows\system32\regsvr32.exe from an administrator command prompt. Next open PS3EyeDriverMSVC.sln and build the desired configs again. Build the solution with all desired configurations. If you don't have the Windows 8.1 SDK, change the SDK target to Windows 10 in all of the libusb project properties. Open libusb/msvc/libusb_2017.sln in Visual Studio 2017. There isn't any need to provide a custom DirectShow or WMF source for a native camera. Also Windows will automatically make those cameras available via the DirectShow API (both 32 and 64 bit) as well as Windows Media Foundation. On the other hand native camera drivers have slightly better performance.
![driver for ps3 eye camera driver for ps3 eye camera](https://i.ytimg.com/vi/k8Y7TLYvWes/maxresdefault.jpg)
It provides a generic way for user space programs to communicate with the device.Īnother big advantage of a user space driver is it's much easier to directly make use of other libraries such as libusb and the github project that this driver is based on. The part that runs in kernel space is the WinUSB driver and it's a stable component provided by Microsoft. This means any flaws in this driver will only affect the program that's using the camera instead of crashing the entire operating system. The biggest advantage is all of the code runs in user space instead of kernel space.
![driver for ps3 eye camera driver for ps3 eye camera](http://1.bp.blogspot.com/-BXb8EbvEWY0/UVtoo52nGaI/AAAAAAAAMfU/9k4bzASz6i8/s320/Driver+1+PC+Game.png)
![driver for ps3 eye camera driver for ps3 eye camera](https://i.ytimg.com/vi/4relCfvhgQQ/maxresdefault.jpg)
This has several advantages and disadvantages compared to a native camera driver. This project makes use of the generic WinUSB driver to communicate with the camera.