But it happens when i scan all the files. Now it doesn't happen when it is done.
Please be specific.
What happens when you scan all the files (crash? number of open files goes up?)
What doesn't happen? When what is done?
By scan all the files, do you mean using "Update library"?
If number of open files goes up while doing it, what is the highest number you see (and is it assigned to kodi.bin).
Does the number go down again?
The following command (run from ssh):
lsof | head -1 | awk '{ print "COUNT " $2 " " $1; }' && lsof +c 0 | awk '{ print $2 " " $1; }' | sort -rn | uniq -c | sort -rn | head -20will show which processes have files open. If there is a leak, then one process (possibly kodi.bin) is likely to be increasing regularly.
Do you see the numbers going up after a few minutes of kodi sitting idle?
Do you see the numbers going up after kodi playing a file and stopping?
There was a recent kernel fix that could be helpful here.
I think the fix is included in LE 12.0.1. Might be worth a test.
Thanks my friend. But when I play 4k remux, the libreleec outputs rgb. thats normal?
As I said
For 10-bit output at 4Kp60, it is necessary to output YCbCr 4:2:2, so we switch to that automatically.
At resolutions or refresh rates below that we will output the RGB directly.
The hdmi output varies on rgb 8bit to rgb 12bit depending on the media file (1080p sdr, 4k hdr etc).
I also have a amlogic box with coreelec, and is always displaying YCbCr 4:4:4, that is better?
No. As composition (e.g. combining subs or OSD items) happens in RGB space, there is no benefit in picture quality converting back to YCbCr before driving over hdmi.
For 10-bit output at 4Kp60, it is necessary to output YCbCr 4:2:2, so we switch to that automatically.
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=2So 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:
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.
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.
