Posts by HiassofT

This is to be expected, H264 hardware decoding is only supported up to HD resolution. 4k videos should be in HEVC/H265 format, like it's the standard for UHD BluRay.

so long,

Hias

/lib/firmware is a volatile directory in a ramdisk and re-created on every boot.

If you want to permanently add firmware files create a /storage/.config/firmware/ directory and put the files there, then reboot.

so long,

Hias

Quote from wymand

It is a pity that so many out dated and totally wrong instructions exist.

This is true, but a general problem of stuff you find on the internet - the majority is either outdated or completely wrong. Better don't google for third-party info on the net but always refer to the official documentation.

Therefore we have a wiki page with the current info - and it was linked in the first post of this thread:

Infrared Remotes [LibreELEC.wiki]

so long,

Hias

If you plan to only use it on the RPi I'd recommend the RPi TV Hat Buy a Raspberry Pi TV HAT – Raspberry Pi - it works out of the box.

so long,

Hias

The addon update PR [le92] kodi-binary-addons: update to latest Leia versions by HiassofT · Pull Request #4069 · LibreELEC/LibreELEC.tv · GitHub has just been merged, updates should be available in the repo soon.

so long,

Hias

Check the scancodes with ir-keytable -p all -t - on LE 9.2 this'll also print the protocol.

There's no real standard how the scancodes are formatted (eg lirc uses a completely different scheme than ir-keytable) and it could well be that AnalysIR uses a different one.

Also see the wiki for details Infrared Remotes [LibreELEC.wiki]

so long,

Hias

Yes.

so long,

Hias

Thanks for the hint!

I've opened a PR with a bunch of addon updates (including pvr.teleboy 18.1.8), if testing goes fine the updates should be in the LibreELEC addon repo within about a week or so.

[le92] kodi-binary-addons: update to latest Leia versions by HiassofT · Pull Request #4069 · LibreELEC/LibreELEC.tv · GitHub

so long,

Hias

Could you try to install Raspbian Desktop on a separate SD card and check if switching resolution / refresh rate with the display configuration utility causes the same issue?

This would help us to narrow down if it's an issue with LibreELEC/Kodi or the RPi firmware.

If the issue also occurs with Raspbian it's best to open a bug report here Issues · raspberrypi/firmware · GitHub

so long,

Hias

Pulling the plug while the RPi4 was running may have resulted in the settings not being saved.

Better connect the RPi4 to the TV, change the resolution to 1080p60 and then shut it down cleanly. Then pull the plugs and connect RPi4 to the AVR.

so long,

Hias

Thanks for reporting back!

Updating the AVR firmware would be worth a try, often the release note / changes are incomplete.

Can yoiu also try configuring the RPi to 1080p60 and then powering off both RPi and the AVR?

It's interesting that the initial 1080p60 mode from RPi seems to work and most issue reports I've seen so far involved resolution and/or refresh rate changes, so there's some change that using the same mode as on powerup could result in a working display.

so long,

Hias

Can you check if 1080p works if you connect the RPi4 directly to the TV (bypassing the amp)?

It would also be good to know which amp you are using.

We've got a few similar reports of display problems when an amp is in the chain, though it's not quite clear what exactly is causing the issues.

Edit: checking if there's a firmware update available for the amp would be also worth a try.

so long,

Hias

The crash seems to be caused by the HDHomeRun PVR addon.

When kodi safe mode appears ssh in, delete the addon

rm -rf /storage/.kodi.FAILED/addons/pvr.hdhomerundvr/

and then reboot. Kodi should then start up normally. When kodi is up, try installing the addon again.

Edit: this seems to be an unofficial third-party addon, if kodi crashes again it probably needs to be fixed to be compatible with LE 9.2.

so long,

Hias

Youtube uses the VP9 video codec for 4k videos which the RPi4 can't decode in hardware - and software decode is way too slow. So 4k youtube won't work on RPi4 (unless you are satisfied with seeing a slideshow).

so long,

Hias

You have to enable MPEG-DASH support in Youtube addon settings and set Video quality to 1080p (also in the MPEG-DASH tab). With these settings 1080p is working fine here on my RPi4.

so long,

Hias

Enabling "HDMI ULTRA HD Deep Color" is recommended as that'll make it possible to drive the display with 4kp60 (without it it'll be limited to 4kp30 on the RPi4). Other than that it doesn't make a difference for now.

I meant checking the picture settings (i.e. where you can select picture mode, brightness, contrast etc).

If the difference for non-4k videos is minor these settings are probably fine.

I still suspect you are playing HDR 4k videos (eg HDR10, HLG or DolbyVision). In that case the difference will be indeed huge as RPi/Kodi can't currently output HDR. This means the maximum brightness, contrast etc will be far lower than if you play these natively on your TV.

BTW: if you play HDR videos on your TV you may also notice a "DolbyVision" or similar popup and a change of available picture modes in the TV's settings.

Basic support for HDR output has just landed in the Linux kernel and there are still quite some bits missing (in RPi video driver and Kodi) until HDR will be supported.

so long,

Hias

Sep 10 is still the latest official firmware. If you want to use / test the beta firmware you have to download it manually from here rpi-eeprom/firmware/beta at master · raspberrypi/rpi-eeprom · GitHub

You can use rpi-eeprom-config / rpi-eeprom update as outlined above - at your own risk, as usual for beta stuff.

I've been using the beta firmwares for a while now (mainly to test network booting) and in general they worked quite well.

so long,

Hias

Actually it's not the OS crashing and rebooting, it's kodi crashing and the OS (LibreELEC) automatically restarting it.

And while I agree that an application crash isn't the nicest way to handle a corrupted file there's not much we can do about it ATM. So far we only know that it's crashing with some (probably not quite legal) file and maybe with some unknown kodi samples.

So, to be able to move forward with this we need a sample file so we can reproduce and analyze the issue.

so long,

Hias