Skip to content
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

default to encoding in the image message #921

Merged
merged 1 commit into from
Jan 31, 2024

Conversation

mikeferguson
Copy link
Member

My camera is publishing rgb8 encoding - the existing code throws an error that 8UC3 is not a valid encoding, but if we pass rgb8 from the message then things work fine. The encoding in the image should always be more descriptive than just the bit and channel size.

If encoding is not filled in, the existing behavior is used as a fallback

@mikeferguson mikeferguson requested a review from ahcorde January 31, 2024 21:39
@mikeferguson mikeferguson merged commit 9b2468d into ros-perception:rolling Jan 31, 2024
3 checks passed
@mikeferguson mikeferguson deleted the encoding_fix branch January 31, 2024 22:20
Kotochleb pushed a commit to Kotochleb/image_pipeline that referenced this pull request May 27, 2024
My camera is publishing rgb8 encoding - the existing code throws an
error that 8UC3 is not a valid encoding, but if we pass rgb8 from the
message then things work fine. The encoding in the image should always
be more descriptive than just the bit and channel size.

If encoding is not filled in, the existing behavior is used as a
fallback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants