none
SDK and OpenNI possible conflicts RRS feed

  • General discussion

  • Could there be driver conflicts between using the SDK or the open-source solution from OpenNI?  There's definitely some cool examples out there.  I had my Kinect (XBOX version) running relatively fine a few days ago, and have been playing with trying to install the latest OpenNI SDK tools to be able to try some stuff.

    I've failed to get OpenNI to work, and now it seems I can no longer get any of non-OpenNI stuff to work anymore.

    I wonder if the best bet is to setup a dual-boot and make sure to keep the OS and drivers are completely seperate: OS #1 (Windows 7 SP1 32-bit) has the OpenNI drivers (32-bit seems to be the preference for the OSS projects) and OS install #2 (Windows 7 SP1 64-bit) uses the MS SDK.

    Saturday, February 11, 2012 10:28 PM

All replies

  • Without an SSD I can uninstall one and reinstall the other faster than I can reboot.

    Monday, February 13, 2012 4:17 PM
  • Could there be driver conflicts between using the SDK or the open-source solution from OpenNI?  There's definitely some cool examples out there.  I had my Kinect (XBOX version) running relatively fine a few days ago, and have been playing with trying to install the latest OpenNI SDK tools to be able to try some stuff.

    I've failed to get OpenNI to work, and now it seems I can no longer get any of non-OpenNI stuff to work anymore.

    I wonder if the best bet is to setup a dual-boot and make sure to keep the OS and drivers are completely seperate: OS #1 (Windows 7 SP1 32-bit) has the OpenNI drivers (32-bit seems to be the preference for the OSS projects) and OS install #2 (Windows 7 SP1 64-bit) uses the MS SDK.

    To be perfectly honest, that sounds like an enormous level of overkill to get your non-OpenNI stuff working again.

    I'd just uninstall and reinstall the drivers each time I wanted to switch between the two. But if you can't be bothered, why not try virtual box instead of dual booting? https://www.virtualbox.org/

    However, I do suppose that this is (essentially) the same level of work as dual booting. Oh well...

    Other than that, I'm not aware of any other, 'quick' and relatively easy and pain free method of driver switching. I suppose if you were using virtual box, you may want to be running a PC with specs a bit over the recommended specs if you want to maintain 30fps as you'd be (essentially) emulating windows.

    Alternatively, you could always use openNI in linux. I mean that's why a lot of developers use openNI, due to its ability to be used cross platform and I mean linux is a pretty light weight operating system, to the point where you can use it on a flash drive or CD (though obviously that's not the smartest idea if you want to use openNI and you'd want to have an installed copy of linux...).

    Tuesday, February 14, 2012 1:31 PM
  • Hello;

    I am facing a similar problem. I went the VMWare root and I have a windows 32 running only visual studio 2010 and Openni drivers. One of my friends told me I could using Norton to optimise my boot up and using I could disable the Kinect or Openni drivers from loading depending on which one to use. This would also require to reboot. I am still for using a virtual machine.

    Regards

    Shivam

    Tuesday, April 24, 2012 9:23 AM