I'm doing a project on Hand Gesture Recognition , I installed OpenCV on my system it works fine except for sample programs related to camera like bgfg_segm, camshiftdemo etc . When I run these programs I get a window asking me to select the Video Source type from Integrated camera or FA VirtualCam(Fast Acces Software for Facial Recognition,Dell) . When I select Integrated cam light does not even glow whereas when I choose FA VirtualCam Cam switches on but it does not capture any image its just dark.
Using same setup I installed in my friend's laptop -Lenovo/WinXP it worked.
My camera works fine otherwise, no problem with it. I tried uninstalling and reinstalling and all possible combination but it didn't work.
Configuration: Dell Studio 1558
Ram: 4GB,
OS: Windows 7 Home Premium x64
OpenCV version 2.2
Software for camera: Dell WebCam Central.
There's an workaround for that, it worked for me.
You just have to capture the webcam using Processing and redirect it to OpenCV.
I explain it with more details at the Processing forum.
My source code is available at my page .
It appears that your camera is not compatible with OpenCV, see http://opencv.willowgarage.com/wiki/Welcome/OS
I have the exact same issue on a Vaio laptop using OpenCV (light comes on but a blank image). I managed to use processing/jmyron to get the functionality I needed (face detection).
Related
I am trying to use Kinect (the oldest one, the very first one released by Windows) and connect it to Matlab R2013b in a Windows 10 running laptop.
I've already followed the suggested steps and installed the Matlab Support package called "Kinect for Windows Runtime". This is supposed to instal the drivers needed to run the kinect on windows too.
enter image description here
However, as I use the command "imaqhwinfo", I get a warning saying that kinect is either not supported or no powered and this output:
AdaptorDllVersion: '8.2 (R2013b)'
AdaptorName: 'kinect'
DeviceIDs: {1x0 cell}
DeviceInfo: [1x0 struct]
I'd really appreciate if anyone could tell me what the error is or, tell me the configuration you used if you were able to use matlab and kinect.
Thank you in advance
Part 1 - Description of the problem
I have the DK2 and I am working on a VR project. This project uses FirefoxNightly. I've downloaded it and installed the WebVR Enabler Add-On
Got this from http://mozvr.com/downloads/
I have also downloaded and installed the latest SDK and Runtime for Windows from https://developer.oculus.com/downloads/
I am also getting this on the Oculus Configuration Utility (while the oculus is plugged in):
However, I have gone on another computer with windows.. installed everything just like on this windows computer and it clearly shows the Oculus Rift connected properly but the head tracking still not working.
EDIT: I just tried connecting the oculus rift to this "second" pc ( dell laptop ) and now it doesn't even recognize the oculus rift. Still no head tracking.
EDIT 2: I tried installing everything on a third PC without success. I'm getting "service unavailable" on the Oculus Configuration Utility
My display mode is set as shown in the image.
Part 2 - Questions
What am I doing wrong? Is there a step I forgot to do? The weird thing is, I have the same project running on Mac without having any problems. Yes, on windows I can see the screen through the oculus rift but head detection is just not present.
Part 3 - list of possible fixes that did not work
This reddit post talks about the firewall issue however I tried the oculus rift with the firewall disactivated without success.
This reddit post talks about a possible fix by reinstalling everything and updating certain drivers.. however I have followed this fix step by step without success.
This oculus forum post talks about the issue and one person proposes a fix that worked for him/her. I followed the fix without success.
Part 4 - System info
If you require specific translations let me know. It is in French.
Part 5 - List of things I have tried that have been thought of
I have reinstalled everything. SDK (is not even needed in fact), runtime, firefoxnightly, webvr add-on multiple times
I have rebooted my computer multiple times
I have tried the different Rift Display Mode
Basic demos from mozvr.com and other webvr based projects work fine but head tracking does not work.
My Oculus is not broken (maybe for windows), it works fine for the Mac.
I've tried using different HDMI cables and Different minUSB-USB cables without success.
Part 6 - Quotes from the forum
First post
This sounds like the same issue a lot of us are having with the 0.5
and 0.6 versions. It's not something wrong with the cables, but with
the Runtime itself. Direct-mode works flawlessly and in Extended mode
the rift still displays a picture, altho without any tracking etc from
the runtime. Hoping it'll be fixed in the next update.
I've seen head tracking break in Firefox Nightly sometimes but I can usually solve it by restarting the browser once or twice, assuming that the hardware and Oculus side of things is working correctly.
Today, most games made for the Oculus Rift are based on specific versions of the Oculus Rift. I found this GUI desktop application that seems to solve most of those problems.
The idea is to install all Oculus Rift Runtime versions and then use the GUI to switch between each version.
The link above is to a reddit post that talks about how to install the application and the different runtimes.
You must install the runtimes from oldest to newest otherwise you'll run into some difficulties, like I unfortunately did. If I'm not mistaken runtime version 0.8 is very buggy and I never really got it to work.
Good luck.
This is what I did to get the Oculus DK2 working on my Windows 10 Laptop:
Create a windows restore point before you start this.
Download oculus_runtime_rev_1_sdk_0.4.4_win.exe from the Oculus downloads page.
Run the installer. Do not restart your computer when prompted.
Go to C:\Program Files (x86)\Oculus\Service folder, right click on OVRServer_x86.exe and go to properties.
In the compatibility tab, check Windows 8 mode, and Run As Administrator.
Run OVRServer_x86.exe
That's it.
The Good News
You should now be able to run direct to rift games. The HELIX rollercoaster app works well. So does the 6000 Moons demo. Most others do not. Depending on the game, you may need to go to your windows display settings, and fiddle with the screen resolution and rotation of the Oculus display.
The Bad News
Your computer may not restart. When I did the above, and later restarted, the computer hung on the windows loading page. I had to go into advanced start mode and load a system restore point. Definitely not the best user experience, but at least I got something working.
I wonder why every once in a while, Intel RealSense 3D camera fails to start? I have re-installed the drivers and SDK as well as the DCM but still it is whacky and very unpredictable. Any idea what the source of the problem could be? It should be able to run the examples in the SDK in a normal working situation.
Well, previously that it couldn't init problem was that only two of the its drivers could be recognized (not the virtual driver) like the following but now all of its driver are recognized and still it can't init.
so I am receiving an init failed message when running the SDK examples.
Any pointer for fixing is really appreciated.
If you are also showing an integrated webcam (other than the 3 RealSense listings), try disabling that so the RS camera can be seen as the primary.
Actually you can select the device you want to run the sample on in the menu "Device". If you installed the RealSense correctly and if the latest DCM is running (the current version is 1.4 if I remember), you should be able to select the RealSense device there and then run the sample.
Sometimes the DCM Service fails to start (e.g. if you force-restarted your machine recently). Then you just need to make the service restart and it should work.
Hope this helps.
I’m also facing the same problem (on windows 10), and found a way that solved it for me: search “Scanners and Cameras” in Control Panel, choose “Add Device”, under “Manufacturer” choose “Intel” and under “Model” choose “Intel(R) RealSense(TM) Camera SR300 Virtual Driver” or the version you use, and continue to install.
Have you installed the right drivers? There are two versions of the real sense cameras. The Windows 10 works with Intel Real Sense R3 which has completely different architecture than its predecessor.
i recently brought kinect sensor. As per system requirement i purchase desktop . Now followed installation mentioned bellow link. I also downloaded verification link. when check installation it giving me below error. let me know how to sort it out
i already tried reinstal directx 11 download from Microsoft & restarted computer. but i found in device manager only one part is detected. kinect sensor information not avilable.
please let me know what wrong i am doing here
install link
kinect verifier link
You need to buy a faster GPU that supports DX11.
According to:
http://www.game-debate.com/hardware/?gid=326&graphics=GeForce%20210%201GB
http://www.tomshardware.co.uk/answers/id-2297019/play-directx-supported-games-geforce-210.html
your Geforce 210 only supports up to DX 10.1, as is also shown in
your first screenshot as Direct3d API version.
I am using Kinect for Windows (not for XBOX) on Apple iMac 3GHz 4GB 10.8.3. The Kinect is connected with USB cable to iMac and with power supply.
Software: I have installed XCode, XQuartz, MaxPorts, CMake, then libtool, libusb, OpenNI SDK v1.5.4.0, SensorKinect, and NiTE v1.5.2.21.
I am running Processing 2.0.8 with SimpleOpenNI 0.27 library.
Any example from SimpleOpenNI runs, but after approximatly 20sec Kinect stops working and freezes.
(I need to say that the green led is blinking constantly but Kinect is still working, since at least for short period time I can get e.g. the depth image etc.)
Any ideas why is not working constantly? Maybe I need Kinect for Xbox in the end? Is there any power supply issues with Apple computer? (I have tested the same Kinect device on PC and it worked fine)
This is a bit late, but for others finding this problem that I also found, try installing OpenKinect within Processing and running one of the sample sketches (like Average Point Tracking) for a moment, closing, then trying your Simple OpenNI sketch. I'm also using .27 (because I couldn't get later versions to work) and this fixes the problem, but you have to do it every time you plug the camera back in or restart the OS. Hope this helps someone else.