USBUIRT seems to pick up every IR signal I throw at it. The eventghost plugin seems to work easily enough.
Issues:
1) The MCE remote appears to throw alternating commands per button. So pressing "up" sends one command, and then pressing "up" again sends another command, and then pressing "up" again sends the first command again, and so on. This is surprising to me because the MCE IR base with alternate driver only reported the one MceRemote.Up command. Should I just build my eventghost macro to contain both of the alternate IR commands?
2) Possible bug: In testing "up" with both IR commands in the macro, I dragged the two commands into my existing macro that had MceRemote.Up already there. After mashing the button 20 times I noticed that more than the expected USBUIRT commands had been reported by eventghost -- MceRemote.Up had been reported once or twice as well. This should not be possible with no mce IR base hooked up, I think? So maybe in the shuffle of pressing the button so often, eventghost executed or reported MceRemote.Up when it shouldnt have, just because it is in the same macro as the real commands? The MCE plugin is still active during this test.
3) Pressing the up button repeatedly and faster than eventghost executes the macros results in the macro events being queued up and executed long after button pressing has stopped. So I press up up up up up up up and stop, but it keeps going up for a second or more afterwards. I guess most IR applications (like a TV) will discard some commands so that this does not happen. How do I do I stop this queue of commands with eventghost?
USBUIRT is a smooth, small device compared to the MCE IR. I like it. The pretty eventghost GUI also makes this process easier
