Posts by HiassofT

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

It's just for testing. Please try to disable it and check if you get proper scancodes with ir-keytable -t / evtest.

I suspect that patch from LE could be missing in the CrazyCat addon. If that's the case I'd like to write a proper patch for the issue which I can send upstream and include both in LE base kernel and the CrazyCat drivers (the patch in LE is not good and needed fixing for a long time).

so long,

Hias

Do you have any of the DVB driver addons enabled? If yes, which one and does the issue also occur if you disable it?

so long,

Hias

Which platform / build and which of IR receiver are you using? Please upload your dmesg output

dmesg | paste

The xxxx8xxx/xxxx0xxx scancode change you are seeing is the toggle bit (it flips if you release a button and then press it again).

But this is quite odd, LE kernel contains a patch that enables the toggle bit on all RC6 protocol variants, not only on the original Microsoft MCE. So you should never get a xxxx8xxx scancode, only xxxx0xxx ones...

linux-057-removed-mce-customer-code-restriction-in-rc6-decode.patch

so long,

Hias

It may be worth giving the current LE9 alpha version (8.90.003) or a current Milhouse build (see LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) ) a try.

Quite a lot of ethernet and Wifi fixes for the RPi3B+ are included in these builds that are not in 8.2.5.

Also test the network performance (using iperf3 from the network-tools addon and a iperf3 client on some other box in your LAN), DLAN / powerline adapters can be problematic as well. Test with a "real" ethernet connection (ethernet cables and a switch) to see if this is an issue.

I can't comment on UPNP / DLNA, never used this.

so long,

Hias

ffmpeg HEVC optimization patches are included in LE master tree, what's currently missing in LE master tree are the kodi patches needed to use these.

so long,

Hias

I haven't used the keymap editor for ages so don't know if it's working or if it maybe has some issues.

Mapping remote buttons via a remote.xml file in /storage/.kodi/userdata/keymaps/ is working fine though.

Here's the remote.xml I'm using for my Hauppauge remote. I've remapped the power button to show the shutdown dialog window so my RPi doesn't unconditionally shut down if I accidentally press it.

 <keymap>
  <global>
    <remote>
      <power>ActivateWindow(ShutdownMenu)</power>
    </remote>
  </global>
  <FullscreenVideo>
    <remote>
      <red>AudioNextLanguage</red>
      <blue>ActivateWindow(SubtitleSearch)</blue>
      <green>SubtitleDelayMinus</green>
      <yellow>SubtitleDelayPlus</yellow>
      <star>ActivateWindow(Teletext)</star>
      <hash>NextSubtitle</hash>
    </remote>
  </FullscreenVideo>
  <FullscreenLiveTV>
    <remote>
      <livetv>ActivateWindow(PVROSDChannels)</livetv>
      <guide>ActivateWindow(PVRChannelGuide)</guide>
    </remote>
  </FullscreenLiveTV>
  <PVROSDChannels>
    <remote>
      <left>PreviousChannelGroup</left>
      <right>NextChannelGroup</right>
      <reverse>PreviousChannelGroup</reverse>
      <forward>NextChannelGroup</forward>
      <livetv>Close</livetv>
    </remote>
  </PVROSDChannels>
  <TVChannels>
    <remote>
      <reverse>PreviousChannelGroup</reverse>
      <forward>NextChannelGroup</forward>
      <livetv>Menu</livetv>
      <red>Container.NextViewMode</red>
    </remote>
  </TVChannels>
  <TVGuide>
    <remote>
      <reverse>PreviousChannelGroup</reverse>
      <forward>NextChannelGroup</forward>
      <guide>Menu</guide>
      <red>Container.SetViewMode(10)</red>
      <green>Container.SetViewMode(11)</green>
      <yellow>Container.SetViewMode(12)</yellow>
    </remote>
  </TVGuide>
  <Teletext>
    <remote>
      <star>Back</star>
    </remote>
  </Teletext>
</keymap>

Enable debug logging in kodi and watch the kodi log with tail -f .kodi/temp/kodi.log while you press buttons to see which buttons are mapped to which keynames ("power", "red", "forward", ..).

The available actions and general info about remote/keyboard mapping are described in the kodi wiki Keymap - Official Kodi Wiki

so long,

Hias

Update to LE 8.2.5 and remove your banned addons / repositories. I'd recommend doing a clean LE 8.2.5 installation and check if it works there.

Edit: also make sure Lirc is disabled in LE settings.

so long,

Hias

With LE9 you can just put a lircd.conf file in /storage/.config/ and then reboot. in LE 8.2 you have to enable Lirc in LE settings.

But I recommend following the wiki guide and create an ir-keytable configuration, this is the modern standard in Linux and more flexible and hassle-free. Only use lirc if you have an odd remote that is not supported yet by ir-keytable.

so long,

Hias

The hardware is identical for all RPis, just buy a TSOP34448 and connect it to the GPIO pins.

Then add "dtoverlay=gpio-ir" to config.txt to enable the Linux IR driver.

Read through this wiki page Infrared Remotes [LibreELEC.wiki] for info on how to configure the system for your particular remote.

so long,

Hias