Posts by Da Flex

Thanks for the video. It makes me think that the DB is not the problem. Instead the LE player loads different data from the DB (cast, no cast), depending on where it's started from. So this time my advice is to write a bug report for the LE player, not for the DB add-on.

Quote from fr1day

The one thing I do know is that my issue with sound existed before that block was added, as I've had the same issue with sound since I did a clean install.

I would try a fresh install on an external drive anyway (USB stick). A/V latency can be the cause of your issue.

Remove this block from your advancedsettings.xml:

<video>
    <latency>
        <delay>0</delay>
        <refresh>
            <min>23</min>
            <max>24</max>
            <delay>175</delay>
        </refresh>
    </latency>
</video>

I assume you're using an RPi 4B. On that device you can't do this. HDMI1 is for dual-screen mode only. If you need an additional digital audio output, go for an HDMI audio extractor.

chewitt Can we do a device list, updated by users? Something like an initial post by an admin (like me ), and all users can post answers, which devices work for them. Then the admin will add the device to the list at the initial post (device name, chipset, LE version, hardware, user name), and deletes the users post after this.

PS: It's really hard (impossible?) to find a 5GHz device, which is not from Realtek. Many users have this problem.

advancedsettings.xml has some features to play with. I just have no clue if it affects your issue.

A pretty rare solution. Thanks for sharing it!

LE uses it's own add-on system to install packages. APT is not supported. Fortunately you don't need APT or an install script for this project.

• install the "Raspberry Pi Tools" add-on (provides Python GPIO lib)
• create the folder /storage/.kodi/userdata/scripts
  
• insert this lines between line 4 and 5 of softshut.py:

import sys
sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib')

• put softshut.py into /storage/.kodi/userdata/scripts
  
• create /storage/.config/autostart.sh with this content:

#!/bin/sh

(
    python /storage/.kodi/userdata/scripts/softshut.py
) &

Some advanced users run GParted to format the card by leaving out bad blocks. That's an option to keep it alive, if you invest the effort.

HiassofT You've been answered faster, that's why I double-posted the same facts.

There is no need to extract the image by yourself. Just let the update script do the job. It updates some files. It doesn't installs the complete tar for the Linux partition. All unneeded data will be deleted after the update. At the end you'll get the same result like on GUI update.

Quote from wylda

But when i compared the image file with KODI log, i wonder, why GUI uses TAR archive instead of above image file??

The image file contains data for two partitions. The tar file is the one that contains the update for the Linux partition. The data for the Windows partition isn't needed in your case, because you don't install LE from scratch.

Add this line to config.txt:

hdmi_force_hotplug=1

PS: I'm not sure whether the buggy kodi.log is related to your issue. The cause of your issue could also be a lack of hardware performance. Do you have options to overclock your device? Read here about HEVC and overclocking on RPi.

INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/confmisc.c:767:(parse_card) cannot find card '$CARD'
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4568:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/confmisc.c:392:(snd_func_concat) error evaluating strings
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4568:(_snd_config_evaluate) function snd_func_concat returned error: No such device
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/confmisc.c:1246:(snd_func_refer) error evaluating name
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4568:(_snd_config_evaluate) function snd_func_refer returned error: No such device
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:5047:(snd_config_expand) Evaluate error: No such device
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:5014:(snd_config_expand) Unknown parameters CARD=HDMI,DEV=0
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:5014:(snd_config_expand) Unknown parameters CARD=HDMI
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4898:(parse_args) Unknown parameter DEV
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:5031:(snd_config_expand) Parse arguments error: No such file or directory
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4898:(parse_args) Unknown parameter DEV

That looks buggy to me.

I've been moved this into our showcase section, because many users had trouble to multi-boot LE. Grub2Win is a nice solution.

Your original thread title was too long, so I was cutting it. You said the boot error appears since your Windows update.

Go into your EFI / BIOS settings and check the boot order of partitions. Some Windows updates change it, but that's not our fault.

pspablo_pl Please edit your post. Only English language is allowed.

PS: Thanks.