Posts by HiassofT

RPi4/400 video driver currently supports 1920x1080 max, support for higher resolutions isn't fully implemented yet.

The pixel-wrap is a known issue in the video driver, see here vc4-kms-v3d-pi4 offscreen quad leaks to the left side of the screen buffer · Issue #3667 · raspberrypi/linux · GitHub and here [BUG] Final output image overflows by 1 pixel to the right, pixels wrap around to the left of the screen · Issue #4779 · LibreELEC/LibreELEC.tv · GitHub

ATM we're waiting for fixes for these issues, when they are included in the RPi kernel/video driver we'll add them to LE as well.

so long,

Hias

Please try the latest nighly image and add otg_mode=1 to config.txt instead of the dwc2 dtoverlay. This will give you an XHCI controller instead of the limited dwc2 controller and it's also what recent USB boot is using for the OTG port.

See also [BUG] Missing configuration parameter for DWC2 at RPI4 · Issue #4722 · LibreELEC/LibreELEC.tv · GitHub

so long,

Hias

RPi 400 uses a different wifi/bt chip which isn't supported in LE 9.2.6. It will be supported in LE 10 (current nightly builds already work).

See also here RE: LibreELEC (Leia) 9.2.5

so long,

Hias

Live TV and especially tvheadend is a different can of worms, better keep discussion about that confined to separate threads, otherwise the worms will creep everywhere

I can't really comment on Live TV issues as I'm very rarely using it.

The seeking issues I mentioned only affect H264 decoding with HW acceleration (which was previously disabled on RPi4). I didn't have any issues with H265 HW decoding and also am not aware of any issues in that area.

so long,

Hias

Yes, master is still limited to HD. 4k will come later, it's currently not supported in the RPi video driver.

so long,

Hias

Short update:

Kernel 5.10.1 update and a first version to fix seeking with H264 (and MPEG2/4 on RPi2/3) hardware decoding were merged into master yesterday and are now in nightly builds.

CEC on RPi2/3 should work again and H264 hardware decoding is now enabled by default on RPi4.

H264 seeking isn't perfect yet, sometimes it jumps to the beginning of the file (this is being investigated). You may also notice a bunch of ERROR lines in kodi log when seeking, these were (temporarily) added to make debugging seek issues easier - just ignore these if seeking works fine for you.

Video occasionally cutting out on RPi2/3 is still an issue, this is also being looked into.

so long,

Hias

The easiest thing would be to connect the tuner via an externally powered USB hub.

I can't comment on your specific tuner, would guess though that when using the official power supply it should work fine, if it's the only thing you connected to the USB ports (RPis have limit on overall power draw on USB ports).

From my personal experience with a Xbox USB tuner I can say it works fine, but if I also connect a bus-powered HDD it fails miserably - total USB power consumption is too large and that makes the tuner completely drop off the USB bus (USB disconnect messages in dmesg).

so long,

Hias

Quote from harry_fine

At this point I'm ready to buy another tuner that's known to work on the PI4 with Libreelec. Are there any tuners out there, single is fine if need be, that absolutely work out of the box with the current version on the Pi4?

If single tuner DVB-T/T2 is fine then have a look at the RPi TV Hat Buy a Raspberry Pi TV HAT – Raspberry Pi

so long,

Hias

See Post #3 in this thread. This feature is included in our latest nightly builds here Index of /, , please use these instead.

so long,

Hias

The changes will be added to master branch (and in nightly builds) when they are ready.

so long,

Hias

On LG TVs the setting to disable overscan is called "Just Scan", it has to be set to "on". On my 55C8 it's in Settings->Picture->Aspect Ratio Settings.

so long,

Hias

I had described the IR and kodi remote processing in the wiki, but it seems this has now been removed with the switch to the new wiki...

Here's the archive of the old wiki page Infrared Remotes [LibreELEC.wiki] , the introduction should contain the info you need - also read through the linked kodi wiki pages for more detais.

so long,

Hias

No, although the device has "LIRC" in it's name it has nothing to do with lirc or the other infrared remotes - it presents itself to the system as a keyboard.

Enable debug logging in kodi, push the button and then post the kodi debug log - this will show which key kodi received and give more hints.

so long,

Hias

I don't have a Harmony remote but AFAIK the selected remote profile is what defines the scancodes to be sent - so dig into that.

My guess is the remote profile sends two different scancodes on left/right to support two (slightly) different DVD players - which might work with the original players but is highly non-standard with anything else.

Check if there are other similar remote profiles if you want to stick to the Pioneer DVD profile or just configure the Harmony to use the Microsoft Media Center remote (not the MCE keyboard!), this will work out-of-the box in LE.

If you plan to use both your original pioneer remote and the Harmony to control LibreELEC you can still do this when the Harmony is configured as MCE: Enable both nec and rc-6 protocols in the keymap and add the key/scancode definitions from rc6_mce to your keymap (we do a similar thing in the default libreelec_multi keymap to support Xbox remotes in addition to MCE).

so long,

Hias

The output of "play" looks fine (as expected when the Harmony repeats the command 3 times): It sends the scancode 0xab22 three times, which then results in a single key_down event.

The "left" test is odd though, the Harmony transmits two different scancodes, first 0xab2c and then 0xaf63, and repeats that three times. This doesn't end well, when a different scancode is received it's interpreted as a release ("up") of the previous scancode.

That's something you need to fix in the Harmony configuration - make sure a button sends a single scancode.

so long,

Hias

Copying dt-blob.bin from LE9.2 to the FAT partition might be enough to get an RPi2 image booting. Recently a user used that to successfully boot RpiOS (ex Raspbian) on a Slice with CM3

Trying (and failing) to resurrect my Five Ninjas Slice with CM3 - Kernel Panic - Raspberry Pi Forums

As I don't have a Slice I haven't tested that myself so can't be 100% sure if that'll also work with current or future LE 10 images, but I'm quite confident and you should have a starting point.

so long,

Hias

Can you post the output of "ir-keytable -t" when you do a short button press on the remote?

Usually remotes send the scancodes every (approx) 100ms while the button is pressed, this is interpreted as a "held down" button by the input subsystem - you'll see an initial "key down" event and then get further key down events after the specified repeat delay.

If the scancodes are too far apart linux will detect them as separate button presses (i.e. key down followed by key up some 150ms afterwards).

If the scancodes are only a bit too far apart then tweaking the receive timeout (ir-ctl -t VALUE_IN_MICROSECONDS, eg ir-ctl -t 125000) can help to detect these as a held down button - ideally the Harmony remote should behave like standard remotes though and follow the protocol specs though.

so long,

Hias

You could try increasing the delay before repeat kicks in - use eg ir-keytable -D 750 to increase it from 500 to 750ms.

This will work while kodi/eventlircd are running so you can experiment with the values.

so long,

Hias