Posts by GrimGriefer

    Just to try I loaded this image on my Kaby Lake 7th Gen NUC NUC7i5BNK and had no luck. Trying to playback HDR content just results in a black screen and I wasn't able to select any sound options other than Bluetooth presume the image is missing the drivers for the platform.

    Good to see work continuing on this though as LibreElec would definitely be my platform of choice given the option.

    Hi there,

    Currently testing the latest Milhouse build of LibreELEC and I have a recurring issue that has been there for a while now and only getting around to reporting it.

    Using my Intel NUC NUC7i5BNK I get the following results for 24p playback when the option is set to adjust the display refresh rate (On start / stop).

    • LibreELEC 8.2.5 (kernel: Linux 4.11.12) - Kodi 17.6 Git:a9a7a20
      • 1080p24 : Working
      • 2160p24 : Working
    • LibreELEC (Milhouse): devel-20181003210259-#1003-gf262797 - Kodi 18.0-Beta4 Git:4e8fd14
      • 1080p24 : Not Working
      • 2160p24 : Not Working

    Every time on the development builds my TV reports the refresh as still set to 60Hz and I can see noticable frame duplication.

    Hope this is something that is picked up in future bug fixings.

    Thanks.


    I doubt this is an error. As far as I can make out installing addons is deliberately more difficult in krypton to make life harder for the build makers. Pre-krypton you could plonk an addon in the addons folder and on re-start it was working. Now it's installed but disabled.

    I think you may be right. Its quite frustrating having to go in and renable restored addons and sometimes they won't enable at all (some services for example).


    Which addons in particular?
    Because we need to be able to reproduce the error(s).

    Nothing in particular. I was trying a flat install of LE and installing Backup and any random addon (like GiantBomb from the Kodi Repo). Backing up the addon and copying the export to my computer. Resetting LE to fresh install again, installing Backup and copying the old export back and importing.

    The addon again wouldn't be present but if I went into my addons it would be there and disabled.

    I just tried the LibreELEC-Generic.x86_64-8.0-Milhouse-20161108212737-#1108-g3f30170 build from last night and suspend now successfully puts the system into sleep mode but any keys presses fail to wake the system up. If I press the power button on the front the system immediate returns from its sleep state.
    [hr]
    Also just noticed that NIC connectivity is not restored on resume. Have to reboot to restore the connection.

    Hi folks,

    I've loaded the LibreELEC (Krypton) v7.90.008 alpha and also the latest Milhouse build on a Zotac ZBOX EN1070 mini PC which uses the nVidia GTX 1070 GPU. Its dual booting LibreELEC and Windows at the moment and have two issues to query if you don't mind.

    Firstly the suspend option doesn't appear to be working correctly as when I try to suspend it shuts the mini PC down for about two seconds before automatically powering it back on again. I've tried disabling and enabling all the different power option in the bios (incluindg the S3 power state) and also tried pulling all usb devices from the system as soon as suspend is triggered but without success. When I choose to suspend in the Windows 10 environment it works fine so I have to thing its something in LibreELEC.

    Secondly I have the mini PC connected to a Samung UE55KS8000 UHD tv and LibreELEC is set to run at 3840x2160@60hz with no problems but when I try to play back a UHD .ts test file with the video profile of HEVC Main [email protected]@High it reverts to using the software decoder instead of the onboard nVidia decoder. The nVidia HW decoder works fine for all other non UHD files/profiles I have tested.

    Anyone got any ideas or suggestions for both?

    Thanks


    Came here looking for this, glad it see it isn't just me.

    Running on an older Intel NUC (Sandy Bridge from memory) and saw this same issue of suttering on the Beta versions of OpenELEC and the Stable/Alpha Versions of LibreELEC.

    I just reverted back to OpenELEC 6.0.3. Can anyone confirm this has been fixed in the latest builds of LibreELEC?

    The latest Milhouse releases (link in previous post) are working a lot better for me now in my testing environment. I haven't switched to it full time yet as my skin of choice (Aeon MQ 7) doesn't work with Krypton yet.


    Hi Guys super noob here.

    I have an mxs plus from sunny tv running libre elec. How can I go about adding 7 short cuts to the confluence menu instead of 5?

    How could I also change the firmware boot logo and splash screen to my own?

    I would recommend ignoring the standard confluence skin and take a look at Aeon MQ7. It is much more scalable to different configuration requirements.

    Had another look tonight and the video decoder is ff-h264 (SW) and I can't seem to change that despite changing the VAAPI options on/off.
    [hr]
    Just updated to LibreELEC-Generic.x86_64-8.0-devel-20160906210318-#0906-gb37a514 and it is working perfectly again.

    Video decoder now says ff-h264-vaapi (HW).

    I use my Harmony Elite in collaboration with a Flirc so can assign any kind of keyboard combination to a remote IR value.

    My keymaps gen.xml is configured as such so the power puts OpenELEC/LibreELEC into suspend mode immediately, or open favorites with the DVR button and switch video soundtracks (to say commentary tracks) with one blue button click.

    Love it.

    <keymap>
    <global>
    <keyboard>
    <f11 mod="ctrl">activatewindow(favourites)</f11>
    <f12 mod="ctrl">XBMC.Suspend()</f12>
    </keyboard>
    </global>
    <fullscreenvideo>
    <keyboard>
    <f10 mod="ctrl">audionextlanguage</f10>
    </keyboard>
    </fullscreenvideo>
    </keymap>

    Sorry to see you are having issues Markus. Whilst I do have video on my devices the video playback is stuttering. Going back to OpenELEC v6.0.3 resolves it but seeing as your NUC uses HD 4400 it is obviously in the Ivybridge family of chipsets and that seems to be the cut off point for issues as you can see in my post here.