Posts by Da Flex

I currently had an RPi4 user, who had disrupted sound due to an old HDMI (1.4) cable. Replacing by an HDMI 2.0 cable solved the issue.

Wow, a very misleading name.

I'm no FLIRC expert, but the name indicates that it has to be configured like a LIRC device. Read here.

Quote from goran_s

Any other advice for this platform?

No. One question - one thread.

Create /storage/.config/autostart.sh with this content:

#!/bin/sh

(
    echo 750 > /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_min_freq_mhz
) &

I assume mglae is right. So test this /storage/.kodi/userdata/keymaps/keyboard.xml please:

<keymap>
    <global>
        <keyboard>
            <red>VolumeDown</red>
            <green>VolumeUp</green>
        </keyboard>
    </global>
</keymap>

Maybe you just had the wrong file name (keymap.xml instead of keyboard.xml).

No, the kodi.log file will store the debug text. If you post a link to your uploaded kodi.log, we can read what happened on your device.

Test with this commands first, just to make sure we use the right config file for your RC:

<red>VolumeDown</red>
<green>VolumeUp</green>

Try /storage/.kodi/userdata/keymaps/remote.xml with content like:

<keymap>
  <global>
    <remote>
      <red>YOUR_COMMAND</red>
      <green>YOUR_COMMAND</green>
      <yellow>YOUR_COMMAND</yellow>
      <blue>YOUR_COMMAND</blue>
    </remote>
  </global>
</keymap>

Which LE hardware and LE version do you use?

HiassofT is pretty much the man when it's about RC's. Maybe our Wiki or lirc_options.conf can help you (timing etc.).

You could use key mapping. Each remote button press will start it's own script, which ignores repeating events for some time.

First: You've been mixed different topics into one thread. We don't like that one-thread-fits-all thing. One question - one thread.

Quote from Herminator

...make the display of my A/V-Receiver show "Multi-In". Is this the same as Dolby Digital?

In the good old days of the internet, the answer would be: RTFM (read the fuc*ing manual).

Anderssen Well, christmas is the time of miracles . You're right, on a non-4K device a 1.4 HDMI cable should be fine. Those 2.0 / 2.1 HDMI cables have better shielding, so I think that did the trick for you. I'm happy that we finally solved it.

It's not just you don't have "apt-get" on LE, you also have to hack the kernel:

Quote from instructables.com

The next step is the part where we hack the kernel! This is what's going to enable us to get 8 channels of sweet, sweet, high resolution audio out of the Pi via HDMI.

The answer is: yes, it's possible - if you're an Amlogic kernel hacker. I don't think somebody else will do that work for you, because it's so unusual. Your question assumes that you are no kernel hacker. So my advice is to buy an RPi, follow the instructions and don't use LE.

PS: HiassofT currently builds an audio-optimized LE for RPi4. If you're very lucky, he could help you, but surely not on Amlogic.

Maybe it's a good idea to start with a fresh installation on another microSD, because your current installation is packed with add-ons.

I'm using the DAZN add-on from the "Kodi Nerds" repo, and I'm in Germany. Maybe one of those facts makes a difference. The rest is pretty close to your setup (LE 9.2.6 on RPi3B+).

You found the right guy, I had the same error a couple of days ago . Solution: Uninstall the DAZN add-on (including config data), switch LE's GUI language to English (US) and install / login DAZN under that language. After successful login you can switch back to your original GUI language. Maybe the add-on developer is from the US, and hasn't tested other language environments.

Quote from Anderssen

de-interlacing is disabled for all videos. Hardware acceleration is switched-off. Nothing changes. However, here's an interesting thing there are no problems with sound in bluetooth headphones. This is a clear HDMI problem .. Maybe, even the HDMI-MicroHDMI adapter is cheap. Maybe the TV is cheap (unnamed). I am switching temporarily back to RPI3 (it is really problem-free)

Thanks again for the feedback! Can you check the standard of your HDMI cabling please? It has to be conform to HDMI 2.0 or 2.1. Otherwise it could be too slow for 4K. It's a common mistake of RPi3 -> RPi4 switchers not to update the HDMI cabling.