Content-Length: 233130 | pFad | http://github.com/NVIDIA-ISAAC-ROS/isaac_ros_image_pipeline/issues/46

94 Unable to use Mono8 streams? · Issue #46 · NVIDIA-ISAAC-ROS/isaac_ros_image_pipeline · GitHub
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

Unable to use Mono8 streams? #46

Open
aatb-ch opened this issue Apr 30, 2024 · 5 comments
Open

Unable to use Mono8 streams? #46

aatb-ch opened this issue Apr 30, 2024 · 5 comments

Comments

@aatb-ch
Copy link

aatb-ch commented Apr 30, 2024

I have an Oak-D Pro W camera with mono left/right and rgb central imagers. For performances reasons I want to do all rectification on a Jetson Orin Nano, instead of partly on-camera via their DepthAI SDK. The mono streams are encoded as mono8 and the color as bgr8.

I have tried using the RectifyNode, it works fine with the color topic, which is encoded bgr8, but the mono topics crash the node with an invalid input data type error. Inspecting the sources it seems that the RectifyNode only wants color input streams, so I looked into the ImageFormatConverterNode to first convert my mono8 as bgr8 but it seems to expect only rgb8 as input and allow to pick only the output formats.

So I am left wondering, is there any way to use Isaac Image Pipeline nodes to preprocess my stereo mono8 stream for rectification and then feed it to visual slam node? I'm sure I can do that with a non-accelerated package, but I loose then the advantage of CUDA and Nitros.. I'm also a bit surprised since mono imagers are a pretty common thing? I know that the "ideal" pipeline should make use of Argus and then it will output directly NV12 or NV24 streams, but since Isaac Visual Slam takes in mono8 rectified images it would make sense to have the upstream pipeline also supporting that format?

@naitiknakrani-eic
Copy link

We have the similar issue with 16UC1 depth data coming from ToF. we can rectify it with non-accelerated ros image pipeline but not with Isaac_ros_image_pipeline.

More image encoding support are coming in upcoming release ?

@anshu3012
Copy link

@aatb-ch @naitiknakrani-eic Was there any resolution/workarounds for this except using non-accelerated packages?

@aatb-ch
Copy link
Author

aatb-ch commented Nov 4, 2024

hey, no i left things aside, had too many issues with other parts of the project and waited for Jetpack 6 release, have to revisit the project.

@anshu3012
Copy link

Thanks for the update!

@r4hul77
Copy link

r4hul77 commented Jan 14, 2025

@anshu3012 or @aatb-ch, I'm having a similar issue here was anyone able to find a workaround for this ?

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

No branches or pull requests

4 participants








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/NVIDIA-ISAAC-ROS/isaac_ros_image_pipeline/issues/46

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy