Posts by popcornmix

Some info from here:

$ grep -A9 HDMI-A-1 /sys/kernel/debug/dri/?/state
connector[33]: HDMI-A-1
    crtc=crtc-2
    self_refresh_aware=0
    max_requested_bpc=8
    colorspace=Default
    broadcast_rgb=Automatic
    is_limited_range=y
    output_bpc=8
    output_format=RGB
    tmds_char_rate=74250000
$ kmsprint -p | grep -A 14 HDMI-A-1
Connector 0 (33) HDMI-A-1 (connected)
   EDID (1) = blob-id 300 len 256 (immutable)
   DPMS (2) = 0 (On) [On=0|Standby=1|Suspend=2|Off=3]
   TILE (4) = blob-id 0 (immutable)
   link-status (5) = 0 (Good) [Good=0|Bad=1]
   non-desktop (6) = 0 [0 - 1] (immutable)
   HDR_OUTPUT_METADATA (7) = blob-id 0
   CRTC_ID (20) = object id 87
   max bpc (34) = 8 [8 - 12]
   left margin (35) = 0 [0 - 100]
   right margin (36) = 0 [0 - 100]
   top margin (37) = 0 [0 - 100]
   bottom margin (38) = 0 [0 - 100]
   Colorspace (39) = 0 (Default) [Default=0|SMPTE_170M_YCC=1|BT709_YCC=2|XVYCC_601=3|XVYCC_709=4|SYCC_601=5|opYCC_601=6|opRGB=7|BT2020_CYCC=8|BT2020_RGB=9|BT2020_YCC=10|DCI-P3_RGB_D65=11|DCI-P3_RGB_Theater=12]
   Broadcast RGB (40) = 0 (Automatic) [Automatic=0|Full=1|Limited 16:235=2

Quote from Schorsch33

So alltogether I agree that it is a networking problem, but it seems to be caused by libreelec. Any ideas?

Start with the basics. run iperf (or iperf3) on your smb server. Run iperf/iperf3 on libreelec pi.

Check the speed.

iperf is in the Network Tools addon.

Looks like you are playing the file from a smb share?

To rule out a network issue, can you try playing the same file locally?

(e.g. copy it to sdcard or a usb drive and see if plays smoothly from there).

We are spending nearly half the time in KODI::RETRO::CDeltaPairMemoryStream::SubmitFrameInternal.

That seems to be used by the "rewind" feature. Disable it:

https://kodi.wiki/view/HOW-TO:Fix_Games_Runing_Slow_in_Kodi

Quote from libelle

last week my system started to crash more or less often at different occasions. It just suddenly shows a square filled with rainbow colors for a second before it's restarting itself to the startscreen.
...

System: LibreElec 12, Raspberry Pi 3 Model B Plus Rev 1.4, with 32 GB SD-card, Estuary Skin, USB dongle for remote control, and for a kind of power on/off button I connected a button to PIN 5+6 (GPIO3+GND) and added dtoverlay=gpio-shutdown to /flash/config.txt (after mount -o remount,rw /flash of course) and added autostart.sh and autostop.sh to .config. Can't think of anything else right now, but willing to provide anything needed.

The rainbow square shows you've had a reboot, rather than a crash.

That is actually pretty rare. It means something has intentionally requested a reboot or there has been a significant power failure.

I'd be suspicious of the power switch and gpio-shutdown overlay - can you remove those and see if there's any change?

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.

See here.

TLDR: adding vc4.force_hotplug=1 to cmdline.txt (on existing line) will probably avoid the unwanted behaviour.

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.

Quote from Billzilla

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*).

Quote from Cabal

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.

Quote from BallerShotCaller

The really strange thing is that 1080p@60Hz does not work anymore now. When I set the default UI setting to 1080p@60Hz, the screen goes black until the resolution goes back to 4K automatically again after confirmation time is up.

When it is set to 1080p60 (and is not showing an image), can you report output of kmsprint?

(execute that through ssh).

HDMI port closest to power connector on Pi4/5 is the primary one, and should be used when only using one display.

Quote from BallerShotCaller

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).

Did you try on RPi OS? Did you have the same issue?

The crashes are in python, so it's an addon:

#0  0x0000007f8711918c in ?? () from /usr/lib/libpython3.11.so.1.0

The last line in the log is usually:

2024-05-15 05:26:12.617 T:1766546    info <general>: WEATHER: Downloading weather

so I'd start with disabling the weather addon.

Can you compare the messages in dmesg when plugging in the three tuners on both the Pi4 and Pi5.

If there are some error messages only on the Pi5 then that may help narrow it down.