-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Depth Image Encoding 16UC1 => mono16 #77
Comments
I don't think there is. Does it cause any problem for you ? If it does, would you mind trying to change 16UC1 to mono16 and see if it works fine ? |
Indeed I was trying to use image_saver from image_view to convert images in rosbag to png files. and it has the error. |
And, there is also an issue when I try to rectify the depth image by image_proc. the error I get is:
|
@hwp did you try to change the format in Naoqi Driver directly? |
@hwp can you tell which rosbag file has to be edited for making changes from 16UC1 to mono16? |
I am currently encountering the same problem, has there been a fix yet, or should I open up a new issue with more details? |
@nlyubova no I did't do that. Although I think the naoqi driver should use the format suggested by REP 118. However, I don't know if changing the format will cause a lot of other problems. |
@JanhviK I did the recording without changing naoqi_driver, and then I modified the rosbag that I recorded. |
@frederikscholz I haven't used depth images for a while. I don't know if it has been fixed. |
The depth image encoding in naoqi_driver is
16UC1
rather thanmono16
. Is there any reason to do this?As I understand the cv_bridge does not recognize
16UC1
. From time to time, I get error messages like:The text was updated successfully, but these errors were encountered: