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
and similar are present in the camera driver part. The only little-endian thing is the 16UC1 depth image (which is correct as protobufs are always little).
Is there some reason for the single-byte values to be marked as big endian? If I understand it correctly, this has nothing to do with BGR/RGB as that is one level higher than endianness...
The text was updated successfully, but these errors were encountered:
I don't know much about how ROS makes use of the endianness values when processing/publishing, but I suppose this might be because some things wouldn't work correctly if the endianness is left on its default of false?
Perhaps it's something to try removing and seeing if the images are still output as expected in rviz or other image viewers.
I've tested it with both the mono images from body cameras and with the RGB camera from arm. Nothing changed in the look of the images as viewed by image_view, rqt_image_view, rviz or rqt_bag.
spot_ros/spot_driver/src/spot_driver/ros_helpers.py
Lines 150 to 154 in bb82c29
and similar are present in the camera driver part. The only little-endian thing is the 16UC1 depth image (which is correct as protobufs are always little).
Is there some reason for the single-byte values to be marked as big endian? If I understand it correctly, this has nothing to do with BGR/RGB as that is one level higher than endianness...
The text was updated successfully, but these errors were encountered: