Kinect for Windows version 2, problem with Depth Data RRS feed

  • General discussion

  • Recently i purchase a new kinect for windows (V2). i need to capture depth data. therefore i installed SDK 2 for this reason. i captured depth data with Depth D2D or WPF in SDK 2. but i see the depth data that kinect captured,is very different from real depth. also we can see that many depth data will change suddenly into a random value of pixel(something like above 238, 140 or 3). And we also find that many black and white pixel appear on the display which also means that there exists an extreme sudden change between zero and a great value.
    What makes this happen and how can I correct it


    Saturday, February 28, 2015 6:48 AM

All replies

  • Depth is generated based on the time of flight infrared(IR) data that is acquired from the sensor. Time of flight is different from structured light sensor than v1. In a particular frame, each pixel is going to have a valid depth value or unknown. The only way to correct is to average the data acquire from the SDK. Each frame can be compared to the previous given a constant that the camera didn't move. Based on that each pixel can be averaged with previous frames(more than one) and that should level off to a point.

    Since this is all based on IR data, the reflective properties of the surfaces/environment will determine the amount of noise. With time of flight, the ir data is actively filtered to only look for the wavelengths the sensor has emitted into the area. If you are highly reflective areas(lots of glass, mirrors, shiny metal, amount of direct sunlight) that is going to affect how the IR gets bounced back into the sensor. This also applies to materials that absorb IR.

    The only things you can do is determine how the IR data looks using IR basics and if you are seeing a lot of pure black and bright white that is going to affect what depth can be detected in those areas.

    Carmine Sirignano - MSFT

    Monday, March 2, 2015 7:36 PM