ix.io (which is used by pastekodi) sometimes has hiccups, just try running "pastekodi" again (or reboot and run all three commands again).
so long,
Hias
tried reboot and ran pastekodi 4 times and it hanged all 4 times.
ix.io (which is used by pastekodi) sometimes has hiccups, just try running "pastekodi" again (or reboot and run all three commands again).
so long,
Hias
tried reboot and ran pastekodi 4 times and it hanged all 4 times.
after pastekodi it hangs
Display MoreThe file looks a bit weird (everything in one line), double-check it's fine and doesn't have windows line-endings or other stuff.
Also post the full output of ir-keytable -c -w .config/rc_keymaps/kodi
With a cut-down version it works fine here. After reboot:
CodeLibreELEC:~ # cat .config/rc_keymaps/kodi # table mecool, type: NEC 0x19 KEY_MUTE 0x17 KEY_VOLUMEDOWN LibreELEC:~ # cat .config/rc_maps.cfg * * kodi LibreELEC:~ # ir-keytable -r scancode 0x0017 = KEY_VOLUMEDOWN (0x72) scancode 0x0019 = KEY_MUTE (0x71) Enabled kernel protocols: lirc nec
``
so long,
Hias
Checked the file and line ends were fine
this is output of the command
looks like it does not change the protocol to nec on boot unless you manually change it
Have you set the protocol in the keymap? Also did you use the old format or the new toml one? In the latter case you have to name the keymap file "kodi.toml".
Please post your keymap if you have problems.
so long,
Hias
Yes protocol is set in the keymap and its old format.
below is the file
# table mecool, type: NEC 0x19 KEY_MUTE 0x17 KEY_VOLUMEDOWN 0x13 KEY_VOLUMEUP 0x0d KEY_HOME 0x40 KEY_GREEN 0x42 KEY_RED 0x5a KEY_LEFT 0x06 KEY_UP 0x1b KEY_RIGHT 0x16 KEY_DOWN 0x1a KEY_ENTER 0x4D KEY_EPG 0x51 KEY_BACK 0x55 KEY_PAGEUP 0x15 KEY_PAGEDOWN 0x46 KEY_PLAYPAUSE 0x44 KEY_STOP 0x18 KEY_HOMEPAGE 0x08 KEY_REWIND 0x0b KEY_FASTFORWARD 0x59 KEY_POWER 0x45 KEY_MENU 0x05 KEY_EXIT 0x12 KEY_CONTEXT_MENU 0x0f KEY_0 0x52 KEY_1 0x50 KEY_2 0x10 KEY_3
Hi
I am using latest nightly for RPi4 and got argon 1 case with IR.
I set up the keymaps file in /.config/rc_keymaps/ folder and also edited /.config/rc_maps.cfg to show "* * kodi" and kodi is name of the file I made for keymaps.
however it only works if I type "ir-keytable -p nec" after sshing to the Pi.
then it works until need boot when i have to re do the command to make it work.
anyone know fix on how to make it permanent?
anyone else got this fixed?
I have same issue, the service does not work and script hangs
any newer builds with the HDR patches based on 10.0.2?
I think only RPi is supported for HDR in nightlies.
Kodi 20 is when Linux HDR is meant to be added so maybe in RC1 it will be there maybe.
who knows
we know it works 70% of the time from the SMP builds so its coming along at least
I tested at NUC11PAHI5 with LG OLED.
1. The hdr video could not enter HDR mode, but the previous(20211020222733-d3745e7) was find.
2. Still not support 4k120hz. (The built-in hdmi support 4k120hz, tested in win10)
4k 120hz is not needed for video...95% of 4k videos are 24hz .
4k 120 is a gaming feature
Just wondering if this works with Nvidia cards if I’m not looking for hardware acceleration. I’m perfectly happy with software decoding as I’m using a Xeon 1270 v2 with a gt1030.
EDIT: I tried it, but it crashes at the installer.
Wrong thread this is for Intel/AMD build
No, only static HDR (HDR10, HLG) are supported.
so long,
Hias
Is it just licensing issue rather then hardware dont support it?
Hello
Is it normal for Kodi on RPi 4B using Argon One v2 Case and a Logitech Harmony IR remote to be very slow to respond?
I find the CEC remote to be much faster but using the Logitech remote its very slow to respond after pressing button.
You seem to have set the number of channels to 5.1 so you'll get PCM output - set them to 2 and make sure passthrough is enabled properly in audio settings.
Just checked here, DTS and Dolby passthrough works fine here with 20220115 nightly.
BTW: it also looks like you are using the wrong HDMI port on the RPi4 - use HDMI0, not HDMI1.
so long,
Hias
ah ok
i thought the channels was not applicable if you using bitstream.
thanks will change port too
Hard to tell without debug logs..
so long,
Hias
I tried both output devices. Both same outcome.