Posts by HiassofT

Or install LE13 and use one of the browser addons to stream from the website - you'll need a keyboard and mouse though.

so long,

Hias

v22 is now available in our LE12/12.2/13 repos

so long,

Hias

v22 should be in our repo in the next few days, PRs are already merged

hyperhdr: update to 22.0.0.0 by HiassofT · Pull Request #11731 · LibreELEC/LibreELEC.tv

github.com

so long,

Hias

Use the TVDB v4 addon: https://kodi.wiki/view/Add-on:The_TVDB_v4

so long,

Hias

LE12.2 ships with the 575 series driver, which means Geforce series 700 up to RTX series 40 (RTX 50 series isn't supported as it would need a different kernel driver).

See the supported product list on the nvidia site: https://www.nvidia.com/en-us/drivers/details/250991/

LE13 ships the 580 series driver, which supports about the same cards:

Driver Details | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>

www.nvidia.com

Kodi doesn't support nvdec so video decoding support on LE13 is quite limited.

In general I'd recommend staying away from nvidia, you'll get a better experience with Intel/AMD (even on-board) - or use something like the Raspberry Pi 5.

so long,

Hias

Set the THREADCOUNT environment variable.

As a rule of thumb building LLVM needs about 1GB RAM per thread.

so long,

Hias

Quote from johnny depp

Hi there, I’ve got a question about the new option:

That's a kodi bug, the monitor selection should only be shown if you have multiple monitors connected.

I've opened a PR to fix that: https://github.com/xbmc/xbmc/pull/29073

so long,

Hias

You seem to be missing the closing </FullscreenVideo> tag between </keyboard> and </keymap>

so long,

Hias.

IIRC Kodi's libinput keyboard handler doesn't handle BTN_ input events. Maybe a game controller addon might help, but that's not exactly my area - might be best to ask on the kodi forum.

As a workaround you could remap the BTN_ events using a hwdb file - see eg here: RE: [RPi3] OK Button doesn't work on H1 Remote

so long,

Hias

Quick heads up:

Google finally released Chrome for 64bit ARM and it's now available in our addon repo.

It should also support widevine (usually it's installed via chrome's component updates) so Netflix etc should work with it, too.

If you update Chromium (use the update function of the Flatpak addon) you should also be able to get widevine working.

I haven't been able to verify that myself (as I'm currently away from home), but in the past widevine was installed when you first visited a (streaming-) site that required DRM and then you needed to restart Chrome/Chromium to actually get it working - so try that, too, if it doesn't work at first try.

so long,

Hias

If you plan to use any 4k media stay away from the 1GB models.

Kodi can easily run into out-of-memory with 1GB just by scrolling through a (new) library when it generates thumbnails on-the-fly in the background and some files might not play at all with just 1GB.

so long,

Hias

No.

See also here RE: Nightly Builds

so long,

Hias

The updated externalhelper addon (12.80.7.9) is now available in our repo.

Please give it a try and report back if it works - if it doesn't please post a pastekodi log.

so long,

Hias

Thanks for the log!

Yes, the libdisplay-info update was the culprit, we need to roll out a new externalhelper addon version since the current version (more precisely libwlroots) still links against the old libdisplay-info library.

I've opened a PR https://github.com/LibreELEC/LibreELEC.tv/pull/11638, the new tools.externalhelper addon should appear on our servers in the next day or two.

so long,

Hias

Please post logs, start a flatpak addon and then run "pastekodi" and post the URL.

Also please try with older versions of the flatpak addon and report back which ones work and which don't.

so long,

Hias

Quote from VLouis

My questiuon would be: exist any alternative (simple) way to find the "key id" for different remote buttons?

The easiest way is to enable debug logging in kodi and then watch the kodi log, using tail -f .kodi/temp/kodi.log and look for the HandleKey lines while you press the remote buttons.

You'll see lines like this:

debug <general>: bool CInputManager::HandleKey(const CKey&): volume_mute (0xf0b7) pressed, window 10000, action is Mute

In this case the mute button was pressed, volume_mute would be the kodi keyname to use in keyboard.xml and 0xf0b7 is the kodi key id in hex.

In your case the keyname would be "dvd" so you could also just use

<dvd>System.Exec...</dvd>

in keyboard xml - that's a bit easier to read and understand than key id="61692"

so long,

Hias

Quote from HiassofT

If you get "double button presses" from CEC then try increasing the Remote button double press timeout setting, eg to 30 or 50ms - that can be needed on some buggy TVs.

Checking through the libcec issues I noticed you might need to set that to even higher values like 200 or 250ms - just check what works best for you.

so long,

Hias

johnny depp the two CEC adapters are expected and kodi now supports separate configuration of both.

If you have CEC issues make sure you start with clean settings, whatever you changed before in CEC settings may now interfere.

Stop kodi, remove the old CEC settings and reboot:

systemctl stop kodi
rm /storage/.kodi/userdata/peripheral_data/cec*
reboot

If you get "double button presses" from CEC then try increasing the Remote button double press timeout setting, eg to 30 or 50ms - that can be needed on some buggy TVs.

so long,

Hias