Button press detection problems in Windows
Posted: Tue Sep 15, 2020 9:07 am
Hi All,
I have recently started to notice a problem with my remote setup. When I press a button, like the down arrow, occasionally my computer is decoding it as a "7" for example instead of the down arrow. I notice this in Emby when trying to scroll through the movie library- it is really annoying when a number gets entered because it treats that as search and takes you back to the beginning of the library. In other programs it takes a couple of button presses sometimes to register. I only noticed this problem the past few months.
Has anybody had similar problems? My first suspicion is a Windows 10 update may have broken something, but I can't find anything useful Googling that.
Are there other ideas of ways to test this? I have tested 3 remotes (two JP1 based and one standard WMC remote) and they all behave this way. I only have one IR receiver- could it be going bad? I have a Thrustmaster program that decodes key-strokes (used for validating mapping of keyboard keys to joystick buttons) and it reports out that the 7 key has been pressed instead of the arrow on occasion confirming the behavior I see in Emby.
Thanks in advance for any suggestions.
I have recently started to notice a problem with my remote setup. When I press a button, like the down arrow, occasionally my computer is decoding it as a "7" for example instead of the down arrow. I notice this in Emby when trying to scroll through the movie library- it is really annoying when a number gets entered because it treats that as search and takes you back to the beginning of the library. In other programs it takes a couple of button presses sometimes to register. I only noticed this problem the past few months.
Has anybody had similar problems? My first suspicion is a Windows 10 update may have broken something, but I can't find anything useful Googling that.
Are there other ideas of ways to test this? I have tested 3 remotes (two JP1 based and one standard WMC remote) and they all behave this way. I only have one IR receiver- could it be going bad? I have a Thrustmaster program that decodes key-strokes (used for validating mapping of keyboard keys to joystick buttons) and it reports out that the 7 key has been pressed instead of the arrow on occasion confirming the behavior I see in Emby.
Thanks in advance for any suggestions.