Posts by chewitt

LE packages Kodi to use ffmpeg libraries so there is no ffmpeg binary in the default OS image. We also package a normal binary version of ffmpeg in the ffmpeg-tools add-on. This is compiled with more options enabled to make it more suitable for use with other apps.

Use a decent router with a proper firewall (maybe even threat protection built-in) to protect the TVH server behind it, and port-map from non-standard ports on the router WAN IP (obscurity not security, but avoids some probing) to the standard ports on the TVH server. I wouldn't bother with VPN as TVH provides access to public broadcast video streams not personal data.

KVIM is a legacy image for VIM1 only. The add-on errors are likely caused by the Python2 to Python3 change in Kodi v19 - you'll probably need to remove all add-ons and reinstall them with K19 compatible versions. Once an add-on is reinstalled you can probably copy the config back to preserve settings. The fun thing is .. not all add-ons will be available in Python3 versions yet.

Initial WireGuard support has been merged but I regard it as an experimental feature. It's merged to LE master branch, also to LE 9.2 branch as more people are likely to use it there and thus more issues will be discovered. I will need to bump connman and the wireguard module/tools packages before we release LE 9.2.1 (no schedule).

There is no wg-quick or wg0.conf due to the embedded packaging of LE - read Creating WireGuard Keys [LibreELEC.wiki] to understand how it's implemented.

Most nVidia GPUs suffer from under-development on closed-source VDPAU so even if the card is vastly superior in mathematical compute capabilities it may not necessarily be any better than the Intel GPU which is still capable of hardware accelerating the same range of media. Kodi is not a complex OpenGL app, so it doesn't really need or benefit from high-end GPUs.

macOS stuff is the main hold-up as I understand it ..

Three suggestions that might work:

a) Enable "legacy boot" in BIOS settings which should disable EFI boot.

b) Boot from any other Linux distro USB and run "dd if=/path/to/LibreELEC-Generic.x86_64-9.0.2.img of=/dev/sda bs=1M" (checking the disk you want to write to is /dev/sda .. and noting the image is uncompressed to .img not .img.gz). This writes the USB image to the HDD, and in theory this should boot, time out the same way, but this time it self-installs to the HDD not the USB so you end up with a working install.

c) Remove the HDD and put it in a USB caddy to write the image to the HDD .. different way to the same result as B.

A is easier than B which is marginally more complex but requires no extra hardware like C

RPi4 haardware is capable of HDR but LE (and all other RPi distros) have no "software" support for HDR at the current time. It's still being worked on and might part of the future LE10 (Kodi v19) release if things keep going at the current rate of progress. No promises though.

It's sounds like the device is EFI booting and ends up following the "run" configuration (not sure how or why.. that's the only explanation). I've observed that EFI support tends to get worse the older machines are .. maybe that's the reason.

Anyway .. what happens when you type "installer" instead of leaving it alone?

I haven't used Amlogic BSP kernel images on anything since ~November 2018 so I have no idea, sorry.

Kodi outputs progressive and interlaced media output is faked, e.g. 1080i@25 (typical PAL content) will be output as 1080p@50 (one interlaced frame per refresh, so double the number of interlaced frames). This means even if it can see 1080i in the list, it will choose 720p as the desktop resolution. I forget how things have evolved over Kodi releases, but IIRC this has been the behaviour for some time but older releases wrongly reported things so people believe they were using 1080i desktop in the past when they weren't.

It should be in Kodi v18.6 when that ships (no ETA at the moment).

Английский язык пожалуйста

The commit message is misleadingly worded. VP9 and HEVC share some common pluming which is provided by that commiit. In the same series you also have the full VP9 decoder. HEVC is still missing from the line-up. We are now in the odd situation of having the firmware that was missing a few months ago, but now the driver is absent. Previous patches that added HEVC support are not aligned to the updated firmware and recent compliance changes in APIs .. so rework is needed. Google (who is funding most of the current development) cares most about H264 and VP9 so those are being done first (annoyingly).

Kodi sucks a bit at presenting games, there is still no database to store the configuration needed for a specific game rom. In short, Emulators are just background plumbing and are not the thing you navigate from. You need to start from a game rom, then you're prompted for the Emulator to use with that rom. Then the game launches. This is where add-ons like "Internet Archive Game Launcher" are useful, because they create the searchable front-end interface to navigate from. The only games that will show up under "Home > Games" are games that are natively compiled to run on the host platorm (no emulator involved) e.g. 2048 and the Bomberman clone in our game repo.

mkdir -p /storage/.config/firmware/mediatek
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/mt7610u.bin -O /storage/.config/firmware/mediatek/mt7610u.bin
reboot

^ run those commands (mind the line-wrap on wget) .. working?

"GUI at 1080p" means leave (or set) the default resolution to 1080p.

LMGTFY