You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, We use advanced mode in pyrealsense2 to load exported settings json from the viewer and compare the depth images from the viewer and pyrealsense2, we find out that they are not the same. ( We check the cpp files of sdk and found that librealsense does not set all settings exposed in the viewer). We tried even to use visual preset in pyrealsense2 and postprocessing but still depth images from the viewer are not the same from pyrealsense2. The viewer depth images are much better in quality. How to use the settings from the viewer properly in pyrealsense2 to get the same depth quality (at least visually for us)?
Secondly, We tried to use advanced mode in pyrealsense2 to load exported settings json for different cameras, but it only sets the settings for first device properly and ignore the rest of devices. we use advanced mode in pyrealsense2. How to use advanced mode in pyrealsense2 for multi-camera?
The text was updated successfully, but these errors were encountered:
Hi @HasanFarag The RealSense Viewer applies a range of post-processing and colorization settings by default. When creating your own application, such as a Python script, these settings are not included by default and must be deliberately programmed into the application.
If you have already replicated the post-processing filters that are enabled by default in the Viewer, you could check that you have fully replicated the Viewer's default color scheme and histogram equalization settings. #7767 (comment) and #7089 (comment) provide Python scripting resources for configuring the color scheme and histogram on / off status.
A RealSense team member in #6075 (comment) describes how enabling histogram equalization provides a "nice rainbow of colors", so if histogram is disabled by default in your Python application then this may account for some of the difference between your Viewer and Python images.
In regard to applying settings for individual cameras, you could set up a separate pipeline for each camera with that camera's unique serial number, and configure an individual set of cfg instructions for each pipeline. An example of a Python script for doing this can be found in #1735 (comment)
Issue Description
Firstly, We use advanced mode in pyrealsense2 to load exported settings json from the viewer and compare the depth images from the viewer and pyrealsense2, we find out that they are not the same. ( We check the cpp files of sdk and found that librealsense does not set all settings exposed in the viewer). We tried even to use visual preset in pyrealsense2 and postprocessing but still depth images from the viewer are not the same from pyrealsense2. The viewer depth images are much better in quality. How to use the settings from the viewer properly in pyrealsense2 to get the same depth quality (at least visually for us)?
Secondly, We tried to use advanced mode in pyrealsense2 to load exported settings json for different cameras, but it only sets the settings for first device properly and ignore the rest of devices. we use advanced mode in pyrealsense2. How to use advanced mode in pyrealsense2 for multi-camera?
The text was updated successfully, but these errors were encountered: