Posts by Da Flex

harry_fine Can you guarantee that your HDMI cable is conform to 2.0 or 2.1 standard? That's a common trap for RPi4 users.

Set LE to log level 2 and post a link to a kodi.log.

It's not suggested to use that HDMI mode, because video sources are usually lower than 60Hz, and it slows LE's GUI down. However, you can try to disable de-interlacing on LE's settings, or play with config.txt options (hdmi_safe=1, hdmi_pixel_encoding=2 etc.).

You can expect a lot more progress on RPi hardware, if you search for audiophile features.

I suggest to use Kodi on Raspbian at the moment. If you autostart Kodi on it, you maybe get what you want. Additionally use a second microSD for LE's experimental audiophile builds. Fortunately it's pretty easy to switch to another OS by simply replacing the microSD.

USB data rate could be the issue here, so make sure you are using a blue (high speed) USB connector on the RPi.

Quote from goodrichkenn

I made sure that pass through was working.. but I cannot find where to change any more SOUND settings..

Go to Settings -> System -> Audio -> Audio output device and make sure it's set to "PI: HDMI" or "PI: HDMI and Analogue".

For testing disable "Allow passthrough", which is only needed if the output device should decode the audio.

Use "PI: HDMI and Analogue" to activates the analogue jack of the RPi, and test it with your headphones.

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).