amazingfate

I think they are the same: ``` $ ls -l /usr/lib/aarch64-linux-gnu/libEGL* lrwxrwxrwx 1 root root 20 2月 28 21:59 /usr/lib/aarch64-linux-gnu/libEGL_mesa.so.0 -> libEGL_mesa.so.0.0.0 -rw-r--r-- 1 root root 292072 2月 28 21:59 /usr/lib/aarch64-linux-gnu/libEGL_mesa.so.0.0.0 lrwxrwxrwx 1 root root 11 1月 4 2022 /usr/lib/aarch64-linux-gnu/libEGL.so -> libEGL.so.1 lrwxrwxrwx 1 root root 15 1月 4 2022 /usr/lib/aarch64-linux-gnu/libEGL.so.1 -> libEGL.so.1.1.0 -rw-r--r-- 1 root root 68040 1月 4 2022 /usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0 $ ls -l /usr/lib/aarch64-linux-gnu/libGLESv* lrwxrwxrwx 1 root root 17 1月 4 2022 /usr/lib/aarch64-linux-gnu/libGLESv1_CM.so -> libGLESv1_CM.so.1 lrwxrwxrwx 1 root root 21 1月 4 2022 /usr/lib/aarch64-linux-gnu/libGLESv1_CM.so.1 -> libGLESv1_CM.so.1.2.0 -rw-r--r-- 1 root root 141408 1月 4 2022 /usr/lib/aarch64-linux-gnu/libGLESv1_CM.so.1.2.0 lrwxrwxrwx 1 root root 14 1月 4 2022 /usr/lib/aarch64-linux-gnu/libGLESv2.so -> libGLESv2.so.2 lrwxrwxrwx 1 root root 18 1月 4 2022 /usr/lib/aarch64-linux-gnu/libGLESv2.so.2 -> libGLESv2.so.2.1.0 -rw-r--r-- 1 root root 149600 1月 4 2022 /usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0 $ ls -l /usr/lib/aarch64-linux-gnu/libmali-x11/ total 42740 lrwxrwxrwx 1 root root 36 2月 19 01:02 libEGL.so -> libmali-valhall-g610-g6p0-x11-gbm.so lrwxrwxrwx 1 root root 36 2月 19 01:02 libEGL.so.1 -> libmali-valhall-g610-g6p0-x11-gbm.so lrwxrwxrwx 1 root root 36 2月 19 01:02 libgbm.so.1 -> libmali-valhall-g610-g6p0-x11-gbm.so lrwxrwxrwx 1 root root 36 2月 19 01:02 libGLESv2.so -> libmali-valhall-g610-g6p0-x11-gbm.so lrwxrwxrwx 1 root root 36 2月 19 01:02 libGLESv2.so.2 -> libmali-valhall-g610-g6p0-x11-gbm.so -rw-r--r-- 1 root root 43763352 2月 19 01:02 libmali-valhall-g610-g6p0-x11-gbm.so lrwxrwxrwx 1 root root 36 2月 19 01:02 libOpenCL.so.1 -> libmali-valhall-g610-g6p0-x11-gbm.so ```

@roykI never use ozone args. I just use egl: $ cat /etc/chromium-browser/default # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser # Options to pass to chromium-browser CHROMIUM_FLAGS="--use-gl=egl"

@roykI just tried your video https://www.demolandia.net/4k-video-test/hdr10/page-1.html and reproduced this issue. This video has a drm format which is not supported by kernel. Chromium works on gnome wayland. Moonlight-enbedded does not work because of kernel update, you can use moonlight-qt instead.

@roykkodi log shows that you are using egl instead of direct to plane. That's why you got a black screen with audio only.

@luizkunI wonder if you have set Direct to Plane because I can see Kodi is trying egl from the log.

I use gnome wayland and use pipewire plugin to capture the screen. I can record the moonlight screen.

@peter.eismannThis should be the ffmpeg fix: https://github.com/JeffyCN/FFmpeg/commit/d11a692101ab901226b890aaa8e29751d85a4a48 Make sure you have set `direct to plane` in Kodi.

@maximumsettings You can try obs in my ppa to record the desktop. I'm using pipewire to capture the window or desktop and obs-gstreamer plugin to do the hardware encoding. I'm using gnome wayland as my desktop environment. `sudo apt install obs-studio obs-plugins obs-gstreamer xdg-desktop-portal-gnome`. As for the LG TV issue, some resolutions such as 1440p are not well supported by the video output driver of rockchip's kernel. We have to wait for a fix.

There are missing dependencies, use this command to install those: sudo apt install qml-module-qtquick-controls2 qml-module-qtquick-layouts qml-module-qtquick-window2 qml-module-qtquick2 These deps are not detected by dh_shlibs. I will add them later.

I just added moonlight-qt to my ppa: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/rockchip-multimedia

@ScottPI've created a pull request to armbian to support rock3a 5.10 kernel: https://github.com/armbian/build/pull/4794. You can build a image for rock3a using my branch.

@whitefox My ppa only supports jammy. By now the not-upstreams patches are some unofficially supported boards such as h68k and h88k and a kernel backport patch for rk356x 5.10 kernel. For rk3588 there should be no difference.

@CK1What sample you're using? These BBB movies are played well: https://mirrors.tuna.tsinghua.edu.cn/blender/demo/movies/BBB/.

@agusare you running Kodi under gbm and with direct to plane render method?

@jernejdo you mean this patch: https://github.com/LibreELEC/LibreELEC.tv/blob/master/packages/multimedia/ffmpeg/patches/v4l2-request/ffmpeg-001-v4l2-request.patch

I've built a image for this board: https://github.com/amazingfate/armbian-h68k-images, based on 5.10 rockchip legacy kernel, supporting panfrost gpu driver and hardware accelerated Kodi.

@zelda1link3rock3a is not supported by now because my image hasn't get legacy kernel 5.10 support. But I've just supported another rk3568 board hinlink h68k: https://github.com/amazingfate/armbian-h68k-images. I will make support for rock3a someday in the future.

Solved by modifying the code of ffmpeg. I can play 10bit videos now. Thank you for your response @jernej @balbes150

@balbes150yes I've tried both EGL and direct to planel. Direct to plane seems to support more formats.

I've created an issue about 10 bit videos not playable on kodi: https://github.com/xbmc/xbmc/issues/22202. Here is the debug log of kodi: https://paste.ubuntu.com/p/C29gywz4Tg/. We can see "CEGLImage::SupportsFormat - format not supported: NA12". NA12 should come from ffmpeg: https://github.com/JeffyCN/FFmpeg/blob/master/libavcodec/rkmppdec.c#L48. What I concern is why the support list of dma buf format doesn't have NV15, the yuv420 10bit drm format, which should be supported by the rockchip's drm driver: https://github.com/friendlyarm/kernel-rockchip/blob/nanopi5-v5.10.y_opt/include/uapi/drm/drm_fourcc.h#L244. Kodi uses eglQueryDmaBufFormatsEXT to get the supported dma buf format: https://github.com/xbmc/xbmc/blob/master/xbmc/utils/EGLImage.cpp#L225. Anyone knows why egl doesn't support 10 bit drm format NV15? @jernej@Kwiboo@balbes150

Rockchip has released bsp kernel 5.10 for rk356x and rk3588. Since multimedia support is not fully supported by mainline kernel, a legacy kernel would be good if you want h264/hevc hardware decode. To make kodi support hardware decoding, you need: 1, ffmpeg supporting rkmpp. I've packaged it in my ppa: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/rockchip-multimedia, which is based on the patch from https://github.com/JeffyCN/FFmpeg/. 2, kodi built with gles render system, which is also in my ppa 3, a gpu driver supporting gles. For rk356x you can use mainline panfrost driver. For rk3588 you can use panfork-mesa from my ppa: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/panfork-mesa I've tested that kodi can support hardware decoding on both 3568 and 3588. Here is the steps for rock5b to install kodi: 1, download the image I build with panfork-mesa and malig610 firmware: https://github.com/amazingfate/armbian-rock5b-images, and install it on your rock5b. 2, add my rockchip multimedia ppa: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/rockchip-multimedia: sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia 3, create a udev rule to enable the permission ofrockchip's mpp device: KERNEL=="mpp_service", MODE="0660", GROUP="video" KERNEL=="rga", MODE="0660", GROUP="video" KERNEL=="system-dma32", MODE="0666", GROUP="video" KERNEL=="system-uncached-dma32", MODE="0666", GROUP="video" RUN+="/usr/bin/chmod a+rw /dev/dma_heap" wirte the above rules to /etc/udev/rules.d/11-rockchip-multimedia.rules 4, install kodi: sudo apt install kodi 5, move kodi from xsession to wayland-session: sudo mv /usr/share/xsessions/kodi.desktop /usr/share/wayland-sessions/kodi-wayland.desktop 6, reboot the board: sudo reboot 7, in the lightdm greeter, select kodi and login 8, After starting kodi, in Settings -> Player -> Videos, enable "Allow using DRM PRIME decoder" and "Allow hardware acceleration with DRM PRIME". And set "PRIME Render Method" to "Direct To Plane" 9, Then you can play h264/h265 8 bit/10bit videos up to 4K. ============Updated on 20230206=================== rockchip-multimedia has become a universal ppa for rockchip legacy kernel. Here is the introduction: https://forum.radxa.com/t/introduction-to-rockchip-multimedia-ppa-for-ubuntu-jammy/14537 I provide a new package rockchip-multimedia-config to do all the system configs such as udev rules, chromium v4l2 devices creation. Just install this package and reboot, you are good to go.

@TaNGSoFT@gounthar Armbian has supported u-boot spi image since its initial support for rock5b. If you are using spi flash image from radxa wiki, you will failed to boot armbian because that is not a GPT image. There are two ways to write the spi flash image from armbian to the spi nor flash: 1, Boot armbian from sdcard or emmc first, and use nand-sata-install to install the u-boot to spi flash. 2, You can download the u-boot deb file from the repo of armbian: https://mirrors.tuna.tsinghua.edu.cn/armbian/pool/main/l/linux-u-boot-rock-5b-legacy/linux-u-boot-legacy-rock-5b_22.08.6_arm64.deb. Extrat it using `dpkg -x linux-u-boot-legacy-rock-5b_22.08.6_arm64.deb`, and find the spi image file `rkspi_loader.img`, and write it to spi flash referring to radxa's wiki: https://wiki.radxa.com/Rock5/install/spi Then use dd or ether to install armbian image to your NVME SSD.

You can play 1080p video with hardware decode using kodi. You have to install a v4l2-request patched ffmpeg and kodi rebuilt with option `-DAPP_RENDER_SYSTEM=gles`. You can see more detailed info from this post: https://forum.radxa.com/t/app-kodi-on-armbian-with-hardware-accelerating-decode/10170

I can play 1080p video using kodi with v4l2-request patched ffmpeg. I can also use command `ffmpeg -hwaccel drm -hwaccel_output_format drm_prime -i bbb_sunflower_1080p_30fps_normal.mp4 -f null -` to decode the video, but I failed to play video using mpv with hardware accel, what am I missing?

No need to add overlay. Try the latest image: https://github.com/amazingfate/armbian-rock3a-images. Use command nand-sata-install to install the uboot to spi flash.