Ilvy99 the HEVC codec is not very optimised at the current time. It might help to enable adjust-refresh and set the whitelist to use 1080p @ 24/50/60Hz with 'doubled' modes working. The TV doesn't appear to have 23.976 or fractional rates like 29.97 or 59.94 but that shouldn't be an issue with PAL media; 25Hz should use 50Hz is doubling is on.
Posts by chewitt
-
-
I have pasted my kodi and tvheadend log files to
It's not a Kodi debug log.
-
Is this a tvheadend client or an LE11 problem? How could I find out?
I consulted my magic 8-ball, and it said "could be" .. for a better answer you might need to share debug log files so we can see what media is being played; specifically what codec is being used and whether hardware decoding is active or not.
-
It's best to use an "era appropriate" version of Ubuntu to build images or the docker template we ship in distro sources else weird toolchain issues can cause issues. All official LE 9.2 images were built with Ubuntu 18.04 - so I'd use that.
-
I'm not able to test anything related to DVB cards/drivers, so no idea. I also disable the driver-addons (so we don't ship them) as I'm using a kernel that's always ahead of support for compiling them, so the only option in AMLGX is the in-kernel drivers. I generally suggest people run DVB cards on a separate device so you can use whatever kernel/driver combo works reliably on the headend and a latest version of LE on the client device.
-
Two options:
a) Fix the cert problem, see RE: Cannot Install/Update Addons
b) Grab a spare SD card and bump to an LE11 nightly https://test.libreelec.tv/ .. search on c2
-
mo123 the number of "developers" truly working on each SoC type is measured in fingers not hands. The support for upstream is probably there in u-boot now, or with only minor gaps, but it needs someone to go-through each of the major SoC generations and run proper tests or coordinate the testing with people who have the hardware. It's not an insurmountable task, but people have limited time. All volunteers and input on the topic would be welcome
-
Pi Zero2W hardware will boot LE11 nightlies but it is not supported by the project.
-
There is no Game 'Library' and database so it is not possible to change art like in the Movies/TV Library views.
-
We upgraded the releases server the other day and that broke some of the plumbing behind the scenes of the update system. It will get fixed but you can also do a manual update by SSH'ing into the box and downloading (wget) files directly to /storage/.update/ then rebooting.
-
I'm not sure about LE10 images but LE11 nightlies is 'Yes' assuming the hardware supports it.
-
You will probably want/need inputstream.adaptive installed.
-
dm140 is not in the upstream lcdproc code (it was refused due to licensing issues https://github.com/lcdproc/lcdproc/pull/47) so the easiest thing to do is probably to build the add-on yourself with edits made to the patch that we use to add support. If you are only modifying existing lines in the patch e.g. to use different USB IDs then the line-count of the patch will not change and it will still apply when LE buildsystem compiles the add-on. There is no need to change the module name to amc570.so. It's probably not too hard to do, but it's not necessary.
patch location packages/addons/service/lcdd/patches/lcdd-0.5.6-dm140_henlar_v0.2.patch
-
Remove the Pi board from the Argon case. If the problem still exists we're interested in diagnosing further. If it doesn't exist (and it probably won't) you can join the long queue of users and project staff that are getting a bit fed-up with the random problems those cases add.
-
Where do i get a 9.x LE image for berryboot ?
Get a spade from the garden shed and start digging downwards. When you reach the depths of Hell you will find an LE image for BB.
-
Use the AMLGX "box" image and set the dtb name to boot in uEnv.ini, then trigger recovery mode so it searches for the boot scripts included in that image (which are similar but slightly different to legacy ones). The "lepotato" image is designed for booting an actual LePotato board using mainline u-boot which uses a completely different extlinux.conf boot layout.
-
The short answer is 1) No, 2) No.
-
The Python 3.9 bump is causing issues in a few places - notably one of the caching add-ons that's consumed by some streaming and skin add-ons. It's not anything specific to my images (or LE) and will probably get resolved upstream soon enough.
