Forget about config.txt hdmi_* settings - they apply to the old firmware display driver that is not longer used.
Your symptoms suggest an issue with the edid.
Run:
edid-decode /sys/devices/platform/gpu/drm/card0/card0-HDMI-A-1/edidand check that produces output and contains an "Audio Data Block" section. Post output here.
This would be better asked on the kodi forum, probably in the sub-forum that matches the information provider (scraper) that you are using.
I've never heard of this issue. Possibly you have some invalid/corrupt settings?
Can you try:
systemctl stop kodi
mv ~/.kodi ~/.kodi_back
systemctl start kodiand then play the file? If it doesn't help you can put thing back:
systemctl stop kodi
rm -rf ~/.kodi
mv ~/.kodi_back ~/.kodi
systemctl start kodi(or if you have a spare sdcard, just check if a clean install has the issue).
There are LE nightly Matrix builds which include some additional fixes from 10.0.2.
Giving that a test might be useful.
There are also LE 11 nightly builds which include even more changes (including a kernel bump from 5.10 to 5.15) which may be worth trying if previous build doesn't help.
If these don't help then a way of reproducing this issue more quickly would be useful.
Perhaps try with just a single video on loop. The shorter the video the better as issues tend to occur on startup/shutdown of the codec.
maybe it was fixed
Can you update to latest and test again?
I found the issue.
On LE when I run ethtool eth0 it shows its only running at 100mb and not 1000mb. While on Pi OS its running at GB speeds.
I've just booted latest nightly on Pi4.
LibreELEC:~ # uname -a
Linux LibreELEC 5.15.61 #1 SMP Thu Sep 15 23:40:51 UTC 2022 aarch64 GNU/Linux
LibreELEC:~ # ethtool eth0 | grep Speed
Speed: 1000Mb/sSo I'm not seeing the issue on my network.
There is a debug feature to force the field order:
Try running "find /sys -name field_override" to find the location of the debug node.
When video is running you can poke 8 (TB) or 9 (BT) to force the field order. e.g.
echo 8 > /sys/.../field_order
Does one of those look better than the default?
But, as Hias says, a sample file would be useful.
See: https://wiki.libreelec.tv/configuration/edid (which really needs updating for pi style gdb platforms).
As chewitt said, you want to run getedid (when display is correctly connected and powered on first).
From that point on, it can use the edid from the file if the display is not available on a subsequent boot.
Output of modetest and kodi log may be useful (you should be able to ssh in).
It may also be of interest to switch to the fkms driver.
You'll need to edit /flash/distroconfig.txt. Change:
dtoverlay=vc4-kms-v3d,cma-512
to
dtoverlay=vc4-fkms-v3d,cma-512
does it provide the live channels?
No. Just on demand.
I just tried the hotfix addon from here and it appeared to work (I just tested the first episode of A Touch of Frost and it's playing). The video is SD.
Yes, I think 1080p60 is a struggle on a Pi2.
You could try overclocking. e.g. add:
core_freq=500
h264_freq=500
over_voltage=6Does it help? You may be able to go up to 550 or 600 (but with overclocking, YMMV).
We'd need to know the format of the file you are trying to play, to know what the issue is.
1080p24 (and up to 30) with a hw decode supported codec - h264, mpeg4, mpeg2 (with licence), vc-1 (with licence) should be fine.
1080p60 may struggle (overclock can help).
Software decoded formats (including hevc) will struggle.
Post a debug log, or mediainfo of file and we can confirm.
Need to check with HiassofT. Possibly just add a way to get the 0x100 effect (probably with a better named option).
is mediainfo an addon for kodi?
You can install it on windows/linux/mac/etc
I need force_turbo because otherwise overclock is useless, because when i check the clock speed while playing videos it hovers above 900Mhz.
Assuming the videos are hw accelerated (e.g. hevc or h264) then the arm isn't used for video decoding, and there's no reason for the clock to be high. The hevc/h264 clocks will be high in this scenario.
You could always force full arm frequency without force_turbo with:
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governorBut if the hard disk isn't detected with force_turbo, then I'd say it is power supply related.
Even if drive has an external power supply, that is often just 12V for the motor, and it will still take 5V through USB.
If you have a powered usb hub then try connecting through that.
Does ARD addon use widevine? It may be suffering from [this issue]([Netflix] audio is out of sync even on sd) and need a downgrade of widevine lib.
You could try:
systemctl stop kodi
mv /storage/.kodi /storage/.kodi_back
systemctl start kodiand check if the system with the problem can now play videos (I suspect it will be able to).
If it is that suggests the problem is either settings (config files in .kodi/userdata) or addons (while I suspect you have removed addons from gui, there may be some remnants left - check in .kodi/addons).
If it's not it's something outside. It could be custom stuff you've installed (perhaps in /storage/.config).
You can laboriously go through the file system renaming files or directories to narrow down what is causing the crash, but it may be quicker just to switch to the clean LE install that works, and set that up as you like (check playback works after each addon installed or setting changed just in cases a change breaks it).
