I have CEC disabled in my AVR so it's something that I never test, so no clues, but I'd ask that you update to an LE13 nightly first as the LE12.2 codebase isn't going to receive any further development. Functionally LE13 is light-years ahead of LE12.2 as well (all the hardware decoders work).
Posts by chewitt
-
-
Pull requests · LibreELEC/service.libreelec.settingsthe LibreELEC settings addon for KODI. Contribute to LibreELEC/service.libreelec.settings development by creating an account on GitHub.github.com
-
Pull requests · LibreELEC/service.libreelec.settingsthe LibreELEC settings addon for KODI. Contribute to LibreELEC/service.libreelec.settings development by creating an account on GitHub.github.com
-
To me it looks like something something goes wrong in the DB schema update. I'd post an issue on the Kodi GitHub repo (mind that you follow the template or it will be ignored) or open a thread in the Kodi forum so one of their devs sees it.
-
-
I would go further and assume that x86_64 hardware has NO support for HDMI-CEC unless the device/board is explicitly advertised as supporting it, because most hardware is designed for "Desktop" use where CEC control is not required. There are increasing reports of small form-factor boxes with support, but it's a long way from being guaranteed.
-
Kodi is on RC2 (but still backporting things that kind of violate the idea of RC) while LE is working to push out a beta. There's no big rush on our side and if you have update OCD there are nightlies.
-
In the absence of any logs from either the LE devices (which likely don't exist after a few reboots) or the transaction log from the MariaDB server it's rather hard to comment on what might have happened. I constantly swap between different test devices and that regularly involves clean installs and reapplying an initial working-state config that involves connecting to a common MariaDB server. I do see issues from time to time, but these are easily attributed to DB version bumps (migrations) and scraper changes that are seen earlier in the release development cycle. Late in the cycle and release images are generally stable.
-
Nightlies are disabled while release images for 12.95.1 and the accompanying add-on repo(s) and other bits necessary for a beta release are generated.
-
S905Y2 uses the meson-di driver that I (claudius) wrote recently. This only works on G12A and up. There are hints for mem2mem operations in older SoC databooks, but as Amlogic never used/implented it that way there's no prior art in vendor kernels and the institutional knowledge of how to drive it that way isn't documented and now so long ago that the staff who did it (all in senior positions now) can't remember either. I might see what Fable can achieve by fuzzing the SoC directly, but that's going to burn a ton of tokens when I have other tasks that need them.
I'll have a look at the ffmpeg patch, thanks.
-
RPi4/5 are designed to run far hotter than people are used to, or comfortable with. As long as you are using 'some' kind of cooling solution it will be fine. If you like fan noise, go nuts. If you prefer a passive solution that will be fine too.
-
CMA at 384MB hasn't been an issue for me in testing on a native 4K screen downscaling might require more. I'll make a note to have a look into that. MPEG1/MPEG4 is something that will be added once we've finished considering the UAPI required.
I'd like to improve deinterlacing on older GX boards but the vendor kernel handles the conversion to progressive post-decode in the DRM layer rather than pre-decode as we do with the ffmpeg filter approach used in newer boards (and Allwinner/Rockchip). The GX era IP looks tied to this mode of operation and Amlogic engineer for deinterlace things isn't forthcoming with answers to questions.
-
PR is merged, thanks for testing and submitting

-
I'm hungry for an RK3588 port ala Rock 5B
It works quite nicely. I believe I've overwritten the test image that I made though, so that will need to wait a bit.
-
So slyguy is pirate. CBC, because it’s not an official app, is pirate. Both are legally available in Canada, SlyGuy’s PlutoTV etc etc, I mean, he just makes it more accessible/easier to integrate…but yaaar, I get it.
Nope, you don't get it. The Slyguy repo and those streaming services add-ons are not pirate. You need to have normal (legal) access to those services to use the add-ons with Kodi. If you're in the wrong region and/or don't have the the required accounts, they don't work. Random user showing up here with IPTV-simple and 4,500+ channels is the pirate.
-
-
What are “pirate” IPTV sources?
Any IPTV subscription service offering a global assortment and thousands of channels. Legitimate sources generally have low 10's of channels limited to a single country or small region. If we see obvious pirate feeds in use, support is refused.
-
Perhaps the switch case should be extended to 2|3|4 instead of 2|3?
That sounds plausible. Keep us posted
