I've not seen issues with stuttering and jumping in HEVC videos but the HEVC codec is unfinished so it's not impossible. I'd normally associate that kind of description with bad encodings or TV's without correct modelines (e.g. 24Hz not 23.976Hz, or perhaps 3:2 pulldown; 23.976Hz at 60Hz) where occasional corrections are required.
Posts by chewitt
-
-
I have a VIM4 and currently see no sensible route to an LE image that runs on it due to zero upstream kernel support and a long (and not guaranteed to ever happen) time-gap until that happens. It's not simply a new iteration of the A311D (VIM3) chip, it's an all new SoC with some non-trivial IP changes (new USB, new HDMI driver, etc.) that need all-new drivers. CE can probably handle this device better since they work with vendor kernels that bundle those drivers, but even for them it's not so straightforward as Amlogic has dropped amcodec and most traces of older hardware from their latest iteration of codebase.
-
deffffz If you update using the .tar file from my share I've bumped the broadcom firmware package and it should be in the image now.
-
cant run LE off USB on Pi I dont think
only works on SD sadly
RPi3B onwards (with firmware update) and RPi4 have supported USB boot for some years now.
-
Install the current nighly test image (so latest code). Then run the SSH command and share the URL so we can see the boot log and what issues or errors might be there.
-
I'm not aware of any major issues with newer boxes, but you'd probably need to use a nightly to get newer kernel with drivers that support the latest Intel hardware. Current 'release' LE versions are probably too old.
-
There are more NUC variants than anyone cares to keep tabs upon these days so rather than ask if there are any known issues with a specific model, it's much easier to just stick the latest nightly LE image on a USB stick and try it - then come back if there are problems.
-
Safe mode only applies when the OS is fine but something got messed up with Kodi (normally a bad add-on causing repeated crashing). In your case something more fundamental is messed up and you're not getting that far in the boot process. The OS does (or should) attempt to fix basic filesystem issues automagically but there are limits to that. NB: If you aren't familiar with Linux and only used the USB a few times it'll be easier abd considerably quicker to start over with a clean install.
-
We do automated build runs of all the add-ons at least weekly so if it's not in the repo there's some kind of build issue.
heitbaum are we aware of any issues with libretro?
-
It's just installed to /storage/.config/samba.conf (rename the .sample file). It's the same process as any other OS but ISTR we are missing the tools needed to create the password database, so you'll have to do that somewhere else then move the file to LE and reference where it resides in the conf.
No idea on the performance drop/difference with containers as it's not the kind of thing we ever have time for - but it's $free to experiment.
-
IR remotes. BT remotes are "keyboard" HID devices.
-
LE has a samba server embedded but it assumes a single user so you will need to deploy a customised .conf to support different configs with multiple users and any extra configuration required. LE has no package manager but you can install the Docker add-on to add containers to extend other capabilities and functions. There are deliberately no torrent add-ons in our repo.
-
The add-ons in that share are just test builds for specific build/compile issues. The full list of supported add-ons for nightlies are (or should be) in our main repo; both ARMv8 and ARMv7.
-
Run "dmesg | paste" from a current nightly and share the URL please.
-
just did a check and I think its actually a BCM4334
The q200 dtb should has the bits needed for WiFi support and firmware should be present in the image (https://github.com/LibreELEC/brcm…7bba7f0c7ee36c2). Run "dmesg | paste" using the current "box" image from https://chewitt.libreelec.tv/testing/ and share the URL please.
-
-
deffffz AP6335 should just work (as with most Broadcom SDIO chips): https://github.com/LibreELEC/brcm…9d802a2d7355e90 .. what dtb did you use?
-
LE uses upstream kernels, so if the original change was backported the fix would also be backported and eventually end up in the Linux 5.10 stable branch that we occasionally bundle/package into an LE update.
