Same as above, beside that you can try to change the video decoder to h.264 in monnlight-qt settings. Maybe the HEVC/h.265 decoder is quirky
Still testing, the default is HEVC, and yes, is all garbled, but h.264 at 1080/60 lags and insert a couple of black frames.
It's not an issue for me actually, but as i said, i'm testing.
Before i report some kind of issue, i make sure that i've tried everything i know to solve it, or at least pinpoint the problem.
I'll back to you later.
Still testing, the default is HEVC, and yes, is all garbled, but h.264 at 1080/60 lags and insert a couple of black frames.
It's not an issue for me actually, but as i said, i'm testing.
Before i report some kind of issue, i make sure that i've tried everything i know to solve it, or at least pinpoint the problem.
I'll back to you later.
Could you supply me with some logs too? I've opened an issue at the moonlight-qt repo [RPi] RPi4 video HEVC/h.265 glitches · Issue #553 · moonlight-stream/moonlight-qt · GitHub
I didn't find a specific Moonlight log file, I have its configuration file and System Log. Maybe it will help you.
Thx - all logs of my extended builds are summed in in 06_varlog.log in the logfile zip
Could you supply me with some logs too? I've opened an issue at the moonlight-qt repo
Sure, last 2 test 1080/60 H.264 and HEVC. : https://drive.google.com/file/d/1HaeHhr…iew?usp=sharing
IFAIK moonlight-qt doesn't support HEVC on the RPi4 because the HEVC decoder is stateless.
Sure, last 2 test 1080/60 H.264 and HEVC. : https://drive.google.com/file/d/1HaeHhr…iew?usp=sharing
IFAIK moonlight-qt doesn't support HEVC on the RPi4 because the HEVC decoder is stateless.
Well the RK3399 stateless decoder did not work not long ago too: [RK] SDL Error (0): Unable to open decoder for format: 1 · Issue #509 · moonlight-stream/moonlight-qt · GitHub
I've pointed the moonlight dev to the patches LE uses and he made use of them to fix this, well of course you need a patched FFmpeg version too but technically RPi should probably work if he adjusts the missing bits like he did for RK.
Beside moonlight-qt: did you run into any major isses at Emulationstation, Retroarch or Pegasus? Could you test some stuff like N64 which uses GLES? It would be interesting how fast games run, you can enable the fps counter by pressing F3 btw.
Emulationstation, Retroarch or Pegasus? Could you test some stuff like N64 which uses GLES? It would be interesting how fast games run, you can enable the fps counter by pressing F3 btw.
Well, the Super Mario 64 intro, runs at an average 45 fps, 50 highest 38 lowest.
In gameplay, as soon a Mario comes out from the pipe 38/39 fps.
No major issue, my setup is a little more complex than usual (my audio card tunneled from a WRT powered Routed with pulseaudio, took me some work).
My only problem (and unrelated to your work) is that the QT environment and Splash works at 4096*2160 my TV is 3840*2160, and i lose the sides, probably got to edit the config.txt to force a hdmi mode.
Besides that, all is well.
I'll repeat myself, GREAT WORK.
Please tell me if you need something else tested.
Since you've mentioned it, could you run Retroarch with ALSA backend configured in settings addon & use alsathread instead of alsa as audio driver?
I want to know if I could get rid of this:
Hi, with alsa in RR Configuration, and alsathread in Retroarch i've got sound.
so please test again and send me the log files for h.264 & hevc/h.265 so I can pass them cgutman (the moonlight dev).
Here you have: H.264, 1080p/60 a couple of seconds ok, and the a few black frames, HEVC completly black screen.
https://drive.google.com/file/d/1oGaNcN…iew?usp=sharing
I've overhauled the package and it should now grab cores for ARMv7 with NEON extensions
I got the same behavior as before.
ElBoluTony you probably know how to run custom scripts & use the terminal? If so then I would use as pro guinea pig 
Beside that the core list should be the same but the cores are compiled for ARMv7 + NEON now which should speed things up in case someone wants to pull in buildbot stuff. Even though it's more useful for cores not included in my builds, the included ones should be at least as fast if not faster since they are build with optimised build flags matching the platform/device.
you probably know how to run custom scripts & use the terminal?
Yes!
Yes!
Perfect! So could you download & unzip those scripts on your RPi?
Then stop Kodi by kodictrl --stop & run them?
each scripts sets flags according to [RPi] RPi4 video HEVC/h.265 glitches · Issue #553 · moonlight-stream/moonlight-qt · GitHub before it starts moonlight.
Perfect! So could you download & unzip those scripts on your RPi?
Log: https://drive.google.com/file/d/1NQwofH…iew?usp=sharing
The files DFD1 got a typo at line 27.
export DRM_FORCE_DIRECT=0
So, the files are equal, i modified it, the last run is with "export DRM_FORCE_DIRECT=1", and HEVC show a picture!!
Bravo!!
Imgur: The magic of the Internet
Niceeeeee, now is to do some tests.
Hi SupervisedThinking
I really look forward to give this a try! Appreciate your efforts very much.
As upgrading an existing 9.x is not recommended... Could a fresh install and restore the 9.x backup work out? Reason is that I'd like to continue to run TVheadend and Hyperion.ng.
Thanks!
LibreELEC-RPi4.arm-10.0-RR-20210322-9a4d199.img.gz is online & export DRM_FORCE_DIRECT=1 was added to the moonlight-qt start script for RPi4 builds.
Tested it, Moonlight-QT works with HEVC out of the box!
Great job.
Bub4 tvheadend should work flawless, I've upgraded my old 9.x build too with one of my images but that said I'm the one to face the music on my system 
A clean installation and restore should work fine as long as the addons come from official repos which offer Python3 compatible versions. The main reason why I recommend a clean install is that a lot of config files I provide have been updated, also config paths, symlinks... else & old version will interfere with that. Also you can only update old LE-RR builds because they have a partition size of 1024MB. But as I said this will lead to serious problems unless you're not in mood to dig through roughly 1000 commits of changes.
CvH any news about Hyperion.ng? Wasn't it somehow broken?
