-
Notifications
You must be signed in to change notification settings - Fork 608
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
[ROS2] symbol lookup error when starting usb_cam_node_exe #214
Comments
Hey @flynneva, thanks for the response. I tested the new version and indeed no more error regarding libavcodec occurs. However, I can now only get my camera working with the pixel format yuyv and not with mjpeg or h264. My camera supports yuyv and mjpeg on /dev/video0:
and H.264 on /dev/video2:
When I start the usb_cam_node_exe with default settings, it creates the yuyv stream on /dev/video0 just fine and it also display the possible pixel formats:
However, when i switch to using pixel format mjpeg and color format yuv420p the node just closes without an error:
The same happens when i try to use H.264 on /dev/video2:
Is there an issue with my configuration or my device? |
@greinet you might have to test out different color formats that are compatible with the pixel format you chose. I am not sure what exactly your error is and it is hard for me to debug remotely. |
@greinet fyi MJPEG is now supported on the 👍🏼 |
Hey,
I get the following error when running the executable:
I am building the current
ros2
branch locally with ROS2 Foxy on a NVIDIA Orin (aarch64/arm64 architecture).As I used this library before, I tried going back in commits to find where the issue first started. This commit was the first one that started to fail with a similar error:
My understanding is, that it does not recognize the method
av_image_alloc
in line 111 of that commit.I also listed my installed libavcodec version, resulting in 58 as far as i can tell, which should provide the wanted method i guess:
I guess this might be related to #203. What libavcodec versions are currently supported and what can i do to get this package running on my setup?
The text was updated successfully, but these errors were encountered: