Posts by HiassofT

Viewing photos seems to be a good method to fill up the thumbnails folder / texturecache - and it looks like kodi doesn't automatically garbage collect that.

I've noticed a similar situation when I last visited my parents, the thumbnails folder was at 1.4GB. They mainly view photos and use TV catchup services (ORF, Arte, ARD/ZDF tvthek addons).

Running texturecache P brought that down to a much more reasonable ~300MB and the log showed that it was mainly thumbnails from photos and those video streaming addons.

Milhouse then gave me this additional info about texturecache / thumbnails cleanup:

• texturecache.py R to remove "orphan" images from Thumbnails (ie. delete artwork from Thumbnails that is not referenced by a row in the Textures13.db database).
• texturecache.py Xd to remove Textures13.db database rows that reference non-existent Thumbnails artwork.
• texturecache.py P to "prune" the cache of all artwork which is not referenced by the media library.
• If you run all three (P, R, Xd) then that's about the best you can do to trim the fat, and fix any inconsistencies.

I ran all tree options but P was the one that helped the most (R removed some 200 Thumbnails / 5MB total).

BTW: 1GB storage is a bit small. I'd recommend using a larger partition / SD card

so long,

Hias

Quote from darksky

My goal is to build kodi on a different distro using the innovations the LibreElec team have created, for example, the HEVC support on RPi3.

These innovations / optimizations aren't from us, they come from popcornmix and other people from RPi.

If you want to build kodi and ffmpeg with all the optimizations it's probably easiest to just use his newclock5 branch (that's the current development tree). In LibreELEC we're doing the same, only difference is that we split out the ffmpeg patches to a separate package (but the changes are the same as in the newclock5 branch).

I'd recommend sticking to the tags in the repo (unless you want to track bleeding edge stuff, like in milhouse builds), in LE 8.90.005, which is based on Kodi Leia beta2, we built from this tag: newclock5_18.0b2-leia

so long,

Hias

Hyperion NG is still in a very early state and according to the maintainer the code isn't in too good shape Hyperion.NG release soon? | Hyperion - Forum

Not sure if/when there'll be a stable version available, the github repo hasn't seen any additions since December last year. GitHub - hyperion-project/hyperion.ng: PRE ALPHA - The reworked version (next generation) of Hyperion

AFAIK no one of us has tried creating an addon yet, this may change if/when a stable version of Hyperion NG is released. For now just stick to Hyperion as the readme in the Hyperion NG github repo recommends.

so long,

Hias

You can define both global defaults (in the "global" section) and window/screen specific settings (that override the defaults) in the kodi keymap.xml. See the kodi wiki for more info Keymap - Official Kodi Wiki

I'm using this in my remote.xml files to eg bring up the TV channel list when I press the "TV" button while watching live TV and then use the same button to close the list when the OSD channel list it's open:

<keymap>
  <FullscreenLiveTV>
    <remote>
      <livetv>ActivateWindow(PVROSDChannels)</livetv>
    </remote>
  </FullscreenLiveTV>
  <PVROSDChannels>
    <remote>
      <livetv>Close</livetv>
    </remote>
  </PVROSDChannels>
</keymap>

Note: this is for remotes, your (bluetooth) remote might actually act as a "keyboard".

You can use the keymap editor addon to easily assign actions, then you don't need to care about xml files or if your remote is seen as a keyboard by kodi.

so long,

Hias

To configure IR repeat settings you can use a udev rule like this - place it eg in .config/udev.rules.d/90-ir-repeat.rules

ACTION=="add", SUBSYSTEMS=="rc", SUBSYSTEM=="input", KERNEL=="event[0-9]*", RUN+="/usr/bin/ir-keytable --delay=750 --period=200 --device=$devnode"

so long,

Hias

You don't need to use the installer if you don't want to. Just download the gzip-ed image from the downloads section and then, as root, write it directly to your USB pendrive, SD card etc - but beware, don't choose the wrong device our you might nuke your harddrive

eg (replace /dev/sdh with the device node of your pendrive, SD card, ...)

zcat LibreELEC-RPi2.arm-8.90.004.img.gz > /dev/sdh

so long,

Hias

You have to install it from the LibreELEC addon repository -> VideoPlayer InputStream -> InputStream Adaptive.

so long,

Hias

RPi2 and RPi3 use the same build - the addon I linked to will be fine for you.

I tested it yesterday evening on my RPi3B+

so long,

Hias

