Posts by DerDominik

    See https://github.com/LibreELEC/LibreELEC.tv/pull/9587

    You can replicate this locally by creating /storage/.config/udev.rules.d/98-eventlircd.rules with the same content as the PR.

    I'm interested in testing/feedback a) to get this merged for LE13, b) potentially to backport for LE12.2.


    Thanks for the link to that Pull Request.
    After creating the file with complete content from https://github.com/Dashinginthe90…ventlircd.rules it is now working.

    Absolut great and many, many thanks for it :)

    Yes, I tried also with the Keymap Editor, but more/less same error.

    If I configure some actions with buttons I get everytime the same key id, but I pressed different buttons on remote.

    Code
    <keymap><global><keyboard>
           <key id="16839168">audionextlanguage</key>
           <key id="16839168">nextsubtitle</key>
           <key id="16839168">menu</key>
    </keyboard></global></keymap>

    If I test again with the ev-test like mentioned before I see the different buttons.

    In my mind main problem is, that the remote is not correct recognized (as keyboard as I see in the logs).
    Is there a possbility to see some logs from LibreElec Bluetooth connection? I think there is the main problem?

    Today I did some more test with LE12 and I'm more and more confused.

    I stopped kodi from ssh terminal (systemctl stop kodi) and started a libinput logging with "libinput debug-events --show-keycodes"
    Here I see the buttons from my Sony BD Remote as I would expect

    But if I start Kodi it seems that another mapping is automatically taken.

    Most of the buttons are working, but the (for me) important Menu button is not working (the part after left, right should be the menu button)

    I tried to create a keymap xml with different entries, but nothing worked.

    Code
            <keyboard>
                   <key id="0xf081">KEY_UP</key>
                   <key id="0xf080">KEY_DOWN</key>
           </keyboard>
    Code
            <keyboard>
                   <key id="f081">KEY_UP</key>
                   <key id="f080">KEY_DOWN</key>
           </keyboard>

    Maybe someone has an idea how to solve?

    Hello @ll,

    since a long time I'm using LE11 on my NUC which is working good, and I want to change to LE12.
    But there's a small problem with my PS3 BD Remote, where not all buttons are working like "normal".

    I created for comparison two log-files.

    LE11 -> Working
    Button pressing from line 1050

    LE12 -> Not working
    Button pressing from line 1309

    What I'm wondering. In LE11 LIRC is used and in LE12 I don't see something like LIRC in the log files?!
    Don't wonder, LE12 is installed on a RPi4, but same behabiour on my NUC.

    Is there a possibility to re-map the buttons from my PS3 BD Remote?


    Thanks and best regards,
    Dominik

    Hi all,

    I'm using LibreElec on my HTPC in combination with a PS3 BD Remote Control since a long time which was working perfect.

    After update to LibreElec12 only basic buttons are still working (like left/right/up/down, OK, ...).
    But some are not working anymore like top menu/pop up. How and where can I re-configure the missing buttons?
    I think the mapping from LibreElec 11->12 is gone.

    Thanks in advance,
    Dominik

    Maybe "sync playback to display" be chosen, the audio isn't real passthrough.

    No, that option is not selected. Almost every other audio format is working.
    Also DS-HD HR, what I'm wondering about.
    I don't have detailed information about the difference of -MA and -HR, but both are HD audio formats?
    So my suggestion is, that either both or none are working?

    My NUC7i3BNH plays HD-Audio to my Denon amp just fine.

    This wonders me. But what is the difference? :/

    Hm, strange.

    In general the rest of the hardware is ok. Suddenly I took my RPi4 (which works normally as a small server) and installed LibreElec on it.

    DTS-HD MA is working without problems.

    On my NUC7i3BNH I tried also to change the cable. The HDMI firmware is also up-to-date

    DTS-HD MA can work on the hdmi by origin from intel, NUC's hdmi is from DP, so can't play it.

    So maybe this is the reason?

    Or any other suggestions what could be tried?

    Otherwise I've to search for new hardware, which can handle it.


    But anyway.
    Thanks to all for your help :)

    Hi there,

    normally I'm using Kodi on my Windows HTPC, but after upgrading to a new TV and AV-Receiver I also want to test HDR and HD-Audio on that HTPC. HDR is working, but DTS-HD MA is not working. So today I tried LibreElec on that HTPC (booting from a USB-Stick) but the result is the same. DTS-HD MA won't work.

    Before my hardware constellation:
    My HTPC is a Intel NUC7i3BNH, which is connected to a Yamaha V4A AV-Receiver, and this is connected to my TV (all with HDMI).

    I start a .mkiv file with DTS-HD MA Audio, and the AV doesn't get a signal. But the file is working, as my Bluray Player can play it (and I see DTS-HD MA in the AV Receiver Display). The Bluray Player is also directly connected to the AV.

    So maybe the NUC7i3BNH cannot handle DTS-HD MA, but then I'm wondering why DTS-HD HR is working.

    Attached a debug-log from my last try to play that file (I tried that file --> https://we.tl/whSFPBN6hT)

    Debug-Log

    Maybe screenshots from the config are also necessary?
    But I made only basic settings

    Settings->Video->Adjust display refresh rate->On start/stop

    Settings->System->Display->Resolution->1920x1080p

    Settings->System->Display->Refresh rate->60Hz

    Settings->System->Audio->Audio output device->GSM LG TV SSCR2 on DisplayPort #0

    Settings->System->Audio->Number of channels->7.1

    Settings->System->Audio->Output configuration->Best match

    Settings->System->Audio->Allow passthrough->Yes

    Settings->System->Audio->Passthrough output device->GSM LG TV SSCR2 on DisplayPort #0

    Actived all tone formats

    For HDR I tried the updated LE11 version, which is working in general. But with that build also DTS-HD MA is not working.
    So in my mind it was better to create the debug log with the latest official build.

    Maybe someone has an idea about the behaviour?


    Thanks for your help,

    DerDominik