berndpfrommer
commented
6 months ago Not sure what's going wrong here. You can try setting the parameters with something like this in your launch file:
parameters=[{
'ffmpeg_image_transport.encoding': 'hevc_nvenc',
'ffmpeg_image_transport.profile': 'main',
'ffmpeg_image_transport.preset': 'll',
'ffmpeg_image_transport.gop': 15,
}]but I doubt it'll make much of a difference. The parameters appear to be set correctly, the plugin is logging, so it's installed and found as well.
For some reason when the node is started through the launch file, the ffmpeg library it's using there cannot find the hevc_nvenc encoder, whereas when you run from the command line, it can find it. I suspect it has to do with the difference in launch environments.
Try this: use strace -f <your command here> >& /tmp/foo.txt to run from the command line and to run with the launch file. This will produce a huge amount of output since strace logs every system call. Now search the foo.txt file for anything related to ffmpeg_image_transport, libav and other interesting stuff. You may be able to see where it opens nvenc related stuff (successful run). You should also see what version of libavcodec (aka ffmpeg) is being used. Does it come from the same location? Compare the output from the two runs. What are the differences? Does libavcodec open the same files in both cases?
PierreInnodura
tonynajjar
Hello,
I try to republish a image topic with this package on a Jeston Orin AGX.
Everything works well in command line:
But when trying to do the same with a launch file it fails and gives this output:
My launch file:
Everything works fine with libx264, but when trying to set hw accelerated encoder it fails.
Could you help me on this topic ?
Thank you.