PS: If a device can route its own input signal to the output, then it's called "loopback functionality" or "direct monitoring". Because your audio interface doesn't have buttons for that, only software switches are possible.
If your audio interface has loopback, then software switches are part of the driver, and you should see them at LE audio settings.
I don't think so. LE has no customizable audio routing or mixing capabilities.
Most people use an AVR to connect multiple audio sources. Your audio interface is some sort of an AVR, but it misses the input selector. Ask the manufacturer, how to do that. I'm sceptical, because it's dirt cheap.
jgregg You can use that tar file to update from SSH:
cd /storage/.update
wget https://chewitt.libreelec.tv/testing/LibreELEC-gbm.x86_64-12.80.0.tar
rebootYou have the Trakt add-on installed. There is a chance that Trakt is blocking your file transfer due to Trakt synchronization.
Disable Trakt for a test.
fliz You're right, the PSU is fine.
I think it's a problem with wrong RPi firmware (unknown/new hardware revision on RPi5):
Mar 24 02:45:55.807760 LibreELEC kernel: rp1-pio 1f00178000.pio: error -ENOENT: failed to contact RP1 firmware
Mar 24 02:45:55.807790 LibreELEC kernel: rp1-pio: probe of 1f00178000.pio failed with error -2
...
Mar 24 02:45:55.817716 LibreELEC kernel: rp1-firmware: probe of rp1_firmware failed with error -110Try the latest LE 13 nightly.
Use JSON-RPC or kodi-send.
force_eeprom_read=0
dtoverlay=hifiberry-digi
Those two lines should do it. Try latest LE 13 nightly (download section).
Could be an undervoltage issue. Post a log to be sure.
The configuration concept of LE is to have default files for settings. They are read-only. To edit one of them, you have to create another file on a different location. That file will then overwrite the settings of the default file.
In your case, create a /storage/.kodi/userdata/advancedsettings.xml file.
Better ask at Kodi forum. LE devs are not responsible for this code.
If "reboot" command works from SSH, then it's probably just a configuration issue.
If I grab a modern pci-e card is it likely to just work?
If it's too modern, then it might fails. Something like Intel AX200 should work:
https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html#primary-content
We don't have a whitelist for WiFi dongles. If a WiFi dongle works on other Linux distributions, then our devs often find a way to import the driver.
So if you want to spend more time, try the dongle on other Linux OS, like Ubuntu.
If you want to buy something new, get an Ethernet-to-WiFi adapter. The Ethernet driver is universal, and just works.
Looking over the code, I do not think those settings should have an impact. Visualizations are essentially a secondary sink at a fixed 44.1khz, with the audio buffer being resampled if required.
I think you're right. After looking at x86-64 and RPi crash logs again, both have segmentation faults:
Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --audio-backend=alsa+pulseaudio'.
Program terminated with signal SIGSEGV, Segmentation fault.So probably the memory stack of the audio was corrupted by bad MP3, and later GUI sounds lead to a crash on RPi.
If i disable crossfade my Kodi does not crash immediately on end of crashsong but if i press some keys after it played and navigate e.g. to main menu then Kodi crashes and restarts.
And that i can reproduce on my x86 AND on Raspy3 V2.
Please post the crash log from RPi. What's your audio output device?
Since nobody can reproduce the issue, smf007 is maybe on the right track.
When something complex just works on LE, then it's truly a miracle. 
Yes, Anynet+ is HDMI-CEC, and commands go from TV to RPi.
That log isn't helpful.
