in the new config software is a reset to default button and that one sets min repeate rate to 1.I try to reproduce the problem, but i am not able to. If your reading this and you had already created the file above you should delete it. The method to change this setting as of OSMC’s Bullseye update will be to use a program called “evrepeat”. The issue being that the version of ir-keytable no longer will take a -device argument and therefore will no let you set the repeat delay on a device not running through lircd like a FLIRC. MOD EDIT: This patch is no longer working with updated versions of OSMC and should not be created. (For reference the default OS values before applying this change are 250 ms for the delay and 33 ms for the period, so a much shorter repeat delay and a faster repeat rate) Please let us know whether this fixes the problem for you. The repeat delay and period can be customised by editing this file and rebooting, however I think the suggested default of 500 and 50 should be fairly optimal. This should change the repeat delay and repeat rate (period) for any keyboard-like devices including flirc. RUN+="/usr/bin/ir-keytable -delay=500 -period=50 -device=$devnode" # set default repeat delay to 500ms like rc remotes # don't change eventlircd device settings Then copy and paste the following into nano:ĪCTION="add", SUBSYSTEM="input", KERNEL="event*", GOTO="start" Next create a udev rule file by creating a new blank file in nano: Via SSH first install the ir-keytable package: If you want to try the fix ahead of time and give feedback as to whether it fixes it for you please try the following: We think we’ve identified the cause and a potential fix for this problem. I’ve also asked if he could create a test build with Kodi’s repeat delay increased to 600mS to see if this will solve the problem without any changes on the remote side, as some remotes may not be able to have their repeat delays and anyone else having problems with unwanted repeats after the last update. If anyone tries this with their harmony remote can you please let me know what the repeat setting was set to by default (2 or 3 I think) so I can set mine this to test the problem further. So it’s a combination of Kodi having too short a repeat delay and the remote repeating the IR code for too long with a short button press.įor those using a Harmony remote you could try reducing the setting I’ve shown in the screenshot to zero for the “device” that your Flirc is configured as, this should solve the problem. If the remote continues to repeat the IR code for longer than the Kodi repeat delay you will get a duplicate press no matter how briefly you press the button on the remote. The repeat delay in Kodi is now 400mS - we’re not sure what it was before, it may have been controlled by settings in Linux itself, however I’m pretty sure it was more than 400mS. I find with most devices (including my Xbox One) that the default repeats for too long, so long ago I reduced the repeat setting to zero as shown in the screenshots. This can be adjusted on the following screens for the device that you have assigned to the Flirc profile:įrom memory the default is either 2 or 3. Harmony remotes by default continue to repeat the IR code for quite a long time after you release the button. It’s not related to inter-key delay in the flirc - that has nothing to do with it. I’ve had a look at this with my Flirc and Harmony One remote and I’m not seeing an issue, however I know what it probably is.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |