Repeated button press speed
Posted: Wed Jan 29, 2025 11:30 am
This question is based on programming of an ONN equivalent of the 3660. I am using these with multiple TV/Roku combinations. Something that has been frustrating with the Roku is with repeated FF or Rwd button presses.
Last night I picked up my Roku remote and found that it responds much faster than the 3660 with multiple presses while not going as fast as a held button does. I would prefer this action on my 3660 but have found no way to do that. I've tried creating a real-time macro with 0 or 0.1 pause on those buttons calling the actual command mapped to a phantom button.
The closest I could come to something a bit better was to create a real-time macro with multiple (like 5) consecutive presses with 0.1 pause on each. That executes more rapidly than I can do by pressing the button consecutively but not as fast as I can do with the Roku remote. On the other hand, it is more predictable than a held button operation that goes too fast. For a single press operation to be also possible, this approach requires mapping the macro to an alternate button.
Can anybody suggest a different approach to forcing individual button presses to be executed more quickly allowing faster consecutive presses? This may well be a limitation with the hardware, but my multiple press macro seems to suggest otherwise.
Last night I picked up my Roku remote and found that it responds much faster than the 3660 with multiple presses while not going as fast as a held button does. I would prefer this action on my 3660 but have found no way to do that. I've tried creating a real-time macro with 0 or 0.1 pause on those buttons calling the actual command mapped to a phantom button.
The closest I could come to something a bit better was to create a real-time macro with multiple (like 5) consecutive presses with 0.1 pause on each. That executes more rapidly than I can do by pressing the button consecutively but not as fast as I can do with the Roku remote. On the other hand, it is more predictable than a held button operation that goes too fast. For a single press operation to be also possible, this approach requires mapping the macro to an alternate button.
Can anybody suggest a different approach to forcing individual button presses to be executed more quickly allowing faster consecutive presses? This may well be a limitation with the hardware, but my multiple press macro seems to suggest otherwise.