The MPD add-on is probably just compiled to deliver IP port binding.
Posts by Da Flex
-
-
Usually 127.0.0.1 is the right address for local host.
-
You can also change the firmware on LE, but it's easier on Raspbian. After changing the firmware, you can insert your LE card and instantly use it (firmware is at the chip).
-
At the 2GB variant, this result was expected. I guess the data bus is too slow for 60Hz plus AAC audio at the moment. Wait for optimization updates.
-
I never heard about channel mapping on LE. You had a working system before your microSD died, so I think it's not a driver issue.
Because you have another HiFIBerry card, we can rule out a HiFiBerry firmware issue.
On the other hand, the RPi has it's own firmware, too. LE installs the right firmware, but maybe something broke while your microSD died.
My suggestion: Take another microSD, install Raspbian, and if Raspbian also has channel issues, try different RPi firmware on Raspbian.
-
I understand if this openelec build is a POS, but am I doing something wrong, here?
Yeah, you did something wrong, because this forum is about LE, not OE. So please stop asking for OE things.
-
This is unusual, and I suggest to provide a link to a complete kodi.log.
To rule out a hardware defect, you can also try a different OS, like Raspbian.
-
Always use the search function before starting a new thread: Click.
-
OK, then I don't have a clue how to restore that. The cache folders content is all, what can be deleted without a doubt.
-
This one:
LibreELEC-RPi4.arm-9.80-nightly-20201106-9862821.img.gz
-
kaputnik Thanks. Dev's will have a look at this, soon (maybe wrong RPi4B compiler flag).
-
-
You haven't described which folders content you've been deleted. If you delete the content of /storage/.cache, then it maybe updates time.
-
Just on GUI, or on terminal (ls -l) as well?
-
Sad to hear.

Because Pulse Audio is mainly for Bluetooth on LE, you could try some Bluetooth add-on's. Maybe one of them is able to store the volume setting.
-
Read here about TVDB scraper.
Because it's a different issue, and the original issue has been solved, I close this thread.
-
Yeah, Docker is your solution: Click.
-
You could check whether the network controller chip (?) is supported by Linux, before you buy.
PS: I've seen Linux support at your link, so this part is OK.