The latest widevine needs a newer version of inputstream.adaptive (2.2.27), we fixed this last night inputstream.adaptive: update to 2.2.27 · LibreELEC/LibreELEC.tv@47767b9 · GitHub) but it could take a bit until the addon is rebuilt for all architectures and available from the LibreELEC addon repository.

In the meanwhile you can download inputstream.adaptive 2.2.27 for RPi2 from here inputstream.adaptive-2.2.27.0.zip and install it manually.

so long,

Hias

If you enable debug logging (in Settings->System->Logging) you'll see the key code received by kodi and what action it'll execute in the kodi log - just run tail -f .kodi/temp/kodi.log to see that info while testing.

You can also run evtest from the system tools addon to see the keycodes - but you have to stop kodi (and maybe also eventlircd) as they'll grab the input devices and then evtest can't show any info

systemctl stop kodi
systemctl stop eventlircd

so long,

Hias

Interesting, I hadn't noticed the "dtoverlay=hifiberry-digi" print on my PCB ("HifiBerry Digi-Pro HW 1.1") before

Adding that line won't hurt, but it doesn't seem to be needed. Just tested here on a 3B+ using LE 8.2.5 and it was detected fine, without anything added to config.txt (yesterday I tested it on a 3B using bleeding edge LE9 build with kernel 4.19-rc2).

LibreELEC (official): 8.2.5 (RPi2.arm)
le8:~ # aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HiFiBerry Digi+ Pro HiFi wm8804-spdif-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

If you can't get the card working, add the following line to config.txt:

dtdebug=1

then reboot, ssh in and post the output of the following commands

vcdbg log msg 2>&1 | paste
dmesg | paste

Then add "dtoverlay=hifiberry-digi" to config.txt (maybe it's indeed needed on some version of the card, who knows), reboot, run the two commands again and post the output as well.

so long,

Hias

The Hifiberry Digi Pro should work out of the box. It's a HAT which contains the necessary config to use it in an EEPROM - so you don't need to add anything to config.txt.

Just tested it here, on a RPi3B (non plus) and it worked fine.

If you already added anything to config.txt better remove it - it could pervent the card from working.

so long,

Hias

Which LE version are you using? LE 9 (alpha) contains significant improvements in IR remote handling that make them react a lot snappier.

If sometimes button presses aren't recognized make sure you have good IR reception - try placing the IR somewhere else - and you have fresh batteries in your remote. Worn out buttons, interference from fluorescent lights or direct sunlight, and the type of IR receiver (there are better and not so good ones) can also cause issues.

You can adjust the repeat delay (time until repeat kicks in) and repeat period ("frequency" of repeat) with the ir-keytable parameters -D (delay) and -P (period). eg add this to your autostart.sh to let repeat kick in after 750ms and then repeat 4 times a second:

ir-keytable -D 750 -P 250

so long,

Hias

Quote from novalis

Can I also use this to make this working as systemwide keyboard on Ubuntu?

Haven't tested it myself but it should work, too. You need to place the config in /etc/ then, of course.

Actually just running "sudo ir-keytable -p mce_kbd" should be enough to get input from your MCE keyboard working.

so long,

Hias

RPi2 is a bit underpowered for this job. You probably need to restrict resolution to 480p and / or maximum bandwidth to 2-3MBit/sec to get smooth playback.

With an RPi3B+ 720p Netflix streams work fine out-of-the-box. I've enabled a bit of overclocking on it as well,but mainly to get 1080p HEVC working nicely

[Pi3+]
gpu_freq=500
over_voltage=2
sdram_freq=580
over_voltage_sdram=5
sdram_schmoo=0x02000020

I wouldn't hold my breath for hardware accelerated Netflix playback on RPi, this is mainly a licensing and DRM issue.

so long,

Hias

Either buy a Synology NAS if you want something off the shelf or buy a HP Microserver and install OpenMediaVault or FreeNAS on it.

Stay away from consumer / home NAS systems, typically they have terrible software support.

so long,

Hias

Thanks a lot for the info!

CvH prepared a testbuild with (hopefully) fixed DVB driver addons: libreelec-generic.x86_64-9.0-devel-20180825192028-5069809.img.gz

Could you test with that and report back if it worked?

so long,

Hias

Thanks for the feedback! I've asked CvH , our DVB driver maintainer, to include a fix for it. I'll drop you a line when an updated build is available.

BTW: The user manual of the remote mentions that it supports various remote codes (selectable with back+number)

9364782.pdf

Could you tell use which configuration you used and post scancodes for the other remote code settings as well (if they use the rc6 protocol)? Just posting the scancode of a single button (eg "1") with the various configurations would do fine.

so long,

Hias