Search the Community

Kodi on Orange Pi 5 with GPU Hardware Acceleration and HDMI Audio Huge thanks to user @roykon the Armbian forums for the directions on this in their various forum posts and Armbian forum user @amazingfate for maintaining the PPAs and software builds required for GPU acceleration. I have simply listed below, for the reference of others, the minimum Steps used to get Kodi running with GPU hardware acceleration (for x264/x265 decode) plus HDR auto switching and with HDMI Audio output*. (I am using the Orange Pi 5 with a Samsung 4K TV) *No instructions added yet for enabling HDMI passthrough. ** No instructions added yet for enabling HDMI CEC. Step 1 (SD card image creation) Download the image below, uncompress it and write it to an SD card. https://github.com/armbian/build/releases/download/23.02.0-trunk.0173/Armbian_23.02.0-trunk.0173_Orangepi5_jammy_legacy_5.10.110_xfce_desktop.img.xz#orangepi5 Step 2 (First boot) Boot the SD card image and complete the on-screen prompts for user & password creation. Note down the IP address of the Orange Pi 5, you will need it in step 3. Step 3 (SSH into the Orange Pi 5) SSH to the IP address of your Orange Pi 5 and login using the user account and password you set up in Step 2. Step 4 (Enable PPAs and install other elements required for GPU hardware acceleration) At the command line, enter the following commands (highlighted in Blue): sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia sudo apt update sudo apt full-upgrade sudo apt install ubuntu-desktop kodi When prompted on-screen if you wish to use gdm or lightdm, select gdm. Step 5 (Configuration file additions & changes) At the command line, enter the following commands (highlighted in Blue): sudo mv /usr/share/xsessions/kodi.desktop /usr/share/wayland-sessions/kodi-wayland.desktop sudo nano /etc/udev/rules.d/11-rockchip-multimedia.rules 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" sudo nano /etc/gdm3/custom.conf Add the line below and save the file. WaylandEnable=true sudo nano /usr/share/alsa/cards/HDMI-OUT.conf Add all of the content below and save the file. # configuration for HDMI connection which just expose the # audio out device <confdir:pcm/hdmi.conf> HDMI-OUT.pcm.hdmi.0 { @args [ CARD DEVICE CTLINDEX AES0 AES1 AES2 AES3 ] @args.CARD { type string } @args.DEVICE { type integer } @args.CTLINDEX { type integer } @args.AES0 { type integer } @args.AES1 { type integer } @args.AES2 { type integer } @args.AES3 { type integer } type hw card $CARD } sudo nano /usr/share/alsa/cards/aliases.conf Add the line below and save the file. rockchip-hdmi0 cards.HDMI-OUT Step 6 (Reboot and Start Kodi) At the command line, enter the following commands (highlighted in Blue): sudo reboot At the login screen, select “kodi” in the bottom right hand corner menu. Now login using your username and password. Kodi should now load. Step 7 (Adjust Kodi settings) From within Kodi goto Settings -> Player -> Videos goto the bottom left corner of the screen and change it from Standard to Expert. From within Kodi goto Settings -> Player -> Videos, Playback, and change Adjust display refresh rate to “On start/stop” From within Kodi goto Settings -> Player -> Videos, Processing, enable "Allow using DRM PRIME decoder" and "Allow hardware acceleration with DRM PRIME". And set "PRIME Render Method" to "Direct To Plane" From within Kodi goto Settings -> System -> Display, and change the resolution to 1920x1080p From within Kodi goto Settings -> System -> Audio, and change the Audio output device to “Built in Audio Digital Stereo (HDMI),HDMI / DisplayPort (PULSEAUDIO)” Step 8 (Test video playback and check that GPU acceleration & HDMI Audio are working) During video playback, press ‘o’ on the keyboard, and it should show Video decoder: ff-hevc_rkmpp-drm_prime (HW) During video playback, if you have a Samsung TV, press the “Info” button on your Samsung TV remote to show the current playback resolution, frame rate and whether or not HDR is in use. (Depending on the video content being played) Thank you again to Armbian forum users @royk and @amazingfate

Hi guys, its the first time im gonna post here so bear with me, i am a recent user of orange pi zero 3, one with 4GB RAM and i have been able to run the latest community release on it, things work besides audio thru hdmi, but i have noticed that the video encoding and decoding is not working, albeit 3d acceleration works thru panfrost and Mesa. I have been digging this topic and i wanted to share what i found and maybe validate if im right or perhaps i am not getting this well. 1. Video encoding and decoding in G31-MP2 is something separated from what Mesa and panfrost would do, so even if those work i cant get video acceleration with h.264 etc. 2. It is possible because the android 12 TV version from the manufacturer can do it in a very easy way, but as far as i understood this is because it is using some kind of closed source driver, that the SoC manufacturer provided (that almost all the boards made with the allwinner H616/H618 would run, so it isnt like orange pi dedicated developers to create the android being offered but it is a stock stuff that Allwinner has available for whoever buys their chips) 3. There are efforts to reverse engineer this properly called CEDRUS but there is kind of a lack of information about them since 2019, it is supposedly present in the kernel, but as many others have said and tried for some reason is not working with H616//h618. Anyone knows if it is still being developed? In conclusion the state of things with hardware decoding and encoding of video in ARM is like a wasteland, at least for linux, these chips, ARM chips we get are mostly developed for android TV boxes or TVs or tablets, but they do not develop for linux, that maybe transferring the necessary code to make it work could be trivial, but with thin resources and doing the bare minimum and being closed source the SoC manufacturer has no interest in creating this support and it is left to open source volunteers to find a way. Which means that support for the H616/H618 might come several years into the future perhaps never. Am I interpreting reality right?, i had some hopes to create something like a jellyfin box with accelerated hardware coding and decoding but nothing might be possible, there is maybe some hope, i read somewhere in the LibreELEC forums that someone made it possible to run it with video decoding (if i am not mistaken) with no audio, so perhaps someone found a way?, thanks in advance.

I have install armbian version 10 on this box. Did watch video for some time, no issues except remote who do not only mine box but satelite receiver also, and this do then crash. I have a new remote who can be adjusted on mucho boxes and dvd, tv enc. but did not manage to let it work on this RT box (mxq pro). Oke I did watch video and encode some in H265, but get not such small files als with H264 in handbrake, I do use hardware encoding with videocard, I need stil to install new computer board with a intel I7 but has not yet the time so I can try the intel hardware encoder who seems to be better... The video has much artifacts, special color screens and darknes, clouds. The videobox I have for years now the Elvira Xtreamer has not this artifacts on that same encoded H264 video while armbian has, The RT29** box do have a lot artfacts in dark scenes, sound do loud bang in the amplifier when boot, need to watch out with this, but that is not because of armbian but hardware of these cheap boxes.. Short, the H265 decoder on chip does a bad job, or the version of armbian has issues, and then I think special with the videoplayer, I can also just have 1280 x 720 max in armbian setup, or there is a software active who recode video on the fly for adjust screen dimensions?. I do not now. someone has experience with this?. regards

Hello, I find armbian awesome and my problem is because of the manufacurers. I basically want to play accelerated video (because I need 4k). I tried amlogic, but it is not still supported (https://linux-meson.com/hardware.html) the status is partial for the chips I tried. I don't what "partial" means but I can hardware decoding. I also tried allwinner, several chips. In this page https://linux-sunxi.org/Sunxi-Cedrus I see that it is supported but I tried with new kernels, old kernels... Nothing worked. I always reach a point that stops me (like segmentation fault when loading sunxi modules, system freeze when using vdpau, compilation errors due incompatibility between version...) I was thinking of try some rockchip but I think that I will suffer the same pain so this is why I want to ask you guys because I am a bit lost and I am starting to think that everything I try is worthless. Can someone bring me some light? Any tip about what chips are more "friendly" with video acceleration and, if mainline kernel or not, player to use... All the documentation/posts I found are outdated or incomplete and this is the reason I am writing this post, because I am not able to find more information. I know that the manufacturers does not help and everything we have is due the awesome work of the community. It is complicated stuff. Any kind of information will be very helpful. Thanks

Hello! I have a Zero2 board with 1GB of RAM. I compiled a Debian 12 desktop image for Zero2 using Armbian and I want to play online videos through a web browser. Unfortunately, the results have been disappointing as the performance for 1080p videos is very slow. I tried using swap, but it didn't help. I also attempted to play 1080p videos using MPV and VLC. MPV can still play the videos, but it feels sluggish, and VLC gets stuck on the screen until the playback is finished. I would like to know how to configure Zero2 on Linux to achieve video acceleration. I'm new to this, so I would appreciate some guidance. Thank you!

Sorry, don't have the Armbianmonitor info handy but wanted to get this started... I'm trying to bring up a Libre Renegade RK3328-CC for use as a media center. Armbian's performance is absolutely wonderful compared to the other builds I've tried on this box. Unfortunately, I want the HDMI output going to a Samsung Frame TV, and resolution negotiation fails badly -- I get obvious rasters with black between them, nowhere near the 4K that this TV model is capable of and not even a smooth conversion (Note that the eyes here suggests that the black line is occurring every third raster or something like that...) What information I have gathered so far: TV: Samsung 43" “The Frame”, model QN43LS03BAFXZA Firmware T-PTMAKVC-1622.4, BT-S 4K native resolution, but should be able to upconvert edid-decode (hex): 00 ff ff ff ff ff ff 00 4c 2d 7f 72 00 0e 00 01 01 20 01 03 80 5f 36 78 0a b3 61 ab 4f 46 a8 27 0b 50 54 bd ef 80 71 4f 81 c0 81 00 81 80 95 00 a9 c0 b3 00 d1 c0 04 74 00 30 f2 70 5a 80 b0 58 8a 00 50 1d 74 00 00 1e 56 5e 00 a0 a0 a0 29 50 30 20 35 00 50 1d 74 00 00 1a 00 00 00 fd 00 18 4b 0f 51 1e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20 01 9f 02 03 51 f0 52 5f 10 1f 04 13 05 14 20 21 22 5d 5e 62 64 07 16 03 12 2f 0d 57 07 09 07 07 15 07 50 57 07 01 67 54 03 83 0f 00 00 e2 00 4f e3 05 c3 01 6e 03 0c 00 30 00 b8 44 20 00 80 01 02 03 04 e3 06 0d 01 e5 0e 60 61 65 66 e5 01 8b 84 90 01 02 3a 80 18 71 38 2d 40 58 2c 45 00 50 1d 74 00 00 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ea Block 0, Base EDID: EDID Structure Version & Revision: 1.3 Vendor & Product Identification: Manufacturer: SAM Model: 29311 Serial Number: 16780800 Made in: week 1 of 2022 Basic Display Parameters & Features: Digital display Maximum image size: 95 cm x 54 cm Gamma: 2.20 RGB color display First detailed timing is the preferred timing Color Characteristics: Red : 0.6699, 0.3115 Green: 0.2734, 0.6591 Blue : 0.1533, 0.0449 White: 0.3125, 0.3291 Established Timings I & II: IBM : 720x400 70.081663 Hz 9:5 31.467 kHz 28.320000 MHz DMT 0x04: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz Apple : 640x480 66.666667 Hz 4:3 35.000 kHz 30.240000 MHz DMT 0x05: 640x480 72.808802 Hz 4:3 37.861 kHz 31.500000 MHz DMT 0x06: 640x480 75.000000 Hz 4:3 37.500 kHz 31.500000 MHz DMT 0x09: 800x600 60.316541 Hz 4:3 37.879 kHz 40.000000 MHz DMT 0x0a: 800x600 72.187572 Hz 4:3 48.077 kHz 50.000000 MHz DMT 0x0b: 800x600 75.000000 Hz 4:3 46.875 kHz 49.500000 MHz Apple : 832x624 74.551266 Hz 4:3 49.726 kHz 57.284000 MHz DMT 0x10: 1024x768 60.003840 Hz 4:3 48.363 kHz 65.000000 MHz DMT 0x11: 1024x768 70.069359 Hz 4:3 56.476 kHz 75.000000 MHz DMT 0x12: 1024x768 75.028582 Hz 4:3 60.023 kHz 78.750000 MHz DMT 0x24: 1280x1024 75.024675 Hz 5:4 79.976 kHz 135.000000 MHz Apple : 1152x870 75.061550 Hz 192:145 68.681 kHz 100.000000 MHz Standard Timings: DMT 0x15: 1152x864 75.000000 Hz 4:3 67.500 kHz 108.000000 MHz DMT 0x55: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz DMT 0x1c: 1280x800 59.810326 Hz 16:10 49.702 kHz 83.500000 MHz DMT 0x23: 1280x1024 60.019740 Hz 5:4 63.981 kHz 108.000000 MHz DMT 0x2f: 1440x900 59.887445 Hz 16:10 55.935 kHz 106.500000 MHz DMT 0x53: 1600x900 60.000000 Hz 16:9 60.000 kHz 108.000000 MHz (RB) DMT 0x3a: 1680x1050 59.954250 Hz 16:10 65.290 kHz 146.250000 MHz DMT 0x52: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz Detailed Timing Descriptors: DTD 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz (1872 mm x 1053 mm) Hfront 176 Hsync 88 Hback 296 Hpol P Vfront 8 Vsync 10 Vback 72 Vpol P DTD 2: 2560x1440 59.950550 Hz 16:9 88.787 kHz 241.500000 MHz (1872 mm x 1053 mm) Hfront 48 Hsync 32 Hback 80 Hpol P Vfront 3 Vsync 5 Vback 33 Vpol N Display Range Limits: Monitor ranges (GTF): 24-75 Hz V, 15-81 kHz H, max dotclock 300 MHz Display Product Name: ‘SAMSUNG’ Extension blocks: 1 Checksum: 0x9f Block 1, CTA-861 Extension Block: Revision: 3 Underscans IT Video Formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 Native detailed modes: 0 Video Data Block: VIC 95: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz VIC 16: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz VIC 31: 1920x1080 50.000000 Hz 16:9 56.250 kHz 148.500000 MHz VIC 4: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz VIC 19: 1280x720 50.000000 Hz 16:9 37.500 kHz 74.250000 MHz VIC 5: 1920x1080i 60.000000 Hz 16:9 33.750 kHz 74.250000 MHz VIC 20: 1920x1080i 50.000000 Hz 16:9 28.125 kHz 74.250000 MHz VIC 32: 1920x1080 24.000000 Hz 16:9 27.000 kHz 74.250000 MHz VIC 33: 1920x1080 25.000000 Hz 16:9 28.125 kHz 74.250000 MHz VIC 34: 1920x1080 30.000000 Hz 16:9 33.750 kHz 74.250000 MHz VIC 93: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz VIC 94: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz VIC 98: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz VIC 100: 4096x2160 30.000000 Hz 256:135 67.500 kHz 297.000000 MHz VIC 7: 1440x480i 59.940060 Hz 16:9 15.734 kHz 27.000000 MHz VIC 22: 1440x576i 50.000000 Hz 16:9 15.625 kHz 27.000000 MHz VIC 3: 720x480 59.940060 Hz 16:9 31.469 kHz 27.000000 MHz VIC 18: 720x576 50.000000 Hz 16:9 31.250 kHz 27.000000 MHz Audio Data Block: Linear PCM: Max channels: 6 Supported sample rates (kHz): 192 96 48 44.1 32 Supported sample sizes (bits): 24 20 16 Linear PCM: Max channels: 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 AC-3: Max channels: 6 Supported sample rates (kHz): 48 44.1 32 Maximum bit rate: 640 kb/s Enhanced AC-3 (DD+): Max channels: 8 Supported sample rates (kHz): 48 44.1 32 Supports Joint Object Coding MAT (MLP): Max channels: 8 Supported sample rates (kHz): 192 96 48 Supports Dolby TrueHD, object audio PCM and channel-based PCM Hash calculation not required for object audio PCM or channel-based PCM Speaker Allocation Data Block: FL/FR - Front Left/Right LFE1 - Low Frequency Effects 1 FC - Front Center BL/BR - Back Left/Right Video Capability Data Block: YCbCr quantization: No Data RGB quantization: Selectable (via AVI Q) PT scan behavior: No Data IT scan behavior: Supports both over- and underscan CE scan behavior: Supports both over- and underscan Colorimetry Data Block: xvYCC601 xvYCC709 BT2020YCC BT2020RGB Reserved MD0 Vendor-Specific Data Block (HDMI), OUI 00-0C-03: Source physical address: 3.0.0.0 Supports_AI DC_36bit DC_30bit DC_Y444 Maximum TMDS clock: 340 MHz Extended HDMI video details: HDMI VICs: HDMI VIC 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz HDMI VIC 2: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz HDMI VIC 3: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz HDMI VIC 4: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz HDR Static Metadata Data Block: Electro optical transfer functions: Traditional gamma - SDR luminance range SMPTE ST2084 Hybrid Log-Gamma Supported static metadata descriptors: Static metadata type 1 YCbCr 4:2:0 Video Data Block: VIC 96: 3840x2160 50.000000 Hz 16:9 112.500 kHz 594.000000 MHz VIC 97: 3840x2160 60.000000 Hz 16:9 135.000 kHz 594.000000 MHz VIC 101: 4096x2160 50.000000 Hz 256:135 112.500 kHz 594.000000 MHz VIC 102: 4096x2160 60.000000 Hz 256:135 135.000 kHz 594.000000 MHz Vendor-Specific Video Data Block (HDR10+), OUI 90-84-8B: Application Version: 1 Detailed Timing Descriptors: DTD 3: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz (1872 mm x 1053 mm) Hfront 88 Hsync 44 Hback 148 Hpol P Vfront 4 Vsync 5 Vback 36 Vpol P Checksum: 0xea I understand that Armbian is an experimental build and this combination may simply not work.... but if there's anything I can try to do to help the driver and monitor reconcile with each other, or to help you debug this, please let me know. (BTW, I don't mind the security timeout/rechecking on this webform, but having it drag focus back to that checkbox is somewhat disruptive.)

Hi all. I made a video about KDE Neon on the Raspberry Pi 5. I love it, I'll be switching from ubuntu-desktop to this. Greetings, NicoD

Hi, I have an A95X F3 Air tv box that has an s905x3 chipset. I followed the instructions here. I believe i used the correct dtb file and tested out multiple others. I've tried reformatting my drive with SD card formatter. I've tried flashing my stock firmware. However I cannot seem to get armbian to boot. I'm getting no video output. I'm not sure what I'm doing wrong here. I've searched high and low on the internet and I could not find a solution. I have seen aml_autoscript.zip being mentioned here and there however the image I've downloaded doesn't seem to have it. Any help would be appreciated.

I installed Armbian from Armbian_23.11.3_Rpi5b_jammy_current_6.1.68_cinnamon_desktop.img.xz downloaded today (February 11th 24) After installation, I performed an upgrade/update. I have not yet installed any additional software. Issues; 1) when cinnamon desktop starts there is message displayed: Your system is currently running without video hardware acceleration 2) vgencmd always gives an error: VCHI initialization failed, no matter if I run it with sudo or not, or with which parameter(s) I run it. armbian monitor -u gave link https://paste.armbian.com/lurunopoyo

Hello, i'm using Armbian 23.11 Jammy-amazingfated Gnome. Kernel 5.10 If to seek a couple of times in h264 1080p BD remux'es it will cause system restart. Any video players are affected. Tried mpv, vlc, kodi and others. Problem affect just h264 1080p remuxes, that typically are 30..40 Gb, smaller h264 or even larger h265 files seem to work fine. I tried fresh install of armbian, where no rkmpp is installed, then h264 files plays/seeks fine, in software mode of course. Once I did sudo update/upgrade, that also installs rkmpp and other rockchip stuff, then videos start to play with rkmpp and problem is back. I've tried disabling hw decoding as workaround , weird, but it seems it's not possible to do in any player. In mpv : hwdec=no , or pressing ctrl+h has no affect, can't get rid of rkmpp decoder. Ive tried all possible commands related to this, from official mpv documentation, but nothing helps to disable rkmpp . This is probably another issue. Disabling buggy h264_rkmpp_decoder could be good workaround, as cpu is easily capable do play 1080p in sw, but can't find a way to do this, no matter i try, pls help. Especially looking for solution for mpv

After shelving my Rock 64 I dusted it off and downloaded the latest desktop image with Ubuntu Focal. The latest OS has video artifacts that the older OS did not. I can only describe the issue as "scan lines," but they are random black bars that appear through out the entire screen (as if WiFi is interrupting the signal only there's no WiFi on the device). I would like to know the best way to bisect the issue as I'm fully capable of cloning the repo, building the image, loading the image and testing it out but if there are pointers to simplify the process I'd love to hear. Hoping to give back since this is a community supported board. Thanks.

wsl2: arm64: current: DRM/FB stuff so wsl2-arm64 can be used in HyperV with video & keyboard wsl2: arm64: current: DRM/FB stuff so wsl2-arm64 can be used in HyperV with video & keyboard wsl2: arm64: current: EFI pstore / keyboard View the full article

I have an OTT TV Box, model ABOX-A1 ( 1G + 8G, S905X ). It is running Armbian 23.11.1 bookworm. How can I have hardware video decoding? Hardware video decoding support seems present in the 6.1.63-current-meson64 kernel. It seems only the V4L2 M2M API is present. Some firmware seems missing. I was getting "meson-vdec c8820000.video-codec: Direct firmware load for meson/vdec/gxl_h264.bin failed with error -2" in dmesg. I don't know what package I need to install. I was thinking maybe firmware-linux-nonfree, but that conflicts with armbian-firmware due to firmware-ralink. The files are available at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec though, and I downloaded gxl_*.bin from there and put them in /lib/firmware/meson/vdec/ . I've tried Kodi, mpv and ffmpeg, in Wayfire and at the text console. Kodi always uses lots of CPU, and mpv crashes whenever I use --hwdec=v4l2m2m-copy. The best result was "ffplay -vcodec h264_v4l2m2m file.mp4" at the console. That at least actually seems to use hardware decoding because I see this output: driver 'meson-vdec' on card 'Amlogic Video Decoder' in mplane mode. But the CPU utilization is actually worse, about 300%, compared to below 200% without -vcodec h264_v4l2m2m. Edit: After installing mpv 0.37.0-1 and its dependencies from trixie (Debian testing), I definitely got hardware acceleration in mpv --hwdec=v4l2m2m-copy. CPU usage was less that 100% on one core. However, there were still problems with dropped frames and audio/video desynchronization, so I don't recommend this. Kodi CPU usage seems decreased too, often below 200% playing the same file, but this is still terrible for playing 720p H.264. It's not worth messing up your packages with a mix from two Debian versions only to get this. Edit: The Kodi 2:20.1+dfsg-1 from Bookworm doesn't have the DRM PRIME options in "Settings > Player > Videos", so I guess it doesn't support acceleration? The Kodi 2:20.4+dfsg-1 from Trixie does have those options, and enabling them makes the video disappear. I've tried setting "PRIME Render Method" to EGL and Direct-To-Plane, and both failed in a similar way.

This https://github.com/Joshua-Riek/ubuntu-rockchip/wiki/Orange-Pi-5 produces nearly 0 dropped frames at 4K 60fps on https://www.youtube.com/watch?v=LXb3EKWsInQ While latest Armbian_23.11.1_Orangepi5_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz and doing immediately after install, only these commands: sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia sudo apt update sudo apt dist-upgrade sudo apt install mali-g610-firmware rockchip-multimedia-config exactly like it says on https://www.armbian.com/orangepi-5/ and sudo reboot produces alot of dropped frames on same youtube 4K 60fps video! What am I missing? Shouldnt there be equal accelerated video performance?

Hello, this quick tutorial is to introduce an experimental Debian and Ubuntu APT repository to install ffmpeg and mpv compiled with v4l2request and v4l2drmprime patches developed by Linux kernel, LIbreELEC and Kodi folks to allow hardware video decoding on stateless decoders like those implemented in Rockchip and Allwinner SoCs for h.264, h.265, vp8 and vp9 codecs. The repository introduces a new package ffmpeg-v4l2request that integrates and substitues the base ffmpeg package and its related packages. Also provides mpv 0.35.1 for Ubuntu Jammy, which has an overrall better support for hardware video decoders. Preconditions: Kernel should be 6.1 or more recent armhf or arm64 architecture Supported operating systems are Debian Bookworm and Ubuntu Jammy Rockchip and Allwinner have already been tested, but this should work on other platforms with stateless decoders supported in kernel APT REPOSITORY SETUP To install the repository, just copy and paste the lines for your operating system in a terminal For Debian Bookworm: $ sudo wget http://apt.undo.it:7241/apt.undo.it.asc -O /etc/apt/trusted.gpg.d/apt.undo.it.asc $ echo "deb http://apt.undo.it:7241/debian bookworm main" | sudo tee /etc/apt/sources.list.d/apt.undo.it.list For Ubuntu Jammy: $ sudo wget http://apt.undo.it:7241/apt.undo.it.asc -O /etc/apt/trusted.gpg.d/apt.undo.it.asc $ echo "deb http://apt.undo.it:7241/ubuntu jammy main" | sudo tee /etc/apt/sources.list.d/apt.undo.it.list INSTALL FFMPEG AND MPV PACKAGES $ sudo apt update $ sudo apt install ffmpeg-v4l2request mpv SETUP MPV CONFIG FILE $ sudo mkdir -p /etc/mpv $ echo -e "hwdec=drm\ndrm-drmprime-video-plane=primary\ndrm-draw-plane=overlay" | sudo tee /etc/mpv/mpv.conf You can now play your videos using mpv and they should run with hardware decoding if supported, either in virtual terminals or in X11/Wayland windows! Enjoy! Notes: your mileage may vary a lot: the more recent is the kernel version, the better is support (you may need edge kernel) bug: when rendered in X11/Wayland window, video may show scattered tiles during frames bug: Lima driver (Mali 400/450) shows a red/pink tint when video is played in X11/Wayland (see https://github.com/mpv-player/mpv/issues/12968) (workaround below: https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/?do=findComment&comment=177968) Panfrost driver should work flawlessy 10 bit HEVC are generally supported on all Rockchip devices (rk322x, rk3288, rk33x8, rk3399), but Allwinner H3 have no hardware support for that

I have owned numerous Raspberry Pi boards over the years, and I have always have ran Kodi on one of them. For years I have been wanting to upgrade my RPi 3 as it cannot play any of my H.265/HEVC videos. With all the shortages, and how old the Raspberry Pi 4 is getting, I made a rather spontaneous purchase for this Orange Pi 4 LTS board. Getting it all setup is easy enough, but of course, the video (even with H.264!) nearly maxes all 6 cores and the video is chunky as it's just doing everything without any video acceleration. Even navigating the menu seems slow and delayed. I have been scouring these forums and other sources for about 12 hours now, and I am still unsure which route to go. Just as a test, I ran Kodi as root and it was much smoother in the menu system and seemed to do H.264 (in software of course, so it was working really hard). But broke Pulseaudio, as Pulse is hardcoded to not accept connections from root when it's not setup as a system-wide service. Anyway, that's not an option. Kodi doesn't need to, and shouldn't run as root. I was very excited, then extremely let down when I found this post: A custom image with custom repositories? Plus, I don't want X11 or Wayland plus a window manager, I don't need it! Either way, it *seems* to be tied to a completely different chipset. I've been up all night working on this, and I am starting to go delirious, so any help would be appreciated.

I've taken peeks at threads related to hardware decoding (of H.264 and HEVC, mainly) on Allwinner and Rockchip platforms on and off, sometimes dabbled in trying and failing to implement solutions recommended there. Being a complete amateur, I find the topic very opaque and confusing, with various different components that need to interface with each other, be patched in sync, and sometimes change drastically between kernel versions, etc. Today I sat down and read up on these subjects, scouring wikis, documentation, this forum, and assorted other sources to try and understand how this works. In this post I will attempt to compile what I've learned on the different software components involved, their relationships, their current status, and solutions to the problem. I hope people more knowledgeable will correct me when I get something wrong or cite outdated information. Stuff which I am highly uncertain of I will print in italics. (This post is going to focus on mainline implementations of Cedrus/Allwinner, I haven't looked into Hantro/Rkvdec/Rockchip specifics yet. I will speak only of H.264 and H.265/HEVC; I don't understand the high/low stuff and didn't pay attention to other codecs.) Components: Basics: Video codecs like H.264, H.265/HEVC, MPEG-2, etc. are standardised methods which serve to more efficiently encode and decode videos, reducing their filesize. Software en-/decoding is very CPU-intensive. Modern GPUS and ARM SoCs therefore contain specialised hardware (VPUs) to delegate these tasks to. Working hardware decoding is particularly important for underpowered ARM CPUs. Drivers: Topmost in the stack are the VPU drivers. These are Sunxi-Cedrus/Cedrus V4L2 M2M and Cedar [Is this the legacy one?] on Allwinner; Hantro and Rkvdec on Rockchip. These are all still in development, but Cedrus already fully supports H.264, and partially supports HEVC, and is already usable in the mainline kernel. APIs: In order for anything (userspace APIs, libraries) to make use of the VPU drivers, you need backends/APIs. For Cedrus, there is the unmaintained libva-v4l2-request backend which implements VA-API, the legacy VDPAU implementation libvdpau-sunxi, and as of kernel version 5.11, H.264 has been merged into the uAPI headers. Different applications may make recourse to one or another of these APIs. Libraries: FFmpeg and GStreamer. provide libraries and APIs of their own to other applications but can (importantly!) also output directly to the framebuffer. FFmpeg must be patched to access either libva-v4l2-request or the Cedrus driver headers. GStreamer directly accesses kernel headers since 1.18 (works on 5.9, not on 5.10; 1.20 will support 5.11.) Media players: mpv and depends on FFmpeg for hardware acceleration (and must be patched together with it). VLC can be set to access libva-v4l2-request directly. Kodi 19.0+ supports hardware acceleration out of the box without any out-of-tree patches. Display server: An additional complication is drawing the output of any of the above on screen. Most successful implementations I've seen bypass X11 and either output directly to the framebuffer or force a plane/display layer on top of any X windows. Wayland apparently makes this easier by allowing applications to use their own DRM planes, but this hasn't been explored much yet. Kodi 19.0 works with all three windowing systems (X, Wayland, and gbm). Codec status: Taken from the LibreElec thread (which reflects LibreElec's status and is ahead of what works elsewhere, but outlines hardware limitations): Approaches: Many people have managed to make it work on their machines using different approaches. Note that some of these solutions are one or two years old, and kernel developments since may have changed the situation. Ordered from newer to older: LibreElec – kernel + ffmpeg + Kodi: LibreElec is a Just-Enough-OS with the sole purpose of running Kodi, a media player. It's at the bleeding edge and usually implements codecs and features well before mainline or other distros. It achieves this by heavily patching everything up and down the stack, from the Linux kernel over FFmpeg to Kodi itself. These patches could all be applied to an Armbian build, but there are a lot of them, they're poorly documented, and you'd need to dig into their github to understand what they all do. LibreElec runs Kodi directly without a desktop. kodi-gbm is a package that can be installed on Armbian and functions similarly. Key contributors to the project are @jernej and @Kwiboo, who sometimes post about their work here (and have been very helpful with questions, thank you). @balbes150 includes some of LibreElec's patches in his Armbian-TV builds, but I don't know which. Kodi 19.0: LibreElec patches + mpv: @megous – Kernel 5.11 + GStreamer: This implementation, done here on a PinePhone (A64), patches the 5.9 kernel and uses a recent version of GStreamer (1.18 and up), whose output is rendered directly to a DRM plane via kmssink. (No X or Wayland.) GStreamer 1.18 works with the 5.9 kernel. It does not work with 5.10, because of numerous changes to the kernel headers in this version. In 5.11 the H.264 headers were moved into the uAPI; the master branch of GStreamer reflects this, but there haven't been any releases with these patches yet. It'll probably be in repositories with GStreamer 1.20; until then you can build it from source. @Sash0k – patched libva-v4l2-request + VLC: This updates bootlin's libva-v4l2-request and follows the Sunxi wiki's instructions for enabling VLC to make use of it. It works on the desktop. This only works for H.264 and breaks HEVC. When I tried to replicate this approach on a recent Armbian build, I discovered that the h264.c files in the kernel (that libva-v4l2-request draws on) have changed considerably between 5.8 and 5.10, and I lack the understanding to reconcile libva-v4l2-request with them. @ubobrov – old kernel + libcedrus + libvdpau-sunxi + ffmpeg + mpv: This approach, which supports encoding decoding of H.264 uses the libvdpau-sunxi API and ports the legacy driver to mainline as a loadable kernel module and if I understand it correctly, ubobrov ported a legacy feature to mainline. In the post quoted below the kernel is 4.20, but the same method has been successfully applied to 5.7.8 by another user. It requires that the board's device tree be patched, as documented in ubobrov's github repository. The summary seems to be that none of the current implementations on Allwinner boards really play nice with X or desktop sessions, and it's best to output directly to the framebuffer. Kwiboo has forked FFmpeg and mpv to make good use of new and unstable kernel features/hardware acceleration which will take a while to make their way upstream. The recent 5.11 move of stateless H.264 out of staging and into the uAPI should facilitate further developments. I intend to try some of these things in the nearer future. Thanks to everyone who works on mainlining all of this VPU stuff, and to users here who contribute solutions and readily & patiently answer questions (Jernej especially). I hope I didn't post any falsehoods out of ignorance, and welcome any corrections. Other related threads here: https://forum.armbian.com/topic/11551-4kp30-video-on-orange-pi-lite-and-mainline-hardware-acceleration/ https://forum.armbian.com/topic/16804-orange-pi-pc-h3-armbian-focal-5104-sunxi-av-tv-out-cvbs-enable/page/2/ https://forum.armbian.com/topic/11184-hardware-graphicvideo-acceleration-in-h3-mainline/ https://forum.armbian.com/topic/13622-mainline-vpu/

Hello dear comminuty, I have spent the last few days trying to get Hardware-Accelerated Video Decoding Encoding to work on the H618. I have tried everything but it does not work. ffmpeg -input_format mjpeg -video_size 1920x1080 -i /dev/video1 -c:v cedrus264 -f rtsp rtsp://localhost:$RTSP_PORT/$MTX_PATH my goal is to output a rtsp stream from a camera. But I get this ERROR: [cedrus264 @ 0xaaaae53e5170] VE Open error. Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height sudo ffmpeg -f v4l2 -video_size 1280x720 -i /dev/video1 -c:v cedrus264 -pix_fmt nv12 test1.mp4 ffmpeg version git-2021-10-01-afd516b Copyright (c) 2000-2021 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14) configuration: --prefix=/usr --enable-nonfree --enable-gpl --enable-version3 --enable-vdpau --enable-libx264 --enable-libmp3lame --enable-libpulse --enable-libv4l2 libavutil 57. 7.100 / 57. 7.100 libavcodec 59. 9.101 / 59. 9.101 libavformat 59. 5.100 / 59. 5.100 libavdevice 59. 0.101 / 59. 0.101 libavfilter 8. 10.100 / 8. 10.100 libswscale 6. 1.100 / 6. 1.100 libswresample 4. 0.100 / 4. 0.100 libpostproc 56. 0.100 / 56. 0.100 Input #0, video4linux2,v4l2, from '/dev/video1': Duration: N/A, start: 2315.045127, bitrate: 147456 kb/s Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 1280x720, 147456 kb/s, 10 fps, 10 tbr, 1000k tbn Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (cedrus264)) Press [q] to stop, [?] for help [cedrus264 @ 0xaaaae53e5170] VE Open error. Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height Conversion failed! It was a hard way for me to get compile FFmpeg with Cedrus I have to say that I am new to Linux. Therefore I hope that someone can give me a detailed instruction on how to finally get it running. lsmod | grep cedrus sunxi_cedrus 45056 0 videobuf2_dma_contig 24576 1 sunxi_cedrus v4l2_mem2mem 36864 1 sunxi_cedrus videobuf2_v4l2 24576 3 sunxi_cedrus,uvcvideo,v4l2_mem2mem videobuf2_common 49152 7 sunxi_cedrus,videobuf2_vmalloc,videobuf2_dma_contig,videobuf2_v4l2,uvcvideo,v4l2_mem2mem,videobuf2_memops videodev 204800 5 sunxi_cedrus,videobuf2_v4l2,uvcvideo,videobuf2_common,v4l2_mem2mem mc 53248 6 sunxi_cedrus,videodev,videobuf2_v4l2,uvcvideo,videobuf2_common,v4l2_mem2mem otherwise I despair of this project

I want to install jellyfin as a docker container on my Orange pi 5. How can I enable hardware acceleration for it? On the container page (https://hub.docker.com/r/linuxserver/jellyfin) there are instructions for various options, but orange pi 5 is not there of course. I have enabled 3D acceleration as mentioned on the armbian page for orange pi 5.

When connected to some PC monitors, the image is larger than the physical screen: about 20 pixels at the top and bottom sides, and 50 pixels at the right and left sides are missing. This happens as soon as the board boots (without logo), the start of lines are truncated, and this also happens on text ttys (Ctrl + Alt + F1..6). I guess it's about a boot env variable, but I could not find it.

Hello, As far as i know Orange PI 3B using the Rockchip RK3566, is this SOC support graphic acceleration? I am running Armbian 23.8.2 Jammy with bleeding edge Linux 6.5.2-edge-rockchip64, only 1 tab of Chromium with video player but the CPU reached 100% all time

Hi, I'm seeing the following error in Chromium when trying to play youtube, the video loading screen never opens the video. I have installed chromium-browser (+libv4l-rkmpp, +ffmpeg, +rockchip-multimedia-config) from the ppa: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/rockchip-multimedia My OS version is Armbian 23.08 Jammy. When using FFplay the rkmpp hardware decoder is able to correctly decode h264 and hevc content, so there does not seem to be a problem with rkmpp. Any thoughts on what could be wrong? I found another guy who had the same issue, but there was no resolution: https://github.com/armbian/build/issues/5384 Failed to query video capabilities: Inappropriate ioctl for device Failed to query video capabilities: Inappropriate ioctl for device Failed to query video capabilities: Inappropriate ioctl for device Failed to query video capabilities: Inappropriate ioctl for device [7199:7199:0929/200251.817665:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.818176:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=0 texture_id=180 [7199:7199:0929/200251.818517:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.818876:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=1 texture_id=181 [7199:7199:0929/200251.819135:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.819298:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=2 texture_id=182 [7199:7199:0929/200251.819505:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.819676:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=3 texture_id=183 [7199:7199:0929/200251.819929:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.820091:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=4 texture_id=184 [7199:7199:0929/200251.837653:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.837912:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=5 texture_id=185 [7199:7199:0929/200251.838197:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.838384:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=6 texture_id=186 [7199:7199:0929/200251.838653:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.838815:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=7 texture_id=187 [7199:7199:0929/200251.839051:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.839206:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=8 texture_id=188 [7199:7199:0929/200251.839443:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported. [7199:7199:0929/200251.839600:ERROR:v4l2_video_decode_accelerator.cc(525)] could not create EGLImageKHR, index=9 texture_id=189 [7199:7199:0929/200251.839815:ERROR:gl_display.cc(520)] EGL Driver message (Error) eglCreateImageKHR: EGL_KHR_image not supported.

Hi, I have installed ubuntu image in the allwinner H616 processor. I have installed chromium browser. If i play full HD video, it is getting struck. I understand that browser is not using the hardware codec for the video playing and total load is going to CPU. Because of that full HD videos are not playing properly. I have checked browser setting but it is enabled. In my image verified the config files. But no clue found. Could any one support what need to checked in the image.

Greetings all; I have a pile of bananapi-m5's, all used behind a home.arpa local network. I am the only one here, and no one but me will ever have access to these machines. So I need full access from any other machine on my local network. I updated one that I am slowly configuring to drive a bigger enter5+ 3d printer. New mobo in the rinter so I am starting from square one. Using klipper and mainsail as web interfaces to klipper. Now it goes to a no screen condition at about the time it used to bring up the login requester, but I can still access it via ssh -X me & my pw., but don't have full access cuz x or whatever is not running. I need it to be running a full desktop, which it was prior to the upgrade a day or so back but after I login from its own keyboard. The ssh -X login I have now has not even run udev, so klipper can't find the printer which is identified as its /dev/serial/by_id, but there is not a /dev/serial now. So, how do I make an uptodate Jammy install, think I've logged in to a fully working desktop? rpi4b's do it. Thanks all, Take care & stay well

Hi all. Here my review of the Orange Pi 5 Plus with Armbian Jammy. I show tips for better desktop experience, show how to build your own images, how to run games, and tons of info about the board. Here's the video : For those who rather read, here's my gathered data : https://docs.lane-fu.com/s/5IxGlf4gn Greetings, NicoD