Endianness of Depth Raw Data from "Save snapshot" Button

[apoorva-sriv]

Required Info
Camera Model	D415
Firmware Version	05.09.14.00
Operating System & Version	Win 10
Platform	PC
SDK Version	2.13.0

Issue Description

Hi, I have an issue with the endianness of depth raw data obtained from the "Save snapshot" button of RealSense Viewer. Reading it as little endian gives the correct depth values for each pixel but doesn't display correctly, and vice versa for big endian.

Little endian gives the correct depth value (499 mm) but displays the image incorrectly (with colormap jet):

Big endian displays the image correctly but gives the wrong depth value (6221 mm >> 499 mm!):

RealSense Viewer snapshot png:

If I read a frame from a bag file recorded in RealSense Viewer, little endian also displays correctly (with the correct depth values), and big endian is the same (displays correctly but wrong depth values). So, this seems to be an issue with the "Save snapshot" button only.

[ev-mp]

Hello @apoorva2398 ,
What tools do you use to display the raw data that you get from "Save snapshot"?
In case you're using PNG renderer/interpreter to parse _file_name_.raw blob, then it will not work as PNG by design assumes that the binary data is ordered as big endianness.

The raw format saves the depth stream in its native format, as transmitted over UVC. The depth format definition can be obtained from linux documentation

Please check #815 for additional info.