Yes, exactly - Dolby Vision isn't supported. HDR10 and HLG work fine.
so long,
Hias
Yes, exactly - Dolby Vision isn't supported. HDR10 and HLG work fine.
so long,
Hias
Try adding video=HDMI-A-1:1280x720M@60D to the end of cmdline.txt (after "quiet", separated by a space).
so long,
Hias
The boot partition is mounted at /flash, not /boot. See also https://wiki.libreelec.tv/configuration/config_txt
so long,
Hias
Are you by chance using an RPi4? If yes, we are waiting for this issue to be resolved KMS: blank screen after TV is brought out of standby on modes that need scrambling · Issue #4486 · raspberrypi/linux · GitHub
Just configure kodi display settings to 1920x1080 and whitelist the 3840x2160 modes, then you won't hit the issue when in kodi GUI.
so long,
Hias
Try adding video=HDMI-A-1:1280x720M@60D to the end of cmdline.txt (separated by a space from "quiet", everything has to be on a single line).
If it's a HD-ready TV then probably the RPi4 doesn't like it's native/preferred resolution (well known issue).
so long,
Hias
Please use the latest nightly build, this is a known issue and already fixed No USB on RPI 4 after upgrading to LE10 RC1
so long,
Hias
BTW: no need for a fresh install, you can just update your current installation (copy the tar or img.gz file to the Update share or /storage/.update/ folder and reboot).
so long,
Hias
We use the more modern in-kernel IR decoding, see our wiki for more info: https://wiki.libreelec.tv/configuration/ir-remotes
As you seem to be using an older IR receiver on the PC's serial port you have to manually disable the UART and load the serial_ir module as described eg here: Problems with lirc serial and autostart.sh
so long,
Hias
Thanks a lot for testing and reporting back, good to hear it's working fine now!
If you like you can update to later nightlies, we fixed a couple more bugs (and stopped enabling 4kp60 by default as that there's an unresolved issue). See the github commit log for details Commits · LibreELEC/LibreELEC.tv · GitHub - clicking on the linked pull requests in the "merge pull request ..." commits usually contains some more info about the changes.
It's always helpful for us if people test the latest nightly so we get feedback if we accidentally broke something.
But of course it's also OK if you just stay on the build that works for you and wait for the final release.
so long,
Hias
Please provide a debug log where you reproduced the issue with H264 files - the log you posted shows only a HEVC file being played and looks fine.
so long,
Hias
Ah, your cmdline.txt is wrong, you seem to have put "
drm.edid_firmware=HDMI-A-1:edid/1920x1080.bin" on a new line - everything needs to be in a single line in that file. You can drop that and make sure that
"drm.edid_firmware=HDMI-A-1:edid/edid-HDMI-A-1.bin video=HDMI-A-1:D" immediately follows after "quiet" (separated just by a blank).
so long,
Hias
Thanks for the logs, it's good to know that it works fine with the projector connected directly to the RPi.
Please do the following:
Connect RPi directly to connector and boot up LE. Then ssh in and run "getedid create". Now shut down LE and add the HDMI converter / audio extractor back into the chain and boot up again.
LE will now permanently use the (working) edid from your projector and everything should work fine.
so long,
Hias
This issue has now been fixed, can you please give the latest nightly (currently 20210730) from here Index of / a try and report back if it works`?
so long,
Hias
I would like too but am using both HDMI Ports, so until that is fixed in the nightlies it‘s a no-no for me
FYI: This issue has now been fixed, please give the latest nightly (20210730 ATM) a try.
so long,
Hias
I've opened a github issue, the same happens in RPiOS KMS: blank screen after TV is brought out of standby on modes that need scrambling · Issue #4486 · raspberrypi/linux · GitHub
The strange thing is I already ran into that issue some time ago, reported it, then it was fixed (and working here with my LG C8) but now it no longer works here either...
so long,
Hias
Makes sense, however, how come I don't experience these issues on your build posted in this thread?
We recently enabled 4kp60 by default in nightlies, which needs higher clocks and is probably more sensitive to thermal throttling and FW reducing clock speed to prevent overheating.
You could try changing the display resolution to 1920x1080p60 in settings (in general that's the recommended setting as kodi GUI is 1080 anyways), that uses lower clock speeds and should be affected less.
so long,
Hias