{"id":45294,"date":"2018-11-29T14:43:25","date_gmt":"2018-11-29T21:43:25","guid":{"rendered":"https:\/\/www.realsenseai.com\/uncategorized-cn\/openni2-for-intel-realsense-sdk\/"},"modified":"2026-03-19T15:59:12","modified_gmt":"2026-03-19T21:59:12","slug":"openni2-for-intel-realsense-sdk","status":"publish","type":"post","link":"https:\/\/www.realsenseai.com\/cn\/news-insights-cn\/openni2-for-intel-realsense-sdk\/","title":{"rendered":"RealSense\u2122 SDK 2.0 and OpenNI2\u00ae"},"content":{"rendered":"\n
\n\nAs a developer, it\u2019s always challenging to pick which hardware makes the most sense to invest your time and money in \u2013 will that hardware still be available when your product comes to market? Is it future proof? How can you ensure that your project won\u2019t require a major rewrite every time you change hardware, especially when it comes to more unique or niche categories of hardware like depth cameras? Depth cameras are widely used in a variety of industries, but this technology continues to evolve and new devices hit the market regularly. A solution to the above problems is to use a common framework with a common structure that provides all the basic tools to work with different depth cameras. This is the problem solved by OpenNI2\u00ae.\n\nWhile OpenNI has stopped support for its OpenNI2 product, since this framework was designed to provide everything necessary for long use, it is still in demand and still useful to developers. For anyone who has been using OpenNI2 for their projects, RealSense\u2122 Depth Cameras now offer OpenNI2 support<\/a>.\n

Features of OpenNI2<\/h3>\nUsing RealSense\u2122 Depth cameras with OpenNI2, you retain all the advantages of the device, such as maximum range of distance, depth accuracy, frame-resolution and frame-rate of sensors. Using it in new projects will allow you to create a product that supports multiple different devices and thus, users.\nThe OpenNI library provides a general framework for working with various depth cameras using the following classes:\n