Intel® RealSense™ Cross Platform API
Intel Realsense Cross-platform API
|
Note: Due to the USB 3.0 translation layer between native hardware and virtual machine, the librealsense team does not recommend or support installation in a VM.
librealsense shall be built on Windows using CMake and Visual Studio 2015 / 2017: (MSVC2013 and older are not fully compatible with the C++11 feature-set).
![link text][Win_cmake_image]
Don't forget to check BUILD_EXAMPLES
if you wish to use librealsense samples.
When working on Windows 8.1, make sure you have KB3075872 and KB2919355 installed. These patches are addressing issues specific to 8.1 video drivers, that were later resolved in Windows 10.
Metadata attributes is an advanced capability provided by librealsense. Read more on this feature in ./frame_metadata.md "link". Follow the instructions to enable metadata generation:
Prerequisites:
winver
command from desktop/terminal - "Version 1607" or later is expected. Powershell
tool as *_Admin_* and navigate to the script directoryPS > .\realsense_metadata_win10.ps1 <optional:operation>
The supported parameters are-op install
adds registry keys for connected Intel Realsense devices-op install_all
adds keys for all RealSense devices logged in the registry-op remove
removes registry keys for connected Intel Realsense devices-op remove_all
removes the keys for all RealSense devices logged in the registry Running the script without arguments will is similar to -op install
operation.... cannot be loaded because running scripts is disabled on this system
message, run: `PS > Set-ExecutionPolicy RemoteSigned` , answer `Y` and then rerun the script **Important** - The registry keys are device-unique. Therefore, __*the script must be executed each time a new RealSense device is attached*__ to the PC.
In case the script cannot be executed due to permissions, or other Host-related issue please follow the instructions to update the registry manually:
Intel® RealSense™ Camera SR300 Depth
(Step 1)Find device's path (Step 2) and the additional interfaces (Step 3)
Modifying the Windows Registry:
HKLM\SYSTEM\CurrentControlSet\Control\DeviceClasses\{e5323777-f976-4f5b-9b55-b94699c46e44}
branch.Device instance path
obtained from the previous step#GLOBAL
-> Device Parameters
DWORD 32bit
value named MetadataBufferSizeInKB0
with value 5.DWORD 32bit
value named MetadataBufferSizeInKB1
with value 5 for RS400 device zero interface ##?##USB#VID_8086&PID... **MI_00**..
HKLM\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}
branchRepeat the procedure for all the additional RealSense devices (e.g. Intel® RealSense™ Camera SR300 RGB
)
During compilation the library will automatically detect and enable/disable metadata functionality according to the WinSDK version selected. In case the installed WinSDK doesn't expose metadata the user will be notified that the build does not include metadata generation: Librealsense notification: Featuring UVC Metadata requires WinSDK 10.0.10586.0 toolset. The library will be compiled without the metadata support!
In order to ensure compilation with metadata support check the ENFORCE_METADATA
in the Cmake configuration stage. When set, the compiler will check the target WinSDK version, and abort the build if it is not compatible with metadata requirements.
Note In case of multiple WinSDK version installed, CMake automatically selects the latest version of SDK. In some cases, however, the automatic selection may fail. Then you need to manually retarget the solution for the proper WinSDK version: