-
Notifications
You must be signed in to change notification settings - Fork 16
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
Changing the input streamer or file path to ros2 node publisher #2
Comments
Abbreviation of the question above, what should i change in the deepstream pipeline flow, in order to replace the input stream with a ros topic subscriber which receives frame by frame images (using Image msg converted by cv2 in python |
Hi! This project currently supports video input through webcam/file. Converting ROS to OpenCV images will not give you the latency optimizations that the underlying DeepStream pipeline provides. Could you please tell us what you want to achieve using CvBridge? If interested in accessing image data, you could try using deepstream-imagedata-multistream. You could also try using RTSP input with your DeepStream application; refer to deepstream-rtsp-in-rtsp-out. |
Thanks @AsawareeBhide for your response!
So what should be a good practice to convert DDS/ROS messages to a deepstream input? |
Hey there, |
Any approach? Very interesting to move some ai to models to ROS using real-time cameras on board robot |
Hey all, and thank you for this incredible project!
I would like to know what are the changes that need to be done in order to convert the input of the node from camera/mp4 file path to a topic of a node that publisher bag file of frames.
which class should be changed or what kind of topic should I use? or other modifications I should take in consider.
best regrades,
AK
The text was updated successfully, but these errors were encountered: