Since a week LE 11.0.0 milestone was closed. Is this version being be skipped for the official release and being replaced with 11.0.1?
Not trying to stress here, just curious what the current plans are
I never had any glitches but there have been indeed a few of unexpected reboots in the last days.
Well, not exactly complete reboots, more a restart of some services I guess:
From watching TV, out of nowhere, a black screen appears and after a few seconds I'm on the LE main screen.
Plus I had a couple of picture blackouts the last days. From watching TV, a black screen for a second or two and then back to the TV program as if there was nothing.
Not sure if this fits your issue titoasi but I'll try do dig deeper into it as soon as I find time and post the logs link here.
Add-ons > My Add-ons > (navigate to the add-on) > Information > Disable "auto-update"
This only works if auto-update is enabled globally, which I would like to prevent, and even then, the add-on still shows up as updateable. What I really wanted is that it won't appear in any way in the update list, so that there is zero chance it will being updated accidentally.
I found the workaround here:
Solved and thanks!
Is it possible somehow to exclude a specific add-on permanently from showing up in the add-on update notification list?
I have an add-on that I never want being updated by the official Kodi/LE repository but instead I want to use a self compiled version.
It's just this specific add-on, all other add-ons should update the classic way as intended.
Very excited! Final version coming soon?
RPi4 will be 'faster' with overclocking but it's 'fast enough' in stock configuration.
Definitely not true for VC-1@1080p content, see my post here I made currently:ThreadI noticed that playing VC-1 endoced files leads to alot of dropped frames. In the first two minutes of the Blu Ray rip of The Boure Identity it says 86 dropped frames in the ctrl+shift+o overlay.
The problem seems to be that the PI 4 does not have hardware acceleration for VC-1, unlike the Pi 3, and that the CPU is not quite powerfull enough to decode it via software. What make me belive that is
- There are alot of dropped frames when playing h.264 when hw-decoding is deactivated, but no dropped
February 4, 2021 at 8:13 PM
Overclocking the Pi 4 solved all stuttering issues in my case.
Just wanted to mention here additionally, it may help others.
What's the current state on this?
I have a Raspberry Pi 4 with LE11 beta 2 installed and VC-1 content still gives me a lot of troubles, playing those video files smoothly is just impossible right now.
Ok, overclocking as described on the following link solved my issues with VC-1 @1080p so far. Nevermind.ThreadHow does one go about overclocking an RPI4 when using Libreelec?
Is it the case that one applies the changes to /flash/config.txt that are provided here?
January 9, 2020 at 6:24 PM
Just for completion, I just added the following content to /flash/config.txt file:
I made some CPU temperaure tests additionally which I wanted to share here.
With the overclocking setup mentioned above, when playing VC-1@1080p content, the Raspberry Pi 4 its CPU temperature does never rise above 50°C with a FLIRC Aluminium case.
Long time since I last posted something, but I'm not dead yet
Add GPG (GnuPG) into LE so that it will be possible to create encrypted TAR files, for example for encrypted backups.
Currently it is only possible to do this via creating a .TAR file first and then put the .TARf file into an encrypted .ZIP file.
Thank you in advance for considering!
I just found this Wiki entry which explains a lot of 4K related stuff in Kodi. Very nice!
But what I'm curious about is what is mentioned here:
Why is it recommended to let Kodi do the upscaling to 1080p when the TV can do it too?
I mean, I see the point of setting the desktop to 1080p, but for movie/TV stuff, as also mentioned in the Wiki, most 4K capable TVs should do the upscaling much better than Kodi.
So why even let Kodi do the upscale to 1080p and not passing through everything to the TV, including SD sources?
Can someone please explain a little deeper?
I think that helps, thank you very much mate!
And that's it? Really not more to implement?
I know I'm far away from being able to expect help with my problem within this forum but I'll try anyway as this place is my last hope. So here's my problem:
Beside LibreELEC, for Retro gaming reasons, I have set up "Batocera.linux" on another Linux based HTPC system, with exactly the same hardware, for which I'm having a hard time trying to make WOL work, while on the LibreELEC system WOL is indeed working without problems.
I asked Batocera support for help and there was one guy telling me that there is no solution as Realtek NICs do disable WOL by default when there is a non-Windows OS running on top of the hardware. Beside the news that WOL is not only BIOS setting dependent but also OS dependent, I thought "this can't be true" and for testing I tried to install a generic x86_64 Ubuntu Server system onto the HTPC. And really, WOL is not working with this setup too.
Now my question is: What kind of magic have LibreELEC developers implemented to make WOL work on Realtek drivers on a non-Windows system?
Again: I know, here in this forum I cannot expect anything for other systems than LibreELEC but I am very thankful for any hint as I don't know where else it would make sense to ask. You LE devs somehow have done the trick and I really want to learn how to make WOL work on Linux systems on those Realtek NICs.
Did you also mention there are several emulators not installing correcty while installing them via the wizard?
I have experienced this with LibreELEC and also on Windows/Kodi.
This causes the wizard to bring up the following message at the end:
I would be happy if I would overthinking the problem, already described here btw.
LE just loses the default screen setting sometimes. Unfortunately I was not able to reproduce the issue (yet), it comes and it goes unexpectedly.
Those entries within advancedsettings.xml, in my experience, are the most reliable way to load those settings before kodi starts, when settings within guisettings.xml on the other hand are just saved on poweroff/reboot as you've already mentioned within the other topic. They obviously can be lost/overwritten in some cases, at least on my system.
New website is the bomb, I really like the new style!