Skip to content

Fix raw_mjpeg passthrough for compressed image publishing - #378

Open
DipFlip wants to merge 1 commit into
ros-drivers:mainfrom
DipFlip:raw-mjpeg-passthrough
Open

Fix raw_mjpeg passthrough for compressed image publishing#378
DipFlip wants to merge 1 commit into
ros-drivers:mainfrom
DipFlip:raw-mjpeg-passthrough

Conversation

@DipFlip

@DipFlip DipFlip commented Oct 8, 2025

Copy link
Copy Markdown

Change pixel format check from 'mjpeg' to 'raw_mjpeg' to enable direct MJPEG passthrough to compressed topic without decode/re-encode.

This allows the driver to publish raw MJPEG data directly on the /image_raw/compressed topic, avoiding unnecessary CPU usage from decoding to YUV and re-encoding to JPEG.

Fixes: #346

Change pixel format check from 'mjpeg' to 'raw_mjpeg' to enable
direct MJPEG passthrough to compressed topic without decode/re-encode.

This allows the driver to publish raw MJPEG data directly on the
/image_raw/compressed topic, avoiding unnecessary CPU usage from
decoding to YUV and re-encoding to JPEG.

Fixes: ros-drivers#346
@DipFlip

DipFlip commented Oct 8, 2025

Copy link
Copy Markdown
Author

To be honest here I just read the issue thread and tried the suggested replacement from @wendwosenbb. I'm not sure what it does or breaks. It's similar to the now closed #336 but doing only three replacements fixed the compressed image feed for me.

@isaac-ahlgren

Copy link
Copy Markdown

Why is this not merged into main yet? I was running into the same issues and this branch fixed it entirely.

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.

Unable to Publish raw mjpeg stream directly via compressed image topic

2 participants