-
Notifications
You must be signed in to change notification settings - Fork 176
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
Noetic support, segfault #71
Comments
Any news on this? Noetic support would be highly appreciated, because we ROS1'ler will stick with it for some time... ;-) |
GStreamer 1.16 (default on Ubuntu 20.04) will cause a segfault. Fix: #61 |
You can use the |
If the images you receive from gstreamer are already in the right format (e.g., |
Can you post your pipeline here? As I said earlier you need to convert h264 to raw using |
That looks right to me. You'll also want to add a caps-filter after the videoconvert to tell that node what format to convert to, e.g.: The bytearrays you'll get in this appsink will then just be plain-old RGB frames that you can publish.
That has nothing to do with gstreamer anymore, just publishing messages on ROS topics, so the very basic ROS tutorial should be all you need: http://wiki.ros.org/ROS/Tutorials/WritingPublisherSubscriber%28c%2B%2B%29#roscpp_tutorials.2FTutorials.2FWritingPublisherSubscriber.Writing_the_Publisher_Node |
Is there any support planned for noetic? Compiling from source under ubuntu 20.04 is easy enough and works out of the box. But when running it the node segfaults right away after sending a first image.
The text was updated successfully, but these errors were encountered: