The amount of time that it takes for a longpress to be registered seems to double when you use an IR translation like this. Perhaps it doesn't really double, the time for it to register is the same, but then after it's registered, then the IR translate layer has to turn around and send the longpress command to the player. So it seems to take twice as long for the player to respond to that longpress than if the IR translation weren't in place at all. (Once to read/interpret and once to send to the player.)


Well, judging by the nature of the IRtranslate functions, I would really assume this to be the case. Remember that IRtranslate does nothing else but to interpret a button press (read it), translate it into (a) new buttonpress(es) and send the result to the player. Since the player doesn't have "short" press aliases for the "long" press functions, there is no way around this.

The real solution for this would be to introduce new "pseudo" button codes to the player (like it was done for "previous visual"), which do what a long button press would do, but only require it to be short.

If those were available, HiJack could send "longright" (replace by a numeric button code) as a short button press to the player instead of "Right.L".

cu,
sven