Posts by popcornmix

    Running "perf top" when playing a game may be interesting.

    Wait for it to settle, and see if there's anything that shows up high on the profile.

    If you can run the same on Lakka, that would also be useful.

    hdmi_ignore_cec_init=1 is an option for the no-longer-used firmware driver, so the setting will have no effect.

    You need to edit the CEC settings (system/input/peripherals/cec) in kodi.

    Probably disable "switch source to this device on startup".

    However this may (or may not) stop the cec remote buttons from being forwarded.

    TrueHD support has been historically quite buggy in kodi. I've seen a lot of reports of glitches, hangs and crashes.

    It has recently had a rewrite: https://github.com/xbmc/xbmc/pull/24984

    It may be interesting to test a nightly build from before and after that PR was merged to see if the problem remains.

    But realistically there is no easy way of fixing bugs in the rather ancient 9.2.8 LE unless you are willing to make your own builds.

    Might be easier to stick with the working AC3 track, or transcode (perhaps to PCM) the TrueHD track if you need 7.1 output.

    It may help if you concisely explain what the current issue is (this thread has got quite long).

    My understanding is that on Pi5 in some circumstances when playing a HDR video, the display shows no signal.

    On a Pi4 with the same display and video, it plays correctly (with working hdr).

    Assuming that is the case, could you report the output of:

    kmsprint

    kmsprint -p

    for both the pi4 and pi5 when playing the video.

    1. I used to be able to adjust the width of the display on the TV screen so that the edge of the menu's, etc, all lined up nicely with the edges of the TV screen but that option seems to have disappeared in this latest version of LE. Is there some add-on I need to install?

    You really should try to solve this at the TV end. There's almost certainly a menu option to output 1:1, and the quality will be better (rather than resizing the image *twice*).

    Is this a bug, or a limitation of driver/software support as noted in the docs?

    It's a limitation. The only format that supports 10-bit output is P030 (three 10-bit pixels in a 32-bit word in a tiled format).

    P030 is native to the hevc decoder, and supported directly by the display.

    But AV1 is sw decoded, doesn't use that format, and ffmpeg doesn't support conversion to that format.

    So it uses the format it can do (8-bit YUV420).

    In theory a conversion to P030 could be written, but it would need to be written in Neon assembly to have the performance.

    OK, this is weird. I just re-installed LibreELEC on the Pi5 from scratch again, restored the config from the Pi4 and now it works as it should. WTF? There's absolutely nothing I did differently than before!

    But something strange happened: After restring the config and rebooting, the screen remained completely black but I was able to boot into LE via SSH.

    Can you be precise with the sequence here.

    1. Fresh install of LE on Pi5 from scratch works fine

    2. "restored the config from the Pi4" - did you copy .kodi directory or use an backup/restore addon? And this works fine.

    3. "After restring the config and rebooting, the screen remained completely black" do you just mean a reboot compared to the previous step, or did you restore something else?


    Assuming step 2 was working without a reboot, then kodi is likely not using the restored config.

    It may be interesting to identify what file in the config is the one that causes the issue. guisettings.xml is the most likely.

    (But I don't know if you are restoring anything else, like contents of /flash partition).

    Yes it sounds very likely the Rii X8 causes the issue, presumably because (for some reason) it reports the shift key is held down.

    It would be useful if you could confirm this.

    Boot with Rii X8 connected - does it go to installer?

    Remove Rii X8 and reboot - does it go to installer?

    I've asked the experts and the behaviour is surprising.

    One possibility is the keyboard has a stuck shift key.


    If you boot with shift key held down, you'll go straight to installer.

    Do you still have the issue with keyboard disconnected? With a different keyboard?

    This isn't really my area, but I'd imagine a USB drive that was too slow to enumerate may sometimes fail to boot and move to the next stage in booting (which may end up at the network install screen).

    That doesn't really tie in with it also happening with sdcard.

    What do you have BOOT_ORDER set to?

    Have you removed the USB drive when testing with sdcard?

    When at the network boot screen, it says "Press ESC to cancel and go to diagnostics screen" who does diagnostic screen show?

    (if keyboard is not connected on boot, I believe it goes directly to diagnostics screen).

    The crash is from:

    Code
    #0  0x0039a83c in PLT_CtrlPoint::RenewSubscriber(NPT_Reference<PLT_EventSubscriber>) ()
    #1  0x003a2d20 in PLT_CtrlPoint::DoHouseKeeping() ()
    #2  0x003a325c in PLT_CtrlPointHouseKeepingTask::DoRun() ()
    #3  0x003cbea4 in PLT_ThreadTask::Run() ()
    #4  0x00423cb0 in NPT_PosixThread::EntryPoint(void*) ()

    PLT seems to be a uPnP library, so you could try disabling it in system/services/UPnP/DLNA