Posts by HiassofT

ErikSwan the RPi4 HDMI driver exposes standard DRM connector properties to set HDR metadata and colorimetry (BT709/2020) info, like eg Intel and AMD drivers do it, too. This is included in current upstream kernels (since 5.14) and in the downstream 5.10 RPi kernel - I haven't checked with the upstream kernel though.

The driver also exposes a max_bpc connector property to switch from 8bit to 10 or 12bit output, but YCC output (4:4:4 or 4:2:2) selection isn't implemented yet - the driver always outputs in RGB 4:4:4 ATM.

There's a draft PR to allow RGB/YCC selection via another connector property https://github.com/raspberrypi/linux/pull/4201 but ATM it's a bit unclear if it will be implemented that way or if it should be handled internally in the video driver (eg 4kp60 can't output 12bit 4:4:4 due to bandwidth limitations, auto-switching to 4:2:2 may be desirable in that case).

so long,

Hias

Just copy the tar file to the Update SMB share (or to /storage/.update/ via ssh/scp) and reboot.

so long,

Hias

Are you using ASS subtitles? If yes, then look here: RE: LibreELEC RPi4 9.95.2 does not reproduce .ASS subtitles

so long,

Hias

kodi.bin consuming about 15-20% on idle is quite normal on a clean install. Keep in mind that this is the percentage of a single core, RPi4 has 4 cores so it can go up to 400%. If you look at the "%Cpu(s)" summary in top you'll see about 95% idle.

Also keep in mind that the CPU frequency will have scaled down to 700MHz (check with bcmstat.sh or "vcgencmd measure_clock arm") and the load values reported from top are relative to that. So in absolute terms (4 cores at 1.5GHz max) kodi comsumes about 2.5% of available CPU resources.

Of course addons etc running in the background will consume CPU resources, so 20-30% (of a single core, at 700MHz) still look rather plausible.

so long,

Hias

Ballistic did you actually reproduce the issue before creating the log? Log entries look like you grabbed the log immediately after startup.

Also the logs show you are connecting through a Denon AVR.

Does the issue also happen if you leave the AVR out of the chain and connect the TV directly to the RPi? If yes, please provide a debug pastekodi log where you reproduced the issue and state the exact model number of your TV.

so long,

Hias

please post a "pastekodi" log running this build.

so long,

Hias

If you have output configured to 2 channels / stereo (which is the default unless you changed it or enabled passthrough) and are playing a multi-channel file (eg AC3 or DTS audio) you can adjust the center downmix level (eg make center channel/voices louder) during playback:

push the OK button on the remote, then choose settings (gear icon)->Audio settings and adjust "Downmix: Center Mix Level" - +5dB usually is a good choice for action movies with too loud sound effects.

If the file has 2 channel audio then there's nothing you can do.

If the file is multi-channel and you output multi-channel or have passthrough activated then adjust the center level on your amp/AVR.

so long,

Hias

The fix is already in our development branches.

Here's a recent LE10 build https://www.horus.com/~hias/tmp/libr…210-ae16a10.tar - would be great if you could give it a try and report back.

so long,

Hias

Just noticed in the log that the video size is 2560x1920 - RPis only support up to HD (1920x1080) H264 decoding.

so long,

Hias

Please test with this build https://www.horus.com/~hias/tmp/libr…210-ae16a10.tar , it has the latest video decoder fixes that were added after LE 10.0.0

If it doesn't work please use "pastekodi" on the command line or the log upload function in LE settings to create logs and post the URL - we also need the other info like journal that's included in these logs.

so long,

Hias

dmesg shows tvheadend is using a large amount of RAM which probably is the cause for the OOM killer kicking in and killing it.

I'd suggest you look into that first, eg disable timeshift-to-RAM if you are using that.

so long,

Hias

Please test with this build and report back if it fixes the ASS subtitles not showing issue:

LibreELEC-RPi4.arm-10.0-devel-20211001104210-ae16a10.tar

I finally managed to find and fix the root cause, with this build ASS subs area also shown fine for 4k movies here.

so long,

Hias

All HDMI and HW decoder fixes we have so far are in nightly builds.

Note though that the nightlies are based on LE 11 and Kodi 20 - better use the LE10 test build I linked above unless you are in a highly experimental mood and run them from a separate SD card (going back to LE10 most likely won't work without major trouble).

so long,

Hias

Modetest shows the second HDMI is unconnected:

40  0   disconnected    HDMI-A-2        0x0     0   39

If your soundbar only has an HDMI-ARC port then most likely you must connect it to an ARC capable port on your TV, connecting it to an HDMI port of the RPi probably won't work - check the documentation of your soundbar.

so long,

Hias

GUI resolution limit is not relevant, you'll hit the bug if the display resolution is set to 3840x2160 (or larger) at 50Hz or more.

Please test with this build, this is current LE10 branch (what will become 10.0.1 in the future) plus additional H264 fixes:

LibreELEC-RPi4.arm-10.0-devel-20210927231029-e218de0.tar (just copy it to the update share and reboot)

so long,

Hias

Quote from sbstp

I have a brand new Raspberry pi 4 on which I installed LibreELEC 10.0.0. When I close my TV and re-open it, the TV says no input is detected. If I login via ssh to the pi and do systemctl restart kod, it fixes the issue.

This is a known issue if you run at 4kp50/60 and it's even mentioned in the release notes LibreELEC (Matrix) 10.0.0 - LibreELEC

Quote

4K50/60 output is supported by the driver, but has some known issues (eg “no signal” when TV is put into standby and back on)

This should be fixed in 10.0.1

so long,

Hias

This is working now in LE10.

so long,

Hias

Nothing has changed in that area during the nightly builds you mentioned.

Are you using (AC3/DTS/...) passthrough? Note that volume control won't work when passing through AC3/DTS/... - if you play a movie with eg 2ch PCM or an audio file it will work though.

so long,

Hias