Posts by HiassofT

  • Configuring IR Remote that is supplied with tt-4600 tuner

    Sorry for using too technical terms, the simple version is: the remote is queried only 4 times a second on your DVB dongle and that results in it being sluggish (there's probably not much we can do about that) and the repeat issues (that's a problem with all current kernels and I'll look into finding a solution - could be a bit tricky and may take some time).

    As for remotes: I'd recommend using an official (or fully compatible like the HP branded ones) MCE remote together with the HP branded USB MCE IR receiver from ebay for about 15-20 EUR shipped. Official MCE remotes are the ones best supported in Linux and LibreELEC and the HP USB IR receiver works very well too and can be used with all kinds of other remotes as well - I have these here and regularly test with them.

    Be careful when searching for MCE remotes on ebay or other shopping sites, there are a lot remotes advertised as "MCE" that don't follow the rc-6 MCE protocol. Same thing applies for "MCE USB IR receivers", some of them, like the cheap TopSeed receivers that are often advertised on ebay, have nasty bugs - better stay away from them and go for the known-good HP branded one.

    Another cheap and very versatile option on RPi is to connect a TSOP 34138 IR receiver to the GPIO pins. For about 1-2 EUR/USD you'll have a full-fledged IR receiver that's very well supported in Linux/LibreELEC. This is what I'm using on my main RPi. The only gotcha is that some USB DVB dongles seem to interfere with it (low-level timing issues caused by the RPi's USB driver) - I haven't experienced such issues myself and also don't know if you'd be affected by that or not.

    so long,

    Hias

  • Configuring IR Remote that is supplied with tt-4600 tuner

    Thanks a lot for testing!

    I added this kernel patch to set the timeout to the poll interval - basically the same thing that ir-ctl -t would have done (sorry, forgot that the timeout can't be configured on all devices)

    Diff
    --- a/drivers/media/usb/dvb-usb/dvb-usb-remote.c
+++ b/drivers/media/usb/dvb-usb/dvb-usb-remote.c
@@ -285,6 +285,7 @@ static int rc_core_dvb_usb_remote_init(struct dvb_usb_device *d)
     dev->dev.parent = &d->udev->dev;
     dev->priv = d;
     dev->scancode_mask = d->props.rc.core.scancode_mask;
+    dev->timeout = MS_TO_NS(d->props.rc.core.rc_interval);
 
     err = rc_register_device(dev);
     if (err < 0) {

    Here's the LibreELEC tree I built from: GitHub - HiassofT/LibreELEC.tv at le9-dvb-usb-ir-repeat

    This patch was just a quick test to see if it helps on your receiver, in it's current state it will break IR remotes on dvb-usb remotes with long query interval (there are some that query every 400ms or even only once per second).

    I'll have a look at that and should hopefully come up with a proper patch that I can also send upstream. BTW: the sluggishness comes from the 250ms query interval, you'll get a lot better performance from a standard MCE USB receiver or a GPIO receiver on an RPi. Quite a lot of dvb-usb dongles seem to use a 50ms remote query interval, with these the remote should be quite snappy and not suffer from the repeat issues you had, even on stock kernels.

    I can't comment on the tuner crashes, this isn't my area, maybe CvH can help there.

    so long,

    Hias

  • Configuring IR Remote that is supplied with tt-4600 tuner

    Hmmm, the remote doesn't seem to follow the rc5 protocol too well - or there's some bug in the IR receiver driver of your card that then causes rc-5 decoding in the kernel to fail.

    On quickly repeated button presses you should see the toggle bit flipping instead of getting different scancodes for the same button. eg

    Code
    799.923295: lirc protocol(rc5): scancode = 0x1015 toggle=1
800.183294: lirc protocol(rc5): scancode = 0x1015

    But that's no big deal, you can work around it with 2 scancodes for the same button in your keytable - like you already did.

    The more problematic thing is that the signals seem to arrive at about 250ms interval instead of 110ms which is the standard for the rc-5 protocol. Therefore the kernel will interpret the scancode as distinct button presses and the normal repeat handling won't work.

    You should be able to work around this by increasing the IR receive timeout with eg ir-ctl -t 200000 - you can play a bit with the value, 150000 should probably work as well and give a bit better response or you can go up a bit, eg to 250000. Just test what works best for you.

    so long,

    Hias

  • Remote control troubleshooting

    Thanks a lot for the info!

    This seems to be a race between kodi and eventlircd grabbing the input device and if you're unlucky (and kodi "wins the race") the OK button won't work. So far this hasn't shown up during testing.

    We'll have a look how we can best solve this issue and hope we have a fix soon.

    so long,

    Hias

  • No Video Output with Hdmi to Dvi Cable RPI 3 B+

    Add "ssh" to the end of /flash/cmdline.txt, after "quiet". Note that everything has to be in a single line and that there has to be a blank between "quiet" and "ssh".

    You can also edit this on your PC, cmdline.txt is in the first (FAT) partition of the SD card. If you do this make sure the file is saved with unix lineendings, so eg use Notepad++ on Windows.

    Or connect the RPi to some HDMI monitor and perform initial configuration there before switching to the problematic DVI cable setup.

    so long,

    Hias

  • No Video Output with Hdmi to Dvi Cable RPI 3 B+

    ssh into libreelec and then run tvservice -s and post the output.

    I'm using a HDMI-DVI cable on my test setup without issues and the tvservice output here looks like this:

    Code
    state 0x120006 [DVI DMT (36) RGB full 5:4], 1280x1024 @ 75.00Hz, progressive

    You should get a similar line, with "DVI" and "DMT" in there. If the HDMI cable is disconnected the RPi will switch to analog (CVBS) video output and you get a line like this:

    Code
    state 0x40001 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced

    Note the "NTSC" in there, this means analog output is used.

    If auto configuration via DDC/EDID doesn't work you might need to manually set the video mode, using hdmi_group and hdmi_mode parameters in config.txt - see the RPi config.txt docs for details: Video options in config.txt - Raspberry Pi Documentation

    so long,

    Hias

  • Remote does not work in 8.90.006

    Quote from wwessel

    15:35:13.799 T:140619617347328 DEBUG: LIRC: - NEW 16d 0 KEY_EPG devinput (KEY_EPG)

    15:35:13.805 T:140619625744512 DEBUG: HandleKey: two (0x32) pressed, action is ActivateWindow(TVGuide)

    Does it mean that the setting for key 16d has changed?

    Yes, this was a fix in kodi. KEY_EPG should bring up the EPG / TV guide, previously it was mapped to the "title" action KEY_EPG is wrongly mapped to title instead of guide · xbmc/xbmc@5e3e056 · GitHub

    You have to change your remote.xml if you want to map the EPG button to bring up the context menu.

    so long,

    Hias

  • MAME with Leia / LibreElec 8.9.x?

    Until Kodi gets a native frontend for selecting games the easiest way is to use the Internet Archive Game Launcher addon by zachmorris Internet Archive Game Launcher

    A lot of more info is available in the retroplayer section of the Kodi forum Kodi Community Forum - RetroPlayer

    Basically you just have to install a mame addon from the LibreELEC repo and setup your controller. Then use the game launcher or enter the konami code, setup advancedsettings so that zip etc files aren't associated with audio/video files and select ROMs via the file list in the Games section of kodi and open them via the context menu / play with...

    so long,

    Hias