LE13 Testing for RK3288, RK3328, RK3399, RK3566, RK3568, RK3576, RK3588

    I finally had some time to test the LE 13 nightly on one of my RK3588 device and I think it is a really good client now even playing more difficult streams than some other devices. Would it be possible to build ffmpeg with libx264 and libx2645 support or are they still too slow?

    Martin

    Quote from emveepee

    Would it be possible to build ffmpeg with libx264 and libx265 support or are they still too slow?

    The ffmpegx add-on provides an ffmpeg binary wth h264 support (not sure about h265). Hardware encoding is still some way off as the kernel is still missing a defined uAPI for V4L2 encoding so there's a choreographed dance between kernel, specs, and userspace apps like gstreamer and ffmpeg to pull off.

    Quote from chewitt

    The ffmpegx add-on provides an ffmpeg binary wth h264 support (not sure about h265). Hardware encoding is still some way off as the kernel is still missing a defined uAPI for V4L2 encoding so there's a choreographed dance between kernel, specs, and userspace apps like gstreamer and ffmpeg to pull off.

    Service.nextpvr installs ffmpeg-tools and I tried to find ffmpegx and couldn't. I installed TVH too but couldn't find it in .Kodi. How do I find it?

    I did try to use -f v4l and thought it was my lack of understanding causing the missing ioctl messages.

    Quote from emveepee

    Service.nextpvr installs ffmpeg-tools and I tried to find ffmpegx and couldn't. I installed TVH too but couldn't find it in .Kodi. How do I find it?

    I did try to use -f v4l and thought it was my lack of understanding causing the missing ioctl messages.

    The ffmpegx built binary is .kodi/addons/tools.ffmpeg-tools/bin/ffmpeg

    That is what I tried

    orange:~ # /storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg -hide_banner -decoders | grep 264
    VFS..D h264                 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
    V..... h264_v4l2m2m         V4L2 mem2mem H.264 decoder wrapper (codec h264)
    orange:~ # /storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg -hide_banner -encoders | grep 264
    V..... h264_v4l2m2m         V4L2 mem2mem H.264 encoder wrapper (codec h264)

    Cleaning up I found an old Vontar KK RK3566 box that I forgot about and searched and found a random-ish link that has a working Armbian 22.4 (but I didn't put it on the LAN) While it boots I see a firefly bootloader and it says station-m2 but the "official" m2 Armbian doesn't load

    Is there anything in this Armbian that might help identify what is needed to boot or build this on LE? Here is dmesg

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
    if it helps

    Code
    Machine model: Rockchip RK3566 BOX DEMO V10 ANDROID Board

    I'm not sure if this ^ is the same as the evalation (evb) boards present in u-boot/kernel, but if I was building an image to experiment from that would be my starting point. That said, device-tree changes/improvements to RK boards in the kernel seem to be made on a very individual basis (no bulk enablements etc.) so you may also find the evb files need some fixups; they are inherently often the first board to be added for each SoC type, and then development focus quickly switches to commercially available boards, so the evb boards fall behind current driver capabilities over time.

    The historic process I've used with Amlogic hardware is to experiement with all the different device-tree files and see which one gives the best (or least-worst) outcome, then fork that to a board-specific dts that I can develop on.