The RealSense SDK in the '2016 R3' version currently supports theF200 and SR300 cameras, with R200 support having ended at the previous '2016 R2'. The only option available for using the ZR300 in Windows 10 is through running the open-source Librealsense SDK in Windows.
As the R200 is the camera with the closest hardware design to that of the ZR300's, I would think that if it were possible to persuade the RealSense SDK to talk to a ZR300 then the '2016 R2' SDK with its R200 support would be the best SDK to work with when exploring that goal.
There are no plans (that I am aware of) to add ZR300 support to the RealSense SDK. Given the roughly six month update cycles that previous RealSense SDKs have followed, I would speculate that it is possible that a new iteration of the SDK will be coming soon if that timeline is continuing, but unfortunately i have no knowledge about that.
I only read somewhere that Intel product sheet saying zr300 only supported in Linux, there are not even windows installer for the camera. So how did you get it working? My windows 10 did install all drivers of zr300 for me automatically, however, seems the Depth Camera Manager is not installed.
Basically for the ZR300 you have two choices:
1. Librealsense, which can run in Windows as well as Linux (though Linux is the easier to get it working with, I believe;
2. The RealSense SDK For Linux, which I believe installs Librealsense as part of its package of Linux modules.
The R200 and SR300 can work with Windows, according to Librealsense users, but they have Windows drivers available for them).
Intel's FAQ on Librealsense says "Librealsense is a cross-platform capture driver (Linux, Mac OSX, Windows) for the Intel RealSense Camera F200, SR300, R200, and ZR300" This implies Windows support for the ZR300 in Librealsense. However, the minimum specification sheet for the ZR300 says it only supports use with Ubuntu. So 'Linux only' is likely the correct answer for the ZR300, sadly.
1 of 1 people found this helpful
I used librealsense (see GitHub), compiled the vc14 solution and all the demo projects worked like a champion :-). Given that the RealSense SDK appears to be dead for all purposes (i.e. not supporting windows or any current cameras) that means the DotNet wrappers are also dead. So if you doing stuff in C#/JS/VB/Unity/Java(ha!) then best you look at CppSharp or Swig (horror).
The other forms of RealSense camera that support Windows (R200 and SR300) are in stock in Intel's online store, and the RealSense range is continuing with forthcoming new products such as the RealSense 400 (double the trackable depth points and operating range). I understand though the difficulties that the absence of Windows support causes for developers who want to use that OS. Given Intel's prior Windows support for the other cameras, it is possible that there is a technology in the ZR300 particularly (e.g SLAM) that has been problematic to produce Windows drivers for, rather than a deliberate snub of Windows users.
So have you got all the functions promised by librealsense in windows 10 here:
- Native streams: depth, color, infrared and fisheye.
- Synthetic streams: rectified images, depth aligned to color and vice versa, etc.
- Intrinsic/extrinsic calibration information.
- Majority of hardware-specific functionality for individual camera generations (UVC XU controls).
- Multi-camera capture across heterogeneous camera architectures (e.g. mix R200 and F200 in same application)
- Motion-tracking sensors acquisition (ZR300 only)
My setup of ubuntu for zr300 seems broken as it showed only one rgb camera streaming and quit working 10 seconds after. dmesg show the bad magic number blablabla...
This camera seem to be rushed to the market and is driving users crazy busy troubleshooting. The other day i read an article complaining about we as developer spent majority of our time configure the hardware system other than writing codes for a scenerio.