Posts by chewitt

  • write protection libreelec

    a) Your website has screenshots that include Kodi logo's. Under the Kodi trademark rules if you are modifying Kodi in any way (one byte of code changes) you MUST either seek formal permission from the Kodi board for your changes (which will be refused automatically for anything related to piracy or pre-installing add-ons) or you MUST fully rebrand to remove all references to Kodi. As LibreELEC ships Kodi branded as Kodi, you should assume and apply the same rules to the entire LibreELEC distro (rebrand and remove all references to LibreELEC).

    b) Your website appears to be offering managed bundles of links to "movies, tvshows" etc. "for the community" which is wording that we normally see on IPTV streaming and Kodi addon sites associated with content piracy. LibreELEC has zero desire to be associated with piracy in any way, so if you cannot figure out how to embed your addons in our distro image (or even how to use GitHub, as per your PM) we are delighted and we offer no assistance.

    If we are wrong (because the website I have seen is light on information) please feel free to provide more information on your player/service. It's not what is written on the website that is suspicious. It is what is not written, i.e. If you were providing a legitimate streaming service you would want to positively attract attention and openly promote things in a very different way.

  • Playback issues

    No idea. I regularly discover my kids left tvshows or movies playing in sequence for hours; also using WP2 with the stock 8.2.5 image (not on the internal RAM, but that's irrelevant).

  • Audio only works sometimes and I can't figure out why.

    It's a startup timing/sequencing issue. The USB device hasn't initialised and loaded drivers before Kodi starts. Kodi evaluates the available audio devices once at startup and nothing is present; hence the device "disappears" and reverts to some other default. If the device has loaded drivers before Kodi is started the device is visible and can be selected.

    You can solve the problem by setting the badly named "wait for network" startup delay in LE settings. A small delay should give the drivers time to load before Kodi starts. Something like 5 seconds should do the trick if it's borderline.

  • Kaby Lake-R Intel NUC7i7DNHE

    2GB RAM is more than enough for any LE install. 16GB of SSD is more than enough for a huge library; assuming media is on a NAS somewhere else. These days it's hard to find anything smaller than 64GB though. LE 8.2.5 should be fine on Kabylake. It's only the very latest generations that need newer kernels.

  • S802/S812-Libreelec images for 7/8/9

    We currently expect to retire the WC image after LE 9.0 due to upstream changes in Kodi related to the next-generation rendering and decoding pipeline and subsequent cleanup (removal) of proprietary interfaces including amcodec that the 3.10/3.14 kernels depend on. The new pipeline will require a mainline kernel, and while meson8* hardware support in mainline continues to improve positively there is still no visible work being done on a DRM (direct rendering manager) video driver, which is fundamental for LE/Kodi support. It's something we continue to track; if things change our plans can change.

  • Long boot time on new install

    I've got no idea what the issue is or how to debug SATA initialisation problems, but I'll pass the observation that you're running tests on the drive *after* it is has completed initialisation, and it looks like the initialisation process is where the delay is incurred.

    Can you connect the drive to an alternative SATA port? .. any firmware/BIOS updates available for the HTPC?

  • feedback for test build LibreELEC-RK3328

    kostaman Rockchip: use default kernel name by lrusak · Pull Request #2690 · LibreELEC/LibreELEC.tv · GitHub will be the reason. Run the following to tweak boot config:

    Code
    curl -sL http://milhouse.libreelec.tv/other/rkmigrate.sh -o- | bash

    The update function looks for files in the .tar based on the current file naming in /flash so this script renames things to match what the update tar now provides. The decision for a disruptive rename was allowed because at this current pre-alpha release stage user numbers for RK images are small and we'd prefer not to immortalise hacky workarounds in the update function.

    The other alternative (for those scared of scripts) is to backup, reinstall with the latest .img and then restore the backup.

  • Video Card for HEVC 265 10bit

    Quote from Sireone

    So that means there are no discrete GPUs (under $100 at least) that supports 10 bit HEVC in Libreelec? Only option is Gemini/Kaby right now?

    Yup. It's a sucky situation and that's one of the reasons we've been working on a next-generation rendering/decoding pipeline that extends Kodi (on Linux) support to a range of other SoC types so people have more hardware options in the future. It's not going to change the discrete GPU situation though. They're somewhat out of fashion these days.

  • Nvidia GT 1030, Will it Work?

    LE 9.0 still supports nVidia under X11 with the binary blob drivers which provide VDPAU; so everything is 8-bit and no HEVC because nVidia stopped developing VDPAU some time ago. AMD rewrote their formerly VDPAU using drivers to use VAAPI (common with Intel). Kodi v18 is currently broken with VDPAU due to X11 windowing code changes but the main developer that supports X11 has indicated he plans to fix VDPAU support when a replacement test box arrives. Current hardware had some issues and was terminated with a pickaxe. No joke, we have video :)

    LE 10.0 (Kodi v19 so still a long way off) will drop X11 completely and switch to DRM/GBM and KMS (running on the framebuffer, no X11). This works well with Intel/AMD (which dominate user choices) but currently has zero support for nVidia chips because nVidia is solo-championing their EGL streams alternative to GBM buffer sharing. The two current problems are: a) VDPAU is dead code and right now there's zero appetite from Kodi developers to add another proprietary code path for a closed source driver when *all* other GPU/SoC types we plan to support in the future use GBM/KMS, and b) we had a look at EGL streams recently and it failed to run due to nVidia driver bugs. There is a lot of time to kill before LE 10.0 is a serious proposition and we'll maybe look at EGL streams again, or maybe nVidia comes to their senses and uses the same rendering standard as everyone else?

    in the long-term cheap 'Android' boxes/boards will be better all round value for client boxes than x86 kit, except for boxes used as PVR servers, but those don't always need to run Kodi or have the latest GPU in them.

  • Compile Libreelec 6.0.3 (wlan-firmware 404)

    Quote from dreasGh

    I know that but i have several graphic artifacts at startup and shutdown with LibreELEC 8.2.5 and Raspberry Pi 3 Model B, LibreELEC 7.0 does not start. So i'm trying to build old releases.

    RPi 3 hardware was released in Feb 2016 so the OE 6.0 codebase which predates that by a year? is not going to boot even if you do figure out the missing package dependencies. LE 7.0.3 should be fine. NB: Running older software likely introduces more bugs than it might solve, so a current milhouse testing release (newer everything than LE 8.2.5) is probably more productive; and if the issue still exists, report the problem to the milhouse support thread in Kodi forums instead of working backwards with old code.