So instead of buying another webcam I decided to try out the Xbox 360 Kinect stored away in our storage. I successfully paired it to my cMP 5,1 running OSX Mojave and windows 10 in bootcamp. I bought the adapter to connect the kinect to USB from amazon, $12 ("JETEHO 1 Pc Xbox 360 Kinect Sensor USB AV Adapter"). Now with Kinect for Windows Runtime v1.8 installed, the devices that show up when the Kinect is connected are as follows:
Kinect for Windows recognizes the kinect as a camera, this is not what Teams recognizes though
So the camera there is recognized by the computer, but my problem is that when I open MS Teams this does not get recognized as one of the devices. The tricky thing is that MS teams recognized the Kinect as an audio device, but I need it to be recognized as a video device.
MS teams recognized the Kinect as a USB audio device
Kinect as a usb audio device can also be seen in the device manager:
Kinect is recognized as a usb audio device, but I need it to be video as well so I can use it as a webcam in MS Teams
Below is a snip of the MS teams settings not showing the camera as being there: Settings in MS teams showing no camera detected
So, I wanted to know could there be something that I am missing, a driver perhaps of some sort? I have the KinectCam.ax file installed as well and registered, again with no change.
I've tried installing the various SDK's from Microsoft website including v1.8 and v2.0 and even tried installing the most recent runtime from Microsoft for Kinect v2.2 with no avail. The machine still doesn't recognize the kinect as a video or camera device in the device controllers and its driving me bonkers! I have OpenNI virtual cam v0.9.5.0 installed and it recognized the Kinect. The SDKs I've installed also recognize the camera from the Kinect but not MS Teams and that is what I was hoping to use as a webcam device. Any solutions I will try at this point. Also, this website proved somewhat useful, but for some reason I am not getting the same results as them.
https://answers.microsoft.com/en-us/msoffice/forum/all/using-a-kinect-in-teams/3891a30a-2d4e-4d22-8d92-aa7b3ffd779c
GammalSkinka found the solution by using virtual cam for Teams to recognize the device, but I'm not getting the same results as well as cbscript_chris.
working with runtime installed, and w/o sdk, but not for me =(
Again, any help would be greatly appreciated!
Related
I got a Kinect from Xbox 360 and I bought an adaptor to plug it to my laptop. The problem is, I already installed 1.8 SDK and developer tools but when I run Kinect Explorer it says 'kinect sensor required'. So I look the device manager I couldn't find Microsoft Kinect, there's only Generic USB Hub. I tried to use the older version, 1.7, but it makes no different. What should I do to get this Kinect works?
I had the same problem when connected Kinect through an external USB hub. When I plugged it directly into the PC USB port everything was OK.
Can laptop's web camera used in the latest Hololens emulator ?
I'm following this tutorial https://learn.microsoft.com/en-us/windows/mixed-reality/mr-azure-302 to integrate MS Computer Vision API into Hololens.
I want to test this in the Hololens emulator before moving to the device. So, Will I be able to enable Web Cam for recognizing objects using vision API.I'm using Hololens Emulator 10.0 version.
The simple answer is No. HL has own cameras, not compatible with a webcam.
Update. For the case, I would recommend creating video processing library and test it in simple desktop application.
So I've got a few Kinect v2s and am hoping to set up an array of them to get a 3D recording of an area in space (Eventual goal is to build a 360 image from multiple point clouds) But at the moment I can't even get one working on a machine.
I've installed the official SDK onto a windows 10 device and when opening the kinect studio I get nothing but a grey screen when connected to the kinect. Running the kinect configuration verfier says the USB controller is unknown and the system is waiting for the kinect to respond. The kinect itself does not light up, and it's cooling fan does not turn on.
I have reinstalled the SDK, tried 3 different kinects, tried various drivers and troubleshooting guides, and still cannot get anything out of the kinect.
The best answer I've found is that only some controllers are compatible, but every PC I have tried (currently 5 machines) have "Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)" So basically do I really have to get a PCI USB controller or another machine, or is there any way to get the current system to work with the kinect v2 at all.
Also if I do need to buy a new device or PCI card are there any recommended for a setup that would idealy run 4-5 kinects?
Unfortunately, the Kinect V2 prevents you from simultaneously running more than one Kinect on a system:
Sensor Acquisition and Startup
Kinect for Windows supports one sensor, which is called the default sensor. The KinectSensor Class has static members to help configure the Kinect sensor and access sensor data.
Kinect API Overview
A workaround that I've used in the past is to have 1 computer for every Kinect (doesn't have to be fancy, just enough to run it) and then network all the machines together with a router. Designate one machine to be the controlling machine (handles turning on/off of other Kinects). Depending on what you plan on doing to the data, it may be helpful to have those other machines perform some pre-processing and leave the stitching off all the Kinects' feeds up to the controlling machine.
As far as the USB controller goes, I'm running Kinect v2 on that exact one, so other than that malfunctioning, I think you're fine. Have you tried running the "Kinect v2 Configuration Verifier" to see what it suggests? Kinect v2 Configuration Verifier
I use webcam-capture(java api) to get video stream from a usb camera, it work fine.
I want read a usb device descriptor(store some private information), i find out that should install WinUSB or libusbk as a driver to the usb devices. and it test ok, read the descriptor success (by libusb_control_transfer api)
the question is:
befor I install WinUSB, the usb camera is a camera device in the windows device management list. the LibUSB work fail, can't open the usb devices, the error number is -5, means entrypoin not find
after I install WinUSB, libUSB api work ok, but the webcam program can't open the usb devices, it is a universal usb device in the windows device management list.
is there some way the webcam work ok, at the same time, i can read the usb device descriptor use libusb or use other something?
i tested on windows 7 and windows 8, have the same problem.
thanks.
Sadly this is not possible because each of your applications needs a different driver. The only way this can work is if you use libusb and build you own capturing api on top which is quite complicated. As long as webcam-capture can not read the data you want to know about the webcam I am afraid this is not possible.
I'm trying to use the Kinect SDK v1 with an Xbox Kinect sensor. I installed the SDK on my dev machine and I launched the samples. The C# samples do not work, I either get "oops there was an error" or a "NotReady" status and FPS is stuck at -1.
At first I thought this was a problem with the device itself, so I tried installing the SDK on my laptop and the samples work on that fine, both the C# and C++. So the kinect device itself is ok.
I've reinstalled the SDK on my development machine, and I still have the same issues.
Any ideas/solutions?
EDIT: I should note that I have previoulsy developed with this kinect under the 1.0 SDK and when I debug my own app the sensor status enum is still "NotReady"
How is dev machine configuration different from laptop. In the release notes # http://www.microsoft.com/en-us/kinectforwindows/develop/release-notes.aspx it's mentioned that
USB host controller compatibility
The Kinect for Windows drivers have encountered compatibility problems with certain USB host controllers when tested in specific computer configurations. Some examples of these controllers are the AMD Fusion A75 USB2.0 controller, the Etron USB 3.0 Extensible Host Controller, or the Renesas Electronics USB 3.0 Controller. On those controllers, you may encounter a problem, such as a low RGB frame rate, or a Not Ready status when plugging/unplugging a Kinect. These compatibility problems are more likely to occur on PC's running the Windows 8 Developer Preview, or if you plug/unplug multiple devices repeatedly. If this happens to you, you may have to restart your app or reboot your computer. You can also try plugging your device into another USB 2.0 controller.