amazingfate

@schwar3katI'm using kernel 5.10.160-rk35xx kernel now. And I can see wideviine is detected on website https://bitmovin.com/demos/drm by chromium. From chrome://components/ I can see widevine is enabled. I haven't tried kodi.

@MinhYou have to read docs from rockchip: https://gitlab.com/rk3588_linux/linux/bsp/docs/-/tree/linux-5.10-gen-rkr3.5/Linux/Multimedia There should be a lot of guides in the internet world.

@Minh do you know what does `omxh264enc` mean? I recommend you to google it first.

Orange pi 5 has rockchip_suspend enabled in the devicetree. I don't know if that patch really works. Someone has to confirm that.

On rock5b, no need to add the patch. I just have to enable rockchip_suspend node in the device tree. After suspend, I can wake my board by the power button.

Tested on rock5b, that commit won't wake my board after suspend.

Comment this line: https://github.com/armbian/linux-rockchip/blob/rockchip-5.10/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c#L2175

You need to backport the driver of mt7921 from mainline to kernel 5.10. I've already made a patch: https://github.com/amazingfate/armbian-h68k-images/blob/master/backport-v6.0.16.patch

@roykWell done! I've just uploaded a new version of ffmpeg to my ppa.

@roykNV15 and NA12 are the drm format for 10bit videos. HDR support are in the hdmi kernel driver:https://github.com/armbian/linux-rockchip/blob/rockchip-5.10/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c#L1748 I don't have a HDR monitor so I can't test.

@royk @luizkun take a look at this: https://github.com/xbmc/xbmc/pull/16103

@roykthat is not the drm format of hdr.

@luizkun kodi linux will check if the drm format is supported by the kernel: https://github.com/xbmc/xbmc/blob/master/xbmc/windowing/gbm/drm/DRMPlane.cpp#L48 Android works doesn't mean kernel supports that. Kodi linux use drm prime to make hardware decoding work. If you have the ability to solve this issue you can contribute to upstream xbmc.

@royk@PajPajHDR is not supported because the DRM format of the video is not supported in kernel.

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.