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
| Camera Model | D435 |
| Firmware Version | 05.11.06.250 |
| Operating System & Version | Win 10 |
| SDK Version | 2.24.0 |
I have converted a recorded bag file to RGB and depth image(PNG format) using rs-converter. Now I want to get the depth values of each pixel directly from the depth image without using the RealsenseD435 device.
I noticed that there is a similar issue posted before. For the code provided(#2200 (comment)), 'cout << frame.at(i,j)[0]<< frame.at(i,j)[1]<< frame.at(i,j)[2]<< endl;' gets three values from the png file.
I am wondering what these three values mean for the depth image. Do I need to do some extra work to get the actual depth value? Do all these three values represent a single pixel?
Looking for your reply.
The text was updated successfully, but these errors were encountered:
If you wanted to get depth data from a saved file, I would be inclined to use the rs-convert tool to convert the bag to .raw format instead of .png. With PNG, depth data will be be lost when the PNG is created, whilst a .raw file preserves the depth information.
| Camera Model | D435 |
| Firmware Version | 05.11.06.250 |
| Operating System & Version | Win 10 |
| SDK Version | 2.24.0 |
I have converted a recorded bag file to RGB and depth image(PNG format) using rs-converter. Now I want to get the depth values of each pixel directly from the depth image without using the RealsenseD435 device.
I noticed that there is a similar issue posted before. For the code provided(#2200 (comment)), 'cout << frame.at(i,j)[0]<< frame.at(i,j)[1]<< frame.at(i,j)[2]<< endl;' gets three values from the png file.
I am wondering what these three values mean for the depth image. Do I need to do some extra work to get the actual depth value? Do all these three values represent a single pixel?
Looking for your reply.
The text was updated successfully, but these errors were encountered: