Posts by chewitt

Scraping content into the library creates online references to artwork in the DB, but Kodi does not download and cache the artwork from the online source until you start scrolling around in the UI triggering background downloads of original size art that must be resized and cached/stored, which is a CPU and I/O intensive task. You might have a fast internet connection, but the bottleneck for the Library views on older hardware is always I/O and CPU performance. You'll also see I/O as the bottleneck when scrolling around a large library as Kodi has to retrieve a large amount of art for display. The only way to improve this, esp. with a large library, is some kind of script/tool that walks the library and triggers all the downloads in advance (leave it running overnight, etc.) combined with an SSD to boost the I/O performance, and a skin that uses smaller artwork sizes to reduce the amount of data being moved around. If you want to run fancy skins; run fancy(er) hardware with more CPU grunt.

Option #3: https://www.amazon.ae/Cable-Compatib…/dp/B0D8M2KXZ6/ .. allows you to do things in a single step without non-standard configuration.

Option #1 .. Get an HDMI to VGA convertor cable, then VGA > Scart > Component > TV

Option #2 .. Get an HDMI to Component convertor > TV

The more physical and format conversions you use, the higher the risk of things not working right. So the desire to recycle some old connectors you have lying around in a drawer is strong, but option 2 is the better idea.

Something like this should work: https://www.amazon.ae/PARUIEN-Compon…e/dp/B0B7R5C172 and can be paired with a normal RPi micro-HDMI to HDMI cable on the input side, and you have Component RGB + 2ch audio on the output side.

If you leave music playing does it restart, or remain on a black screen?

cron doesn't run in the root user environment so $PATH is different and you should always use the /full/path/to/binary with any commands you run instead of assuming binaries are available in path.

I'm still using an Amazon essentials cable that RPi devs shipped out with the original alpha release RPi4 boards because nobody had them at the time. It works, so no need to replace it with anything fancier.

That's interesting, although from a release management perspective I would not consider switching Generic to OpenGL for LE13 for two reasons:

a) It's getting close to the likely release schedule for K22 and this is slightly exotic and thus needs proper testing on a wide range of GPU hardware (and Generic users often have older hardware).

b) It's a breaking change for Kodi binary add-ons and I'd like a release without breaking changes. In the last two releases we did Python2>3 and arm>aarch64. This time around it's stable, but we'll get enough whinging from dropping nVidia 340.108 support.

There's no issue to add another build option earlier though.

LE's installed base is roughly 80% RPi boards, 10% x86_64 hardware, and 10% other ARM boards. The x86_64 devices break down as 70% Intel, 20% AMD, 10% nVidia; most of the nVidia cards are older ones requiring VDPAU and legacy drivers, not newer ones with NVDEC. LE users mostly run Kodi to watch videos, so features like HDR playback trump shader support for games. The legacy image exists to service a handful of nVidia users and those who require a browser to access certain streams. I'm not aware that you can build mesa with OpenGL without X11, which means no HDR, and the long term goal is to bin X11 and only support GBM, and with either a GBM 'browser' or worst-case Wayland, which supports HDR, but doesn't currently support refresh rate switching which is a must-have feature for Kodi movie viewers. So right now all roads point in the direction of ```GBM/OpenGLES, not OpenGL. If it's now possible to run a GBM/OpenGL environment that would be interesting, but we'll look into that direction once there's a complelling reason; e.g. Kodi finally has Retroplayer OpenGL capabilities. It doesn't make sense for us to switch from a known/good formula unless there's demand. If you've already built Generic/OpenGL/GBM images that work? we'd have no issue with the changes being submitted to make development easier; similar to how we have options for Generic/Wayland although we don't currently build it. There's also no issue to add changes in LE that reduce downstream technical debt in Lakka, if that's at-all a related objective.

There used to be a "Plex Embedded" fork of LE run by some plex staff. Not sure it's still going though.

Quote from hbbs

Is anyone else seeing this?

Everyone running an LE13 image since https://github.com/xbmc/xbmc/pull/24899 was merged (10 months ago) sees the same. The timezone is now configured in the LE settings add-on. LE is/was kind of the 'odd one out' among Kodi platforms as the sole UI for the OS is Kodi itself. For e.g. Android, Windows macOS, and desktop Linux timezone is already configured separately in the OS.

docker run --name homepage \
  -e PUID=1000 \
  -e PGID=1000 \
  -p 3000:3000 \
  -v /storage/homepage/config:/app/config \   <= DEFINE WHERE /app/config SHOULD BE
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  --restart unless-stopped \
  ghcr.io/gethomepage/homepage:latest

Assuming I guessed the container right? (https://github.com/gethomepage/homepage) the docker run command ^ needs to define where the config location resides and this needs to be somewhere under /storage not /docker/homepage/path/to/config which doesn't exist and can't be created since almost all of the root filesystem is read-only.

NB: config.txt file is an RPi thing, but it's used for setting boot-time hardware parameters so wouldn't be of any use for this task.

Revert is merged.

2GB runs fine for a simple playback client device. If you want to run a load of container/server services in the background then 4GB or perhaps 8GB will be more suitable.

Either is fine.

No progress due to other priorities over the last week. Read: https://wiki.libreelec.tv/hardware/amlogic#install2internal

NFS shares will require you to compile a custom LE image that includes an NFS server (and we don't have a package for that in our buildsystem). LE is not a NAS distro, and we intentionally only support basic Samba shares.

One possible source of speed differences is the change from NTFS-3G (LE11) to in-kernel NTFS drivers (LE12) but in theory that should make things faster not slower. It's possible to install NTFS-3G drivers as an add-on from the LE repo and override the in-kernel driver to make a comparison.

I've been running LE13 images for the last 11 months on the family RPi5 daily-driver. The images are stable.

Windows is sometimes a bit crap with USB sticks formatted with multiple partitions. Use the "Tools" image under "Select Version" to download an image/file which will nuke the existing partitions so none exist. Once the device is blank/wiped you should be able to select the image you want and write it to the USB.