Nightly Builds

    The current TigerVNC add-on appears to be compiled against X11 libs so I doubt it runs under Generic, and it probably runs into the same zero-copy video pipeline issues that all the Ambilight setups (that depend on copying buffers that can no longer be copied) enounter under GBM/V4L2. If my guess is correct the add-on will need to be dropped when we remove X11.

    Just curious: LibreELEC-Generic.x86_64-13.0-nightly size jumped from 300 to 500 megabytes


    Code
    -rw-r--r--   1 gentoo gentoo 325067193 May 16 13:40 LibreELEC-Generic.x86_64-13.0-nightly-20260516-ba37c30.img.gz
-rw-r--r--   1 gentoo gentoo 538850403 May 17 17:07 LibreELEC-Generic.x86_64-13.0-nightly-20260517-7374d38.img.gz


    Did something significant change ?

    Have a nice day!

    Caught me out yesterday. The real issue is users can’t apply an update as their current partition is 512MB, LE says to do a new install with a 1GB system part.

    So requires a backup, reinstall, restore.


    Maybe LE can offer NVidia as a new separate gz package?

    Quote from HomerJau

    Maybe LE can offer NVidia as a new separate gz package?

    Nope. If we claim support for nVidia GPUs it needs to work OOB.

    The other option is replacing Generic-Legacy (X11) with an nVidia/GBM image for LE13 to still effect the underlying architectural change but avoid the size-bump for LE13, but we'd want to consolidate for LE14 regardless so it's only delaying the inevitable.

    Wrong place I'm sure. Running an LE build from todays master. x64. A screenshot is now black, no image capture. Is that a known issue with the new GLES changes?


    BTW: LE 13/Piers is in pretty good shape! Well done to all involved. And thanks!

    Quote from chewitt

    The current TigerVNC add-on appears to be compiled against X11 libs so I doubt it runs under Generic, and it probably runs into the same zero-copy video pipeline issues that all the Ambilight setups (that depend on copying buffers that can no longer be copied) enounter under GBM/V4L2. If my guess is correct the add-on will need to be dropped when we remove X11.

    Interestingly I'm running two Intel NUC boxes both manufactured in the same year!

    and Tiger VNC would only work on one even with both installed with;
    LibreELEC-Generic-legacy.x86_64-13.0-nightly-20260519-a7d93f5

    I'm not very good with GPUs but I figured out one box had GPU
    GPU: Mesa Inte(R) HD Graphics 500 (APL 2)
    which VNC would NOT work on

    But the other had GPU
    GPU: Mesa Inte(R) Iris(R) Graphics 540 (APL GT3)
    which is is far superior and VNC works! sorry, useless info but it does save me from walking all the way to the living room to setup Kodi for evenings entertainment... thanks!

    Just FYI for anyone, I've been trying the latest builds on a N150 platform and a AMD Ryzen 5 7640HS that has the Radeon 760M GPU. I have it connected to a Lumagen processor and JVC NZ900 projector. The N150 outputs RGB and the Radeon output YUV:444.

    My lumagen and projector is professionally calibrated by an ISF certified calibrator. We have noticed that the N150 with its output as RGB crushes the blacks slightly. However the Radeon 760M with YUV outputs correctly. We tried all types of material and both agreed the AMD was better. We compared the output to the Kaleidascape Strato player and the Radeon output matches the Kaleidascape. The Intel crushes the blacks.

    Also of note if we play a 4K60 file that is HDR the Lumagen doesn't like the output in RGB. The Radeon outputs it correctly as YUV:420 4k60 which matches the Kaleidascape Player we tried.

    I believe it might be because YUV limits the range to 16-235 where RGB is 0-255

    Just for thought. Someone might find this post useful.


    UPDATE: Looks like it’s a lumagen issue. Disregard 🤣

    Edited once, last by atoulmin: Update (May 25, 2026 at 11:17 AM).

    On a side note. I’ve noticed a bug when using AMD. It doesn’t always apply the correct color. Sometimes it appears washed out. If I stop and restart it usually fixes it.

    I think this has been mentioned before. I’ve tried limiting it to 4:2:0 but doesn’t solve the problem.