![]() # 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. Then I saved the config, forced a firmware update (to the same version) and restored the config and now everything is happy.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. I'm not quite sure what exactly fixed it, but I enabled "builtin profiles" and "sequence modifiers" in the advanced FLIRC settings and set inter-key delay to 2. TL DR: How the heck do I get a held-down harmony remote button to repeat a command using a FLIRC in PMP?ĮDIT: All fixed! Thanks for everyone's input. so I know it's something with either the FLIRC or Harmony setups (and Plex is not to blame). Note: Holding down an arrow key on a USB keyboard on the same box gets me the results I want. but this is the final thing I need to fix to have what I consider the perfect setup. IE: When I'm in my list of movies and want to navigate the alphabet, I have to press the right directional button 13 times to get to "N" rather than just holding it down. I can't get my harmony remote (talking to a FLIRC) to repeat commands when holding down a button. I have only one small issue which I can't seem to figure out: Loving the new Plex Media Player (embedded) on my Chromebox. ![]() Please go to the relevant subreddits and support forums, for example: Build help and build shares posts go in their respective megathreads No referral / affiliate links, personal voting / campaigning / funding, or selling posts ![]() Welcome to /r/Plex, a subreddit dedicated to Plex, the media server/client solution for enjoying your media! Plex Community Discord Rules Latest Regular Threads: No Stupid Q&A: Tool Tuesday: Build Help: Share Your Build: Submit Troubleshooting Post Files not showing up correctly? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |