Pi3 doesn't decode HEVC in HW, it just have extremely optimized SW decoding, but only in LE9.2 and lower, not LE10. I'm not sure what is 10-bit HEVC performance.
Posts by jernej
-
-
oddebian Currently I can't think of any data that would help in narrowing down issue. Sadly only way to fix it, is to reliably reproduce it on my development system, but I don't have any success with that.
-
Oh i thought thats just the name of the decoder(DRM Prime) , and not realated to Amazon. Today i learned :).
Ah, sorry, brainfart on my side. DRM prime is really a decoding method, you're right
Anyway, I'm pretty sure you tried to watch 10-bit HEVC and H5 doesn't have appropriate core neither to HW decode nor HW render it. H6 does, so it will be very low CPU utilization.
You can use mediainfo addon, which shows basic information about video file.
-
DRM Prime
I guess Amazon Prime? Note that if Widevine (or basically any other) DRM plugin is used, video is always decoded on CPU. Cortex A53 cores are just not designed for that task. Because of that, being able to play only 720p HEVC sounds about right. Another part of your problem is that 10-bit HEVC stream was selected. This is not supported by HW in any form, even rendering it via "direct to plane" method selected by default. Kodi doesn't yet know to fallback to GPU rendering in such cases. If you select GPU rendering in settings, video will be there, but due many inefficiencies in decoding and rendering process, it will most likely be slideshow.
-
What do I need to do to get the wifi working?
Your own image with wifi driver. It was explained many times "why" in main topic of Allwinner subforum.
I used the Raspberry Pi Imager. The imager kept giving me an error saying it couldn't create the config.txt file, so I moved on from that, figuring I could just edit the settings in Kodi. Not a problem I need solved, just mentioning it in case that matters.
config.txt is RPi specific thing and is not applicable to any other platform.
When I turn on bluetooth and then go to the bluetooth tab it says no bluetooth adapter, and after a reboot (with it still enabled) it says bluetooth disabled.
What do you mean by "turn on"? Board doesn't have integrated bluetooth. Did you use USB bluetooth adapter?
-
Everytime i get a blank screen when i try this kernel parameter:
initrd=/edid.cpio drm_kms_helper.edid_firmware=edid/edid.bin video=card0-HDMI-A-1:3840x1080D
edid/edid.bin doesn't exist, so yeah, kernel gets confused. Note, loading custom edid is not really supported as of now in some LE images (including AW), because kernel tries to load file before filesystems are even mounted.
-
Can you try with nightly image?
-
No, just put tar file in /storage/.update folder and reboot
-
oddebian I can't reproduce this issue on images built by me, even 10.0.2. So I can't really do much. Except upload 10.0.2 update, which you can use and issue may be gone: http://jernej.libreelec.tv/test/le10/Libr…735-7140f60.tar
-
but is it possible, that xrandr isnt a command anymore?
xrandr has never been supported on LE ARM images, at least to my knowledge. xrandr implies X11, which is not used here and it's on its way out even for Generic. Here Kodi directly interacts with DRM drivers, without any window manager in between (GBM mode).
-
I see the issue on LE 10.0.2 but not on nightly image. Curious, I'll take a look.
-
P.S. i don't have SSH access because on the Pine the Ethernet port wont work.
currently i'm using this image:
LibreELEC-A64.arm-11.0-nightly-20220413-5dcdedf-pine64
Unrelated to your reported issue, but this sounds like you have wrong image. Most probably you want pine64-plus image. Basically the only difference between these two images are ethernet port settings.
Back to your issue:
Do you have a cmdline.txt in your Pine64 file system?
cmdline.txt is RPi specific. U-Boot based images have extlinux/extlinux.conf, where kernel arguments can be added.
then you can append the needed resolution (syntax here).
While I did not try it, it should work IMO.
-
I guess I spoke too soon. Initial DRM driver landed in drm-misc and it will be in 5.19: https://cgit.freedesktop.org/drm/drm-misc/c…9a78c721b778c16
-
oddebian I tested all my interlaced videos (MPEG2 and H264) on Pine64+ and they all work. I would really need your video sample to reproduce it.
-
24 patches is a huge patch series for just one functionality and only 10 patches were acked or reviewed, so this will probably have a few more rounds before it's merged. Window for drm contributions for 5.19 is also almost over, so 5.20 at the earliest.
-
oddebian Can you dump your DVB-T stream to a file and test if offline playback also causes same issue? If it still does, please provide me that file. I have Pine64+ board and if I can reproduce your issue, debugging is much easier. I have an idea what could be the problem in the driver, but I need realiable way to reproduce it in the first place.
-
I think we should determine first if it's really thermal driver issue or is just aggressive throttling on Android that helps.
-
I think I experienced something like that on occasion on OrangePi PC2 (H5), so it could be driver issue (same driver as on A64). I'll look into it when I find time.