-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kinect 1414 (AKA Old) for 360, do not work #526
Comments
What kind of host computer? What is the output of |
On a related note I can say that I recently started playing with libfreenect with a Kinect 1414 and also had a similar sounding issue with no depth/video capture but still able to change the tilt and led etc. I was getting lots of URB size mismatch warnings from the kernel in my case running with the generic ArchLinux 4.13.0 kernel. At some point I rebuilt a minimal vanilla 4.13.0 kernel since I was preparing to dig in to figure out really what was broken but luckily for me things started to work on that minimal kernel build. Since it's working for me now I haven't had cause to delve deeper but I assume now there's a particular module that's causing a conflict. I did try unloading+blacklisting the gspca kinect driver as a seemingly likely candidate but that didn't seem to be the culprit for me. |
I have the same issue. Kinect 1414. Running Ubuntu 17.10, tried both X and Wayland. I used to run this Kinect with the Faro software until a Windows upgrade a few months ago, so I know it's a working device. freenect-camtest gives me lsusb |
I am having problems with the 1414 xbox 360 device also. Depth is working good, but for the rgb video I get, maybe a frame every minute. I have the kernel driver blacklisted on debian testing(buster). Here is the start of camtest. freenect-camtest |
I'm facing like this lost packets with my Kinect 1414, ros kinetic . Is there any other solutions/driver to work with 1414? |
it seems i ran into the same problem when trying to switch to py3. i compiled HEAD and while the debian packages i had before worked fine (v0.5.3) HEAD did not but showed
I checked which version introduced this behaviour and found 4696c80 to be the commit to blame. the version before (it is 873a2cc) worked fine. it seems the 4696c80 ("Add notices about Kinect v2 Fixes #485", 2016-10-23) broke it with the given behaviour. maybe someone can confirm? (even if its years ago when noticed ;) ) |
I also have this problem, kinect 1414, on windows 10
sometimes freenect_process_events() throws an error and communication stops. And only tilt, led and accelerometer works, no video callback or buffer data received |
I tried using the library, everything else works, I am able to change the led, change tilt, but the video feed is not showing up at all. It shows invalid magic.
So I opened it up, and disconnected the IR projector and then tried running the example, no I am able to get the raw camera feed without problem, but as the ir projector is not connected, depth sensing do not work. Connecting the IR projector back, again gives me the same error. No more stream, but sometimes, i do get depth image, but that only for a second and then it freezes. Can anyone help me out?
The text was updated successfully, but these errors were encountered: