Posts by FeFiFoFum

    LE master branch is already on 5.3 and will bump to 5.4 soon .. but not for RPi4 which needs to remain on 4.19 until more V4L2 plumbing has been completed. Kodi is slowly inching towards HDR support. It's already possible to hack something up that works for some SoCs (not RPi4 yet) but we'd rather do it properly at a more measured pace. I'm not expecting to see "proper" HDR support for some time yet.

    Appreciate the reply. Do you think 6 / 12 months or even longer?

    Sorry, just to clarify, when Linux 5.2 is the base for Libreelec, that's likely when the os will fully support 4k and HDR with the Pi4?

    I'm curious so that I know for future reference. (I may consider a Pi4 then)

    I noticed you already pulled in kernel 5.3 in the development, also for the Pi boards, and that you are now even working on kernel 5.4 integration. That's really impressive and quite bleeding edge I might say. :) Can you shed a light on current performance just so we can get a hint of the future? Thanks a lot for all your hard work.

    Also curious about this. Please let us know.

    What is the difficult part of managing the other 2 Pi?

    I once had a similar situation and I used Kodis MySQL database mode, so I was working within a single database.

    You could just have a primary pi, back up to an IMG file and re-burn the other 2, to SDCard once a month.

    I am very inexperienced, I thought perhaps it may be useful to 'buy the developers' a few extra MB (50,100, 200?) to work with for room to move. Obviously you guys know your stuff very well. Wasn't sure if you had all heard of the technology at all.

    Regardless I have faith, LibreElec has been wonderful on my R.Pi3, it was only a suggestion, thank you all for the hard work.

    I would also like to know the answer to this question from the developers?

    Does LibreElec make use of this? I just discovered this technology today and I imagine there's at least 100MB (?) of data in memory which could just be compressed and left there?

    Any value in it?

    Don't worry you can use .tar or .img.gz to manual update device from existing installed running build to latest beta as mentioned in Update Libreelec section of wiki. Just ensure you have correct .tar or .img.gz file for your specific device, transfer downloaded file into update folder of device (using your chosen method to transfer file to device) then reboot.

    So an .img.gz will NOT scrub the entire disk, just over -write necessary system files?

    EDIT: removed, figured out how to find the .TAR file from within the GUI. (Scared to use .IMG.GZ, might over-write the whole disk, isn't it?)

    Does anyone know if Linux 5.1 will have more overhead on the Pi 1,2,3 and may reduce performance? What about 5.2 which is coming soon right?

    Ok in the interest of being a bit more thorough with my testing.

    I have installed LibreElec OVA virtual machine, totally diff computer (x86)

    Date and time IS correct.

    Brand new install!

    Import of Once Upon Hollywood, this time? 19/July/2019?

    So I'm confused, shouldn't the "date added" be the date added to my LIBRARY?


    Ok it appears the 'date added' library flag is based on the date the file was actually written to disk (total madness, but so be it)

    My 9.1.002 was working fine for a few weeks, except some odd, small issues unrelated to docker.

    When I reboot my Pi now, I get the following error, EVERY time.

    LibreElecPi:~ # docker ps -a

    Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

    If I go into addons and re-install the docker service entirely, it takes about 2 minutes but sure enough, it re-starts up fine. Every re-boot of my Pi, will require the service to be re-installed.

    Anyone else? What can I do to provide help on this?