I see that you are using the following (EXO) player: https://github.com/google/ExoPlayer
I see that you are trying to use the HW codec for H264. In Android, I use also the SW codec with the option: --encoder OMX.google.h264.encoder This email is just to make the context much cleaner, and understandable... To YOCTO primes. And, yes, It is interesting to me as well. How to include rpi4 HW coders into the context? ;-) NOT only for rpi4 silicon... ;-)) Thank you all, Zee _______ On Fri, Oct 21, 2022 at 10:56 AM Ed Watson <[email protected]> wrote: > > I want to increase the performance streaming from a rpi4 via an rtsp streamer. > > I am using ffmpeg to do the encoding however it is using CPU encoding. > > What is the right options for using the hardware in 264 encoding? > I assume it is -c:v h264_omx > > That is not compiled it. > > I added to ffmpeg_%.bbappend > > PACKAGECONFIG += " omx omx-rpi " > > > > PACKAGECONFIG[omx] = "--enable-omx" > > PACKAGECONFIG[omi-rpi] = "--enable-omx-rpi" > > > > DEPENDS =+ "virtual/libomxil" > > RDEPENDS_${PN} = "${VIRTUAL-RUNTIME_libomxil}" > > I get the error. > > ERROR: OMX_Core.h not found > > > > Am I braking up the wrong tree here? > > Thanks > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58391): https://lists.yoctoproject.org/g/yocto/message/58391 Mute This Topic: https://lists.yoctoproject.org/mt/94472166/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
