https://www.kernel.org/doc/html/latest/ ... m2mem.html
https://www.kernel.org/doc/html/latest/ ... coder.html for the encoder API documentation.
Looking at https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/v4l2_m2m_enc.c#L214, I see the profile being set, but not the level.
I did recently fix the kernel driver so that it passed in the frame rate correctly when requested for libcamera, and that may be what it tripping you up now. FFmpeg is telling the codec the framerate, but not the level.
Trying to set the H264 level before running FFmpeg will therefore not be a persistent setting that will apply to the later instance.Memory-to-memory devices function as a shared resource: you can open the video node multiple times, each application setting up their own properties that are local to the file handle, and each can use it independently from the others.
https://www.kernel.org/doc/html/latest/ ... coder.html for the encoder API documentation.
Looking at https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/v4l2_m2m_enc.c#L214, I see the profile being set, but not the level.
I did recently fix the kernel driver so that it passed in the frame rate correctly when requested for libcamera, and that may be what it tripping you up now. FFmpeg is telling the codec the framerate, but not the level.
Statistics: Posted by 6by9 — Fri Aug 30, 2024 3:12 pm