1

I've been developing with kinect XBOX 360 for a while. Today, after connecting a different kinect device (XBOX 360) i've started getting an error on the initalization line:

 kinect.Initialize(RuntimeOptions.UseSkeletalTracking | RuntimeOptions.UseDepthAndPlayerIndex | RuntimeOptions.UseColor);

The error I was getting:

Failed in native DLL. HRESULT=0x8004022b.

and the stack trace showed:

at Microsoft.Research.Kinect.Nui.SkeletonEngine..ctor(Runtime mainNui, CINuiInstanceHelper nuiInstance)

I've already tried :

  1. Reinstalling all kinect related drivers and restarting.
  2. Switching back to the old kinect sensor I was using.
  3. Reinstalling the kinect sdk (the version i'm using is : Microsoft Kinect 1.0 Beta2 SDK v.1.0.0.45
  4. The following link - http://social.msdn.microsoft.com/Forums/en-US/kinectsdk/thread/5b9ffac3-86c0-4147-a6c7-f8e4bbc73c56 - talks about finding the registry key but I couldn't understand how to do it.
  5. According to this link - http://msdn.microsoft.com/en-us/library/ms919477.aspx this is an error code:

    VFW_E_SAMPLE_REJECTED This sample cannot be rendered. 0x8004022B 555

is there a way I could use it to solve the problem?

I'm running win7 64 bit.

warren
  • 32,620
  • 21
  • 85
  • 124
oded
  • 11
  • 1
  • 3

4 Answers4

2

Try using the Kinect for Windows SDK 1.5. It's been out for a couple of weeks now.

The API should mostly be the same as in 1.0 beta, but you will have to change the names of some namespaces when using them.

Also, you will still be able to use the Kinect for Xbox360 for development purposes, unless you want to use near mode for depth acquisition.

Chris Ortner
  • 806
  • 6
  • 11
2

Like Chris Ortner said, you should switch to the full version as it is much more efficient. You can find it here. If you are fearing that you must convert all of your code, look here and here. If you are worried about converting code like getDisplayPosition, see Converting Kinect Methods from Beta 2, to Version 1. If you need any more help converting, just ask! Hope this helps!

Community
  • 1
  • 1
Liam McInroy
  • 4,339
  • 5
  • 32
  • 53
2

I had this error. It was nothing to do with drivers or versions.

The Kinect sensor uses a lot of the USB bandwidth, so it is essential to have it on its own USB controller. Try the different USB ports until it works. You can use the Device Manager to see which devices are on which controllers: View > Devices by connection.

tim_hutton
  • 838
  • 9
  • 9
0

Thanks a lot for your help.

I prefer not to change to kinect for windows to timelines. I was able to solve this issue thanks to this link which worked like a charm. The steps to resolve this issue were: 1.Uninstall all kinect drivers from all the USB ports. 2.Uninstall the kinect sdk. 3.Reinstall the Kinect SDK. 4.Disabled network adapter. 5.Plug in the kinect sensor.

The idea is to reinstall all the drivers and prevent it from obtaining drivers from Windows Update.

I appreciate your help.

Thanks, Oded

oded
  • 11
  • 1
  • 3
  • Just a note, the new SDK works much better and has more features (liked [seated mode](http://msdn.microsoft.com/en-us/library/microsoft.kinect.skeletontrackingmode.aspx)), I was scared of converting too, but it ends up helping a lot – Liam McInroy Jun 13 '12 at 19:14