List of Cameras This is a database of USB webcams and cameras. There are 825 cameras in this database. Currently, 463 of these cameras work on Mac OS X. Now 404 of these cameras are supported using the macam driver! Another 18 cameras work with OEM supplied drivers.

43 cameras are supported using the USB Video Class (UVC) built-in driver found in Mac OS X 10.4.3 and later. Please report any additions or changes to this data! Click on the colum headers to re-sort (except Notes). Click on a model name for more specific details. Note that some models might have multiple separately listed variants. Notes Philips works SAA8116HL 3Com works ViCAM AEL (Multi-Cam International) works STV680 AEL (Multi-Cam International) works STV680 AEL (Multi-Cam International) works STV680 Aiptek works STV680 Aiptek works STV680 Aiptek works STV680 Aiptek works STV680 Aiptek works STV680 Aiptek works STV680 Aiptek works STV680 Aiptek works STV680 Ariston works CPiA Creative Labs works CPiA Creative Labs works OV511 Digicom works CPiA Digital Dream works STV680 Dolphin Peripherals works STV680 Intel works 0x0733 0x0430 SPCA505A Intel works CPiA Kensington works????

The Download Center provides a selection of Vimicro PC Camera drivers for download. Since different PC Camera manufacturers design their products differently.

Apologies for the rudimentary nature of this post, I fear there may be a few of these incoming, but: The camera fails to be detected by any capture software, including: Creative's own Live Central 3, Google Hangouts, RealSense's own capture tools and tracking software. Environment: Windows 8.1 (fully updated), Intel i5 3570k processor, USB3.0 connection.

Installed RSSDK, and Audio Update driver. Firmware upgrade installer fails to detect the camera. Running the tutorial app correctly lists the installed SDK modules, and the sdk_info.exe viewer shows the camera virtual driver, the depth camera manager service as RUNNING, and all other relevant modules installed properly as far as I can determine.

Windows device manager sees that the audio component and the camera virtual driver are connected, and importantly, the audio control panel shows that the camera's microphone is receiving input! Fake Drivers Licence Uk on this page. Might anyone have any ideas as to why the device would be apparently successfully connected but fail to initialize the camera component?

This may have answered a question I have been asking. You have a 3rd generation processor and the specifications state that a 4th generation processor is required. I have been asking if the camera will correctly initialise on a 3rd gen, albeit with limited functionality. I am currently using the SDK on a 3rd gen processor with voice recognition and emotion detection. So the SDK is able to kickstart itself, but can the camera? My camera should be arriving within the next couple of days, I will run a similar test. I have an i7-3517 on Win 8.1 (fully up to date) + USB 3.

I received my camera today, and I've run through the SDK examples. Firstly though - plugging in the camera. I put it in the first USB port of 4.

In Device Manager I could see the Realsense camera driver. When I ran the demos, it didn't appear, although in the voice recognition demo, I could see the camera as an audio device. Sure enough, it was listed under audio devices in Device Manager. I unplugged and put in port 2 - the same result. Next, port 3 and voila, I get 3 devices: • 3D Camera Front Depth • 3D Camera Front RGB • 3D Camera Virtual Driver.