(You also have H264 encode available through all the above paths, and the same restrictions apply to each).ĭo you know what Kodi currently uses on the RPi 4? Is this a purely MMAL backend, or are they using the V4L2 wrapper?
#Purchase mpeg 2 and vc1 codec license keys 64 Bit#
IL will not be supported on 64 bit kernels, and does not support dmabufs. You can use dmabufs with it via vcsm, but it requires a bit of fiddling around. MMAL has support for 64bit, but there's an issue that still needs chasing down. It also supports handling dmabufs for efficient passing of buffers between subystems. HEVC decode on the Pi4 is through a separate block that is driven by the Linux kernel. GStreamer likewise has components for V4L2 decode as v4l2h264dec, etc. mpeg2_mmal mpeg2 (mmal) (codec mpeg2video) It also has a client implementation for MMAL mpeg4_v4l2m2m V4L2 mem2mem MPEG4 decoder wrapper (codec mpeg4) mpeg2_v4l2m2m V4L2 mem2mem MPEG2 decoder wrapper (codec mpeg2video) h264_v4l2m2m V4L2 mem2mem H.264 decoder wrapper (codec h264) h263_v4l2m2m V4L2 mem2mem H.263 decoder wrapper (codec h263) This should appear as /dev/video10 on our downstream kernel builds.įFmpeg has a client implementation for V4L2 M2M There is a wrapper above MMAL that implements the V4L2 M2M stateful decoder API. The block for H264 etc can only be accessed via the VPU firmware, which means either MMAL or IL. Pi4 has the same hardware accelerated decode for H264, but not the other codecs. Pi0-3 have hardware accelerated decode for H264, MPEG4, H263, and through optional codec licences for MPEG2 and VC1.