Posts by HiassofT
-
-
See the RPi2/3 section of the release notes https://libreelec.tv/2022/03/09/libreelec-matrix-10-0-2/
QuoteNote that GPU accelerated H265 decoding is no longer available in LE 10 and future versions. If this is important to you stay at LE 9.2
H265 is software decoded and RPi2/3 simply don't have enough CPU power to do that.
so long,
Hias
-
-
JohnWayne111 this thread is about 4k HDR issues (see title). If you have issues with SDR files this is very likely a different issue which should be discussed in a separate thread - don't hijack this thread.
so long,
Hias
-
LE9 has no support for HDR. If you play a HDR video then the colours will be completely wrong (and typically brighter/more washed out) than they should be.
LE10 does support HDR.
And in addition to that TVs usually have separate picture settings/prrofiles for SDR and HDR (again per port, eg on my LG TV). So even if you had set up brightness etc before, in SDR mode, that very likely won't have any effect in HDR - you need to adjust that again, separately.
so long,
Hias
-
Check your TV settings, most likely you have different picture settings configured for the internal player than for the HDMI port with your RPi.
I'm not familiar with your Samsung TV but on my LG OLED the picture settings (Cinema/Game/Sports etc preset, brightness, picture "enhancements" etc) are separate per HDMI port and internal player / apps again have separate settings.
so long,
Hias
-
Thanks for testing! Yes, the fix will be in 10.0.3 - feel free to use the testbuild until then.
so long,
Hias
-
Yes, just copy it to the update SMB share (or /storage/.update/ folder via scp) and reboot.
so long,
Hias
-
Can you please test this build: https://www.horus.com/~hias/tmp/libr…759-4d9d4e2.tar
It contains a fix that might help with your seeking issue (it's the same fix that was included in nightlies a few days ago and seems to have helped ghtester).
so long,
Hias
-
Thanks a lot for testing!
so long,
Hias
-
Can you please test this LE10 build: https://www.horus.com/~hias/tmp/libr…759-4d9d4e2.tar
It contains an ffmpeg fix that should help with your files (I could verify that on LE master, but can't test on LE10 right now).
so long,
Hias
-
Here's a LE10 build with the RTC fix: https://www.horus.com/~hias/tmp/libr…759-4d9d4e2.tar
Could you please test that as well?
so long & thanks,
Hias
-
Thanks for testing and reporting back, good to hear it's working!
I've created a PR for LE master https://github.com/LibreELEC/LibreELEC.tv/pull/6334 and will create a PR for LE 10 too in the next days.
Pretoriano I've thought about the linux USB issue reports, too, but not 100% sure if they are really related. Could also be some of the other USB bugs (eg missing quirk or firmware issue of your USB device/adapter).
so long,
Hias
-
Easiest way to debug such things is with a serial console. Remove "quiet" from cmdline.txt and add "systemd.debug_shell ignore_loglevel" - for initramfs debugging adding "debugging" and "progress" may also help.
I'm not using a USB/SSD here and rarely do updates on SD card, most of the time I netboot my dev systems and update the boot partition with a simple script using the files in the tar
so long,
Hias
-
The last two lines are normal (and harmless) and you can safely ignore them, the first one (10min invalid argument) is odd though and should not be there.
Not sure where that should come from, 10 minutes sounds like a ridiculously long timeout. Did you add some systemd services and set it there?
so long,
Hias
-
Can you give this build a try?
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-11.0-devel-20220327210704-a78ef86.tar
I noticed RPi kernels didn't have CONFIG_RTC_HCTOSYS enabled, since kernel 5.10 that should also work with RTC drivers built as a module and thus system time should be automagically set after module load if it's not been set up yet - so the (broken) udev rule should no longer be needed.
Would be great if you could give that a try, I don't have any RTCs for RPi4 here.
BTW: source code is here: https://github.com/HiassofT/LibreELEC.tv/tree/le11-test
so long,
Hias
-
Thanks, ir-keytable -r output looks OK.
Please try running "ir-keytable -p all -t", push some buttons on the remote and post the output.
Also run "ir-ctl -r", push a single button for a very short time (quarter or max half a second) and post the full output you got - the ir-ctl output in your first post looks rather odd.
BTW: are you sure the batteries in the remote are OK?
so long,
Hias
-
did you stop kodi and eventlircd before? What's the output of ir-keytable -r?
so long,
Hias