Will it be possible to use the second HDMI to output the audio (with or without 1080P or lower video) while sending the full 4K video to the TV on the other HDMI?
I've read that it's possible to configure which HDMI output will get audio (and CEC), so I guess it could maybe work.
I have no idea though how Kodi will react to two active video outputs and unfortunately I have no easy way to test this. Maybe someone else could chime in and check if this works.
so long,
Hias
Do you feel there's any value in purchasing the 4GB at this point for just Kodi usage?
4GB is probably overkill just for kodi.
Unless you want to run a lot of background services or docker containers 2GB will be fine.
so long,
Hias
Does somebody know if the 4B has support for HDMI-CEC?
This would be a very important feature for me to use it as media server.
Yes, CEC works fine on RPi4 - used that mainly when testing on my TV the last couple of days.
so long,
Hias
Is 2GB really required? I've always thought that RAM didn't much matter to video playback if hardware decoding was supported.
My current usage is only 1080p and I won't be upgrading to 4k for many months. Will playback on 1GB be evened out by then?
My crystal ball is currently on repair so I can't tell what the future will bring us in a couple of months.
Current recommendation is: 1GB is fine for 1080p usage, for 4k spend the extra 10$ for the 2GB model. HW video decoding also needs RAM for buffers which need to be larger with 4k content than with 1080p.
so long,
Hias
I understand it has hardware decoding for HEVC content but what about 10 bit? Will it smoothly run 1080 and 4K x265 10 bit content?
both 8 and 10 bit HEVC HW decode is supported and testing with that was fine.
Video output is 8bit ATM, 10-bit / HDR will probably be added later.
so long,
Hias
I'd recommend getting the 2GB model for 4k, with 1GB memory is a bit tight ATM (this may change in the future with further improvements to the firmware and video driver).
so long,
Hias
Thanks a lot for testing and I'm glad it's working fine!
We'll add the changes to LE master, LE10 is still very far away but at least we know that we should be good for now 
so long,
Hias
Thank. How to switch from ir-keytable to lircd?
in LE9 lircd will be started automatically if you have a /storage/.config/lircd.conf file. If you use lircd you should also create an empty /storage/.config/rc_maps.cfg file so that in-kernel decoding doesn't interfere with lircd.
so long,
Hias
1) Can I teach ir_keytable raw commands (similar to LIRC)?
Not yet. Recent kernels added support for BPF decoders (allowing you to upload BPF programs into the kernel to decode almost any IR signal), but this isn't enabled in LibreELEC yet (one of the userspace helper programs, lircd2toml.py, also needs Python3 which we don't have yet - that will be added once Kodi switches from Pyton2 to Python3).
So for now it's easiest to stick to lircd if you want to use a remote with an unsupported protocol.
so long,
Hias
Yes, when you see the thermometer the RPi is throttling - read here for more details Raspberry Pi Documentation
so long,
Hias
From the IR scancodes it looks like you are using a Zotac remote.
In LE 9.0 we reduced the numbers of remotes supported out-of-the-box (to avoid conflicts), but you can easily enable support for the Zotac remote by creating a /storage/.config/rc_maps.cfg file with the following content
so long,
Hias
Thanks for reporting back, I'm glad it's working now and I'll add the fix (dropping the modprobe file) for the next release.
And I agree with you, the driver shouldn't crash if mouse functionality is disabled.
It'd be best if you sent a bug report by email to Mauro and Sean (the maintainers of the media and rc subsystems) and a CC to the linux-media list:
Mauro Carvalho Chehab <[email protected]>
Sean Young <[email protected]>
so long,
Hias
Make sure you haven't disabled eventlircd or have any other old configurations hanging around. If in doubt post the output of
Also check with irw, ir-keytable -t and ir-ctl -r as described in the wiki.
Edit: and please grab the latest log ZIP from the Logfiles samba share and attach it here.
so long,
Hias
Can you test with an empty ati_remote.conf modprobe file?
It looks like LE ships with a modprobe file to disable the mouse part and my guess is that this causes issue in the driver when mouse buttons are pressed on the remote.
LibreELEC.tv/ati_remote.conf at master · LibreELEC/LibreELEC.tv · GitHub
so long,
Hias
Can you test with the default LE DVB drivers? Wouldn't be the first time one of the media builds (DVD driver packages) causes issues with remotes.
so long,
Hias
Thanks for the logs, I could now reproduce the issue, pinged the RPi folks and they fixed it in the kernel (so the next LE release should be fine).
If I understood the code correctly the message is a rather harmless warning which you can just ignore for now.
so long,
Hias
I'm unable to reproduce the issue here. Tried with a fresh 9.0.2 install on a RPi3B+ and checked both with disable_overscan enabled and commented out.
Did you make any other changes to config.txt? If yes, please post your config.txt.
Also please grab the latest log ZIP file from the Logfiles samba share and upload it here.
so long,
Hias
