LibreELEC-RR [ Brave | Spotify | Moonlight | Emulationstation | Retroarch | Pegasus ]

    So I got the audio from the Video Snaps (Video Previews) working by RTFM PulseAudio for Video Previews but I still can't see video.

    es_settings.cfg is set not to use the OMX player

    <bool name="VideoOmxPlayer" value="false" />

    What does emulationstation use when not the omx player? (VLC? libvlc)


    I checked the codec of the snaps and they're YUV420.

    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 224x384 [SAR 9:7 DAR 3:4], 472 kb/s, 29.97 fps, 29.97 tbr, 11988 tbn, 59.94 tbc (default)


    Anyone got any pointers?

    Thanks.

    Edited once, last by kidhazy (August 9, 2021 at 1:12 PM).

    Quote from kidhazy

    ..

    I checked the codec of the snaps and they're YUV420.

    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 224x384 [SAR 9:7 DAR 3:4], 472 kb/s, 29.97 fps, 29.97 tbr, 11988 tbn, 59.94 tbc (default)

    ...

    Looks like it was format issue.

    Whilst the original video previews had been converted (about 1 year ago - ffmpeg v4.2.4) from YUV44 using "ffmpeg -i <<input_file>> -pix_fmt yuv420p <<output_file>>" resulting in format:

    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 224x384 [SAR 9:7 DAR 3:4], 472 kb/s, 29.97 fps, 29.97 tbr, 11988 tbn, 59.94 tbc (default)

    They wouldn't play.

    Reconverting the yuv444 source videos with a new install of ffmpeg v4.4 "ffmpeg -i <<input_file>> -pix_fmt yuv420p <<output_file>>" they now result in format:

    Stream #0:0(und): Video: mpeg4 (Simple Profile) (mp4v / 0x7634706D), yuv420p, 224x384 [SAR 9:7 DAR 3:4]

    This format does play under EmulationStation albeit a bit 'blockier' than the h264 format - but at least it's playing for now (I'll play around with ffmpeg to see how high I can push the resolution)

    Edit: Added the qscale option improved the quaility:

    "ffmpeg -i <<input_file>> -pix_fmt yuv420p -qscale:v 0 <<output_file>>"

    Edited once, last by kidhazy (August 10, 2021 at 5:03 AM).

    Quote from Marciano

    Hi is HDR working for gemini lake in your generics builds?

    the build from smp is the only build so far with working HDR on gemini lake and I doubt that this workaround will ever be used in an official LE build, because there is no Interlace working for PVR and other video sources.

    the only possible way is to add the changes that has smp used in the HDR build.

    I already tried it, but I wasnt even able to compile the LE-RR sucessfully because there were changes made to the code that are not in the github repo.

    • Official Post

    At some point we will dump Xorg and switch Generic to GBM/V4L2, but we're aware of a number of HDR related use-cases that still need work (in drivers and in Kodi). However the devs who've been working on this are limited in number and right now real-life is rather busy for them, and K20 is super-early in the dev cycle so we're not in a rush.

    Hi there, I tried your build and its great! I ran into one issue, when updating emulators within retroarch ( specifically the Dolphin emu ) I found that after the update it gives an error saying " unable to load libreto core "

    I checked my log and it says:

    [INFO] =================================================

    [ERROR] Failed to open libretro core: "/tmp/cores/dolphin_libretro.so"

    Error(s): liblzma.so.5: cannot open shared object file: No such file or directory

    [ERROR] Failed to open libretro core: "/tmp/cores/dolphin_libretro.so"

    [ERROR] Error(s): liblzma.so.5: cannot open shared object file: No such file or directory

    [ERROR] Failed to open libretro core: "/tmp/cores/dolphin_libretro.so"

    [ERROR] Error(s): liblzma.so.5: cannot open shared object file: No such file or directory

    Its looking for a file that is not there /usr/lib64/liblzma.so.5 isn't where it should be.

    Is there anyway to compile the new version of dolphin and create this missing file?

    NickS

    I've uploaded a new SSE4 image & it should be fixed now. I guess you're trying to load lzma compressed RVZ images?

    Quote from chewitt

    At some point we will dump Xorg and switch Generic to GBM/V4L2, but we're aware of a number of HDR related use-cases that still need work (in drivers and in Kodi). However the devs who've been working on this are limited in number and right now real-life is rather busy for them, and K20 is super-early in the dev cycle so we're not in a rush.

    Well hopefully this will mature until then WIP: unstable: add color management protocol (!14) · Merge requests · wayland / wayland-protocols · GitLab because having a full fledged wayland/weston foundation shouldn't hurt and keeps Generic builds flexible.

    Hi there,

    first of all I would like to thank you for this build. It's really nice to have moonlight-qt and xpadneo as part of libreelec.

    I have got a little problem with moonlight. On 1080@60 i noticed some flickering in the upper third of the screen, especially if there is a lot going on, if nothing happens on the screen the flickering is not noticeable. I tried with v-sync on/off and forced h.264. While v-sync seems to make no difference, forced h.264 makes the flickering worse.

    Greetings,

    Cillit

    Edit: If moonlight starts, the TV resolution switches to 4k@30, if a game stream starts the resolution still is at 4k@30, even if the streaming is set for 1080@60 inside moonlight. I have tried to force a resolution with the hdmi_mode solution mentioned in the wiki.

    Edited once, last by Cillit (August 19, 2021 at 4:21 PM).

    Quote from quro

    to be honest, I think it might be trying to use that by default, but I will try your new image, thanks for the speedy fix!

    Well since was RVZ was introduced last year Add support for the WIA and RVZ disc image formats by JosJuice · Pull Request #8538 · dolphin-emu/dolphin · GitHub I guess you've compressed your images lately? Because I use GCZ as format and had never a single problem to load any game. Anyway it should be fixed, at least I've recompressed an image & it works now.

    I guess you use a RPi4? Well I don't own one to test these boards & it might be related to [BUG] Moonlight-qt HEVC decoding on latest RPi-kernel looks tiled on Pi4 · Issue #630 · moonlight-stream/moonlight-qt · GitHub

    Anyway I guess the best solution would be to create an issue and report it straight to the moonlight-qt dev :/

    Hi Cillit, next weekend i'll test the new Build, i couldn't make it before, and give some feedback.

    Hi there,

    I don't think this is a moonlight issue. I did a little bit of research in the forum and it seems like the global resolution is now configured with cmdline.txt, which also has a new syntax. I tried different options, but had no sweeping succuess, yet.

    I tried

    Code
    video=HDMI-A-1:1920x1080@60D

    and

    Code
    drm.edid_firmware=HDMI-A-1:edid/edid-HDMI-A-1.bin video=HDMI-A-1:1920x1080D

    but it didn't work. A hint from this thread:

    Post

    RE: LE 10 RPi2 nightly: no hdmi output

    you are right. the cmdline.txt was wrong.

    i have -restarted the configuration procedure

    first i had deleted the wrong entries (this was the default entry for my rpi2)

    LibreELEC:~ # cat /flash/cmdline.txt

    boot=UUID=1107-2955 disk=UUID=27ea94ba-c897-4e07-942f-594aaf01c537 quiet

    then i had recreated the edid file

    LibreELEC:~ # getedid create

    successfully installed edid override for HDMI-A-1

    after that the cmdline was modified by the getedid command

    LibreELEC:~ # cat /flash/cmdline.txt

    boot=UUID=1107-2955…
    SB9x
    July 31, 2021 at 5:21 PM

    made me try:

    Code
    drm.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:D

    This finally worked, no more tearing and exellent streaming quality, but it killed CEC and HDMI audio, also the picture is slightly darker.

    Maybe there is a better solution.

    Edit: Yes its a Rpi4.

    Edited once, last by Cillit (August 21, 2021 at 4:13 PM).

    Quote from Cillit

    Hi there,

    I don't think this is a moonlight issue. I did a little bit of research in the forum and it seems like the global resolution is now configured with cmdline.txt, which also has a new syntax. I tried different options, but had no sweeping succuess, yet.

    Hi Cillit, i've checked, yes, you're correct, while i could follow the guide on the Wiki and force Kodi into the desired resolution, Moonlight (and probably the QT apps) doesn't respond to this forced res.
    Also can confirm on the streaming glitch.
    Didn't tried on your (somewhat) working method, and i'm short of time to try right now but you've narrow a lot of options. :-S

    Hi,

    i have done a clean install of 10RC1. I have connected a Logitech K380 Bluetooth Keyboard using "Trust and Connect".

    I found the following problems:

    - Sometimes after clicking "Trust and Connect" Kodi (not LibreELEC) performs a restart.

    - After every restart, the connection is lost until I start the discovery on the keyboard and click connect in the LibreELEC Bluetooth menu.

    - If i use "Pair" from the LibreELEC Bluetooth menu, the following window prompts me to press Keys witch aren't shown.

    I hope you can help me.

    Hendrik