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.
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.
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!
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'm trying to connect a usb sensor (see Toradex) to an android phone (Desire Z) running android 4.0.3.
To test this, I wrote a small app to enumerate the attached device(s).
This supposed to have USB HOST mode implemented and to power the usb sensor (HID)... but it doesn't.
I got a USB OTG cable and now, when I attach the cable, a small icon appears in the status bar (car mode).
I'm disappointed since I waited for this feature for awhile now...
Any thoughts? I read almost everything out there related to this (Sven work and whatnot) but I might have missed something...
Thanks!
I have worked a lot in the past year and a half to build custom android platform. Some was under Froyo but mostly on Gingerbread. Most on the hardware I added was on either a UART or on USB, which is what you want to do. Unfortunately, it is not as easy to add a USB peripheral on an Android device than on a PC or a MAC. PCs and MACs have virtually unlimited memory space (hard drive). They can hold the drivers of a very large number of devices. That makes it possible to do auto-detection and automatic loading of drivers. On an Android device, it is a lot more lean therefor, just the required drivers are stored on the device. Every time I added a new device, I had to compile the driver for my platform and make some modification in my configuration. It is also possible to load the driver as a module instead of compiling it with the kernel (gives a file.ko output). Although, the driver must have been written accordingly. But, you will have to install it by modifying the "init.rc" which requires root privilege.
here is a few link of question/answer about about drivers in Android. That should give you a little bit more info:
USB touchscreen driver
Hope it helps but unfortunately, it is quiet a lot of work do do.
I'd like to use digital cameras in my application (running on Windows, written in C++) and I came across two libraries that did that - WIA (Windows Image Acquisition) and WPD (Windows Portable Devices). WIA supports digital cameras only for versions of Windows up to XP and for Vista and 7 one should use WPD. The problem is that I ran WPD's sample project from Windows SDK which failed to recognize all devices I tried (But WIA did on a Win XP machine) apart from a flash memory and an mp3 player. I don't think the other devices were too old to have a WPD driver, so my question is: What devices does WPD support? Am I mistaken or WPD does not work with a broad range of devices? Or maybe there is another library I could use for taking pictures (maybe a video, but that's not as important)?
I hope someone can clear things up. Thanks in advance!
You will need to use DirectShow to work with your webcams on Vista/Win 7. Logitech and the like don't supply WPD drivers. Perhaps they will for Windows 8.
You can also use the MCI interface if you want to go old school, which nowadays is just a compatibility layer on top of DirectShow. Google for "WM_CAP_START" or "WM_CAP_GRAB_FRAME" for some examples.
Don't have a list for WPD, but here's a:
List of Supported Windows Image Acquisition (WIA) Scanners and Cameras
http://support.microsoft.com/kb/264598