I'd be interested if CoreElec is good forever, or if the buttons will stop working after a while.
I can make my Panasonic work with the magic keys (*Power*-button, keep it pressed, and press *7* *3* *Stop* - which was actually documented in the user manual) but it always stops working after a while.
The problem is at the TV end, not the Pi end. If the TV doesn't send the button presses there's nothing that can be done.
See here for a possible fix - but I found that also tended to be temporary. I've ended up remapping unused buttons that are forwarded (e.g. the coloured ones) for functions I use.
I'm not aware of any regression.
If you could identify the exact nightly build where the performance regression started, then the changes there can be investigated.
Edit: We are suspecting https://github.com/LibreELEC/LibreELEC.tv/pull/10258
In my settings, I've switched Refresh to "Off" - keeping it on with my TV makes the movies look too smooth and unnatural, and not like "movies".
You want that setting on. If what you see is unnaturally smooth ("soap opera effect") then that is a setting on your TV.
See here.
To avoid ambiguity, are you saying a build you make from commit 4e4a6f9 is good and the very next commit (a794735ee) is bad?
Or are you testing official nightly builds (which may jump a few more commits).
Unfortunately, switching from 3D to 2D still doesn't work in LE13. In which file is this controlled? I'm not a programmer, but maybe there's a way to fix it.
StereoscopicsManager.cpp is the main control of what 3d mode is configured.
Some of the gui rendering code is in GraphicContext.cpp and some of the video playback rendering code is in VideoPlayerVideo.cpp
Have fun.
One other note, I've notice a message in the journalctl -a -b -0 section of the log when running pastekodi that had a warning about undervolting. I was originally using a 10W power supply, and I've changed that to a 20W power supply now. Wanted to mention that in case that solves the issue.
Running with an inadequate power supply (that the undervolting lines prove) can certainly cause random crashes.
Terrestrial (via aerial)? What country?
Just run "sudo apt install kodi21" on RPiOS Bookworm. (installing kodi will get the older kodi 20).
If you really need to build your own version, then see here.
Might be worth reading through https://github.com/xbmc/xbmc/pull/25813
It sounds like the default behaviour of some types of subtitle has changed.
It's not clear to me whether this is a regression, or a correction to behaviour.
Might be worth finding a nightly from just before and just after that PR went in, to confirm if that was the cause of the change you see.
I started 3 movies. The first 2 were mpeg-2 and h264 had no problems, the third was h265 and worked until the moment I opened the menu. The picture wasn't affected in any way but the sound suddenly stopped (the AVR's indicators for Dolby-HD/Dolby Atmos went out), that's when I ran "dmesg | pastebinit":
Nothing unusual in there.
No real ideas. After a failure run "dmesg | pastebinit" and post the url just to see if anything complained in the kernel.
If it were me, I might try adding "force_turbo=1" to /flash/config.txt.
If that didn't work, I might try a core_freq overclock (note: too high and this could crash - backup before experimenting).
Start with core_freq=600 (but you could try 700 or 800).
How come my battery powered 2018 Snapdragon sdm845 armv8 64-bit processor can handle fluid 1080p AV1 10-bit video and my latest nightly Libreelec 3A turbo=1 1800-Mhz powered RPI4 8Gb RAM can't?
Your phone is running at 2800MHz, has an extra 4 cores, and cost far more than the pi 4 is probably the reason.
In my testing with 1080p VC-1, pi5 can play pretty much anything.
Pi4 can play many titles, but it is close to the edge. High bitrate spikes, interlace and high frame rate (e.g 1080p60) will may cause issues.
You did it right. There is a chance that you have a hardware revision, which wasn't supported by LE 9.2.8 firmware (firmware is part of the LE image).
If it is this, you can install latest LE, copy firmware (bootcode.bin, start.elf, fixup.dat) somewhere safe.
Install LE 9.2.8, then copy the newer firmware back on.
popcornmix AFAIK it's hard-coded? .. or is there a way?
Yes, hardcoded in libcec.
Rebuilding with that line adjusted would probably work, but mglae's hack may work and be an easier fix.
It's not a LibreELEC issue because the bootloader diagnostic shows "EDID=none". That is a hardware issue.
It is either:
the hdmi display.
the hdmi cable (or adaptor if using one for full size to micro-hdmi)
the hdmi socket on pi
All tests should be done with no sdcard and using bootloader diagnostic display:
Try with other socket on pi. If hdmi1 also reports EDID=none then it's not the pi socket
Try connecting to another hdmi display. If you still get EDID=none then it's not the display but the cable.
If another display works then your display is not correctly reporting an edid.
If there's another hdmi socket, then try that. Otherwise report issue to you display manufacturer.
Not sure without digging but if so, the simple fix would be to copy bootcode.bin/start.elf/fixup.dat from a working new image to the 9.2.8 image and see if that helps.
Another possibility is general bug fixes and improvements have improved compatibility with that specific TV.
